Release Overview
Date Release
Changes to be Noted
- Check out also the plans of changes in future versions [Plans of Future Changes] at the bottom of this page.
Details for Version 11.8.1
Changes of Functions for Workflow Designer
- Fixed following Bug:
- In [Service task (Choices Update)], if the contents of the Options Master is the same as before updating, the processing will be stuck
- In case you want to advance the token which has been retained at [Service Task (Choices Update)], please contact us.
Plans of Future Changes
We are planning to alter the following specifications and system platform in the future versions.
Schedule for 2018
- In “Script Task”, change 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 (Winter 2018)
- In File type Data Item, corresponded so that it becomes the same behavior since if there is something other than the file (QfileView, NewQfile) in the List, a script execution error will result
- For “Throwing Message Intermediate Event (HTTP)”, the variable ${var[key]} is now deprecated (Winter 2018)
- 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]}”
Schedule for 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 (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
- Deprecated format
- In the “Script task” and “Service task (Add-on)”, we will abolish data retrieving / updating method of the following format. (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 (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 <view /> 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. (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
- In [Service task (Choices Update)], if the contents of the Options Master is the same as before updating, the processing will be stuck