v11.12.1 2019-11-18 Responding to Improving Customer Service

Release Overview

Check out also the plans of changes in future versions [Plans of Future Changes] at the bottom of this page

Fixed following Bugs:
- Data non-correspondence may occur if data updates to different File-type Data Items occur at the same time within the same Process (Issue)

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

Schedule for January 2020

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)”
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
“Field name” of Data Item will become a required item (Scheduled for Jan. 2020)
- If it is empty, it will be set automatically when releasing the new version of Questetra BPM Suite in January 2020
At the same time as Microsoft ends support for Windows7 (January 14, 2020), Questetra will also end support for Windows7

Scheduled for June 2020

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

Scheduled for January 2021

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