v11.10.3 2019-06-24 Data Maintenance Processing Improved

Release Overview

Date Release

• Mon. Jun. 24th, 2019

Changes to be Noted

• [Notice: Scheduled for July 2019] For “Throwing Message Intermediate Event (HTTP)”, the variable ${var[key]} will not be available.
• [Notice: Scheduled for July 2019] We will change the specification so that, when using Questetra as an OAuth2 server, you can authorize OAuth2 connection only when “redirect URL” registered in Questetra’s “OAuth2 client” matches completely with “redirect_uri” that is passed in the request to “authorization endpoint URL”
• 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.3

Non-functional Changes and Changes of External tool Functions

• Improved regularly data maintenance processing

---

Plans of Future Changes

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

Schedule for July 2019 (Ver. 11.11.0)

• For “Throwing Message Intermediate Event (HTTP)”, the variable ${var[key]} is now deprecated (Version 11.10.0, July, 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]}”
  • If you are using “${var[key]}” in “Throwing Message Intermediate Event (Email)”, the warning will not be displayed, so please be aware.
• We will change the specification so that, when using Questetra as an OAuth2 server, you can authorize OAuth2 connection only when “redirect URL” registered in Questetra’s “OAuth2 client” matches completely with “redirect_uri” that is passed in the request to “authorization endpoint URL” (Scheduled: Ver. 11.11.0 / July 2019)
  • Currently, it is approved in forward match, but after specification change, it can be approved only in the case of exact match
• App archives that have been created in about 3 years ago and before will be out of support.
  • 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

Schedule for October 2019 (Ver. 11.12.0)

• When the sub-type of Select 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)
• 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)”
• “Variable” will not be available when specifying OAuth2 in the security setting of [Throwing Message Intermediate Event (HTTP)]
  • Since on and after Ver. 11.9, setting error occurs if “variable” is used, so please change

Scheduled for after of October 2019

• 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
  • 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
  • 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

---