v11.13.1 2020-03-09 Fixed a Bug that the Batch-Selection Checkbox Did Not Respond

Release Overview

Date Release

• Mon. Mar. 9th, 2020

Changes to be Noted

• [Advance notice] In April 2020, Flash version of the App editing function will be discontinued
• Check out also the plans of changes in future versions [Plans of Future Changes] at the bottom of this page.

---

Details for Version 11.13.1

Changes of Functions for Normal User

• The [Information] will become displaying also for Normal Users
• In the [Information], the summaries of Maintenance, Bugs, and Service Outage are displayed

Workflow

• Fixed following Bugs:
  • Chrome browser, Batch-selection Checkbox doesn’t Work Properly

Changes of Functions for Workflow Designer

• In platforms of Starter Plan, OAuth2 callback URL will be changed to ”https://s.questetra.net/oauth2callback”
  • No change for Business Plan platforms
• In Split condition setting in XOR gateway, etc. improved the indication when referencing Data Item has been removed
• Fixed following Bugs:
  • Starter Plan Cannot Retrieve the OAuth2 Token in integration with Box
  • “Copy”ing a Workflow App may cause a system error
    • Could occur when deleting Data Items or Swimlanes in HTML5 version Modeler
    • Occurs in a condition where the Data items and Swimlanes be referenced from the Swimlane Operator setting
  • In the HTML5 version Modeler, after duplicating a Data Item, the added Data Item by the duplication is not displayed in the Edit Permission setting in Human Tasks, etc.
  • On the setting screen of “Throwing Message Intermediate Event (HTTP)” on HTML5 version modeler, OAuth2 settings that have been set in the Workflow App are not displayed in the selection list

---

Plans of Future Changes

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

Schedule for April 2020

• For “Message Start Event (HTTP / Form)”, “Catching Message Itermediate Event (HTTP)”, we will abolish the following form of URL which includes processModelInfoId / nodeNumber and key (“Form” only) 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
  • If “Throwing Message Intermediate Event (HTTP)” on the same Workflow platform is the sender, a setting error will occur if the URL in the request parameter format is specified
  • If “Script Task” on the same Workflow platform or HTTP request from an external environment is the sender, the deprecated URL format cannot be detected on the workflow platform. Please confirm and correspond individually.
  • For users (Business Plans) whose transmission has been detected API request in the deprecated form, we have been sending guidance asking for correction individually (Ocober, November, December)
• Flash version of the App editing function will be discontinued
• In the API (/API/OR/ProcessInstance/listCsv) that retrieves the process search results in CSV format, add the “Node name where the token is staying” to the output item
  • If you are performing data processing that depends on the column order of the data (CSV) acquired by the API, it may be necessary to modify

Schedule for July 2020

• For the APIs of “Querying for all Process Instances records” and “Querying for Task records operated by the User”, change to explicitly specify to include Data Items as display items in search results
  • Currently, Data Items specified as search conditions are automatically included also in search results
  • After the specification change, only Data Items for which the element is specified will be included in the search results

Schedule for January 2021

• In the “Script Task” and “Service task (Add-on)”, we will abolish the data retrieving/updating method of the following format
  • 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)

---