Release Overview

Date Release

Changes to be Noted

  • In “Script Task”, changed the specification so that script execution errors will occur if there is anything other than the character string in elements in the List specified to Select type Data Item
    • Correspond to become the same behavior of script execution error that occurs on File type Data Item when there is other than files (QfileView, NewQfile) in the List
    • That is, we will carry out the contents of which we have given notice in the “Plans of Future Changes”
  • Check out also the plans of changes in future versions [Plans of Future Changes] at the bottom of this page.

Details for Version 11.10.0

Changes of Functions for Normal User

Workflow

  • Corresponded so that only Tasks which came into [My Tasks] via [Offered] can be [Returned]
    • Tasks which came in [My Tasks] because the user has handled the upstream Step become not able to be returned
    • To prevent notification emails from being sent to users who are not concerned with the Issue by unintended [Return] operation

Changes of Functions for Process Owner (Workflow Administrator)

  • none

Changes of Functions for Workflow Designer

  • Added the following automatic Step icons which allow linking with external site/cloud service
    • Service Task (Any Website: File Download)
    • Service Task Slack: Upload File (Bots)
  • Added a link to [Get Started] (Your first step of Questetra BPM Suite) in the side menu
    • The tutorial videos displayed in Process Modeler is discontinued
  • In “Script Task”, changed the specification so that script execution errors will occur if there is anything other than the character string in elements in the List specified to Select type Data Item
    • Correspond to become the same behavior of script execution error that occurs on File type Data Item when there is other than files (QfileView, NewQfile) in the List

Service Task (Data assignment)

  • Corresponded to be possible to describe codes using “Field name”
    • Retrieve data with the format of “#FILD NAME”
    • (We consider abolishing the data retrieval by EL expression using the data definition number and shifting to retrieving by field name in the future)
  • Changed the error message to indicate which data item is invalid when an “incorrect expression” error occurs
  • Corresponded so that error will result when try to retrieve nonexistent “EL variable” with Expression Language
    • Error occurs upon input check and execution
    • Example of correct variable: #now, #today
  • Enhanced checking on Data Items to be stored

Service Task (Add-on)

  • Corresponded to be possible to define Config items to select the OAuth2 setting defined in the Workflow App応
    • form-type=”OAUTH2″
    • Using this setting item is recommended when referring to OAuth2 setting in a script
  • Corresponded to be possible to identify which setting is wrong when an EL invalid error occurs
  • Fixed following Bugs:
    • On the screen which cannot be edited (confirmation screen) upon selecting a user, unnecessary clear button is displayed

Service Task (Google Drive: Upload File)

  • [Notice] For the upload destination folder, specifying with the folder path will be discontinued in the future version
    • Because the function is duplicated with “Service Task (Google Drive: Create Folder)”
    • You can do the same by uploading files after creating a folder by “Service Task (Google Drive: Create Folder)”
  • Fixed following Bugs:
    • Deletion/type conversion of Data Items referenced in Config items can be carried out

Service Task (Choices Update)

  • Applied an upper limit on the number of characters in the file name when saving Options Master (XML) (57 characters)
    • An error will result if exceeding the limit
    • In v11.9.1 and earlier versions, more than 57 characters were cut off
  • Fixed following Bugs:
    • Deletion/type conversion of Data Items referenced in Config items can be carried out

Throwing Message Intermediate Event (Email)

  • Enhanced the error checking upon setting
    • Corresponded so that in syntax errors, non-existent variables, and references to deleted Data Items result in an error
  • Applied an upper limit on the length of an email that can be set
    • The upper limit of the number of characters in the entire text including the address, the subject, and the body to 10000 characters
    • An error will result on the config screen if exceeding the limit
    • (Separately, the upper limit of the size of an email including the attached file is 10MB (size after MIME encoding))

Team Task (Team Swimlane)

  • Fixed following Bugs:
    • When the option of “Each task is finished when every allocated user as executed it” is enabled, an error occurs when the last user completes the Task if there is a setting of “Data Item to which each information of the Task is stored upon completion

Data Items

  • Corresponded so that it is easy to utilize “Field Name”
    • Moved the display position of “Field Name” to underneath “Data Item Name”
    • Corresponded so that the initial setting value of “Field Name” is entered

Select type Data Item

  • Applied an upper limit on the number of characters for “Choice ID” and “Display Label”
    • 1000 for both
    • Error results if more than 1000 characters when defining choices in an App
    • When defining choices outside of an App, choices over 1000 characters will be ignored
  • Applied an upper limit on the number of choices when defining choices in an App
    • The number of choices is limited to 1000, and an error occurs if the number is exceeded
  • Applied an upper limit on the number of items to read when acquiring all options via HTTP or Option Master (XML)
    • The upper limit is 150,000, and choices that exceeding the upper limit is ignored
  • Corresponded so that error results if exceeds “upper limit of Select type Data Item” when registering an Options Master (XML)
    • When the number of choices is more than 150,000
    • Choice ID/Display label is longer than 1000 characters
  • [Notice] When the sub-type is “radio button/select box/check box”, an upper limit will be applied for the number of items displayed on the Task Operating screen
    • Do not display more than 1000 choices
    • If there are more than 1000 choices, use Search Select
    • Be careful when defining choices via HTTP or using Options Master (XML)

Variable

  • Use of symbols other than underscores (_) in variable names is now prohibited
    • If any is used, an error will occur – Please modify
    • Usable characters for variable names: single-byte alphanumeric characters, single-byte spaces, underscores (_), non-ASCII characters (Japanese characters)
  • For variable, use of the same name as a system variable, such as “applicationRoot” is now prohibited
  • Applied the following upper limit and strengthened the input check
    • Variable name / Profile name: 64 characters
    • Value of variable: 1000 characters
    • Number of variables * Number of profiles: 150
  • Unify the format when embedding variables into “$ {var [VARIABLE NAME]}”
    • Even though “$ {var. VARIABLE NAME}” or “$ {var [‘ VARIABLE NAME ‘]} ” used to work, it will no longer do

Changes of Functions for System Administrator

Changes of Functions for System Engineer

  • none

Non-functional Changes and Changes of External tool Functions

  • Change Java execution environment from Java 8 to Java 11

Plans of Future Changes

We are planning to alter the following specifications and system platform in the future versions.

Schedule for 2019

  • For “Throwing Message Intermediate Event (HTTP)”, the variable ${var[key]} is now deprecated (Version 11.10.0, July – September, 2019)
    • The key can now be freely set for the calling “Message Start/ Catching Message Intermediate Event (HTTP)”. Please set appropriate key considering security etc.
    • When sending the key parameter, do not use ${var[key]} and specify a fixed value set for each event
    • A warning will display on Apps in which “$ {var [key]}” is used. Even though it will work with the current setting until it is discontinued, when you upgrade the application, you need to change it so as not to use “$ {var [key]}”
  • For “Message Start Event (HTTP / Form)”, “Catching Message Itermediate Event (HTTP)”, we will abolish the following form of URL which includes processModelInfoId / nodeNumber / key in the request parameter (on and after July 2019)
    • Deprecated format
      • /System/Event/MessageStart/start?processModelInfoId=123&nodeNumber=0
      • /System/Event/IntermediateMessage/receive?processModelInfoId=123&nodeNumber=4
      • /System/Event/MessageStartForm/view?processModelInfoId=123&nodeNumber=1&key=XXXYYYZZZ
    • New recommended format (Ver. 11.4 or later)
      • /System/Event/MessageStart/123/0/start
      • /System/Event/IntermediateMessage/123/4/receive
      • /System/Event/MessageStartForm/123/1/XXXYYYZZZ/view
  • In the “Script task” and “Service task (Add-on)”, we will abolish data retrieving / updating method of the following format. (on and after July 2019)
    • Retrieving:data.get(“1”), Updating:retVal.put(“1”, “foobar”)
    • Please change to the new format (Ver. 11.4 or later) such as engine.findDataByNumber(1), engine.setDataByNumber(1, “foobar”) (M230)
  • In APIs of “Querying for all Process Instances records” and “Querying for Task records operated by the User”, it will be changed to explicitly designate as display items to include process data items as search results (on and after July 2019)
    • Currently, Process Data Items specified as search criteria are automatically included in search results
    • After the specification change, only the Process Data Items which element is specified will be included in the search results
  • App archives that have been created in about 3 years ago and before will be out of support. (on and after July 2019)
    • App archives created in 2016 will be supported until 2019, in 2017 will be so until 2020. (always the past 3 years will be supported)
    • App archive that is out of supported cannot be imported
  • “Variable” will not be available when specifying OAuth2 in the security setting of [Throwing Message Intermediate Event (HTTP)] (on and after July 2019)
    • Since on and after Ver. 11.9, setting error occurs if “variable” is used, so please change
  • In Service Task (Google Drive: Upload File), for the upload destination folder, specifying with the folder path will be discontinued in the future version
    • You can do the same by uploading files after creating a folder by “Service Task (Google Drive: Create Folder)”
  • When the sub-type is “radio button/select box/check box”, an upper limit will be applied for the number of items displayed on the Task Operating screen
    • Do not display more than 1000 choices
    • If there are more than 1000 choices, use Search Select
    • Be careful when defining choices via HTTP or using Options Master (XML)

1 thought on “v11.10 2019-04-08 Attachment Become Available with Slack Post”

  1. Pingback: Notice for Service Outage due to Upgrading on Apr. 8th, 2019 – Questetra Support

Comments are closed.