v11.11 2019-07-08 Added Automated Processing-steps that can be Used as Standard for Enhancement of Cooperation with Google Drive/Sheets

Release Overview

Date Release

• Mon. Jul. 8th, 2019

Changes to be Noted

• The system variable “$ {var [key]}” in “Throwing Message Intermediate Event (HTTP/Email)” is discontinued
• Changed the specification to authorize OAuth2 connection only when “redirect URL” registered in Questetra’s “OAuth2 client” and “redirect_uri” passed in the request to “authorization endpoint URL” match completely when using Questetra as an OAuth2 server.
• No longer support App archives which have been created about 3 years or more ago
• Check out also the plans of changes in future versions [Plans of Future Changes] at the bottom of this page.

---

Details for Version 11.11

Changes of Functions for Normal User

• none

Changes of Functions for Process Owner (Workflow Administrator)

• none

Changes of Functions for Workflow Designer

• Added the following official items to work with the cloud services
  • Service Task (Google Sheets: Append New Row)
  • Service Task (Google Sheets: Download Choice Data)
  • Service Task (Google Drive Search Folder)
  • Service Task (Box: Upload File)
  • Service Task (Box: Create Folder)
• Added the following official items for automating data processing
  • Service Task (Converter (Date to Japanese calendar text))
• No longer support App archives which have been created about 3 years or more ago
  • App archives created with Workflow platform (Questetra BPM Suite) versions older than Ver. 10.4 cannot be imported
  • 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
• On Workflow diagrams in the Process Modeler, the placement of Swimlanes is also attached to the grid
• Fixed following Bugs:
  • Help Page is Not Displayed from the Workflow Diagram on the App Detail Screen

Throwing Message Intermediate Event (Email)

• Set an upper limit on the length of “Process Start address” (256 characters in the entire email address)
• Fixed following Bugs:
  • If the length of “Process Start address” is more than 256 characters, the Process will not Start

Message Start Event (Form)/Receive Task (Form)

• Set an upper limit on the length of “Page URL on Submit” (1000 characters)）

Service Task (Data Assignment)

• Set an upper limit on the number of target Data Items/length of Expression Language
  • Number of target Data: up to 100
  • Up to 100,000 characters in total including all settings

Service Task (Add-on)

• Changed the display position of indication for beta function
• In definition file, corresponded to be able to specify select-data-type by subtype of Date type
  • Added DATE_YMD, DATE_YM, DATE_MD, DATE_Y

System variable/In-app variable

• Discontinued the system variable key止
  • ou can freely set a key at Variable Setting for the [Message start Event/Catching Message Intermediate Event (HTTP)] to be invoked. Please set an appropriate key in consideration of security etc.
  • When sending the key parameter, do not use $ {var [key]}, but specify the fixed value set for each event
  • If variable “$ {var [key]}” is remained in the setting of an App, it will be treated as In-app variable key
  • Added setting of In-app variable key in accordance with the change of handling of variable key (data migration)
• Canceled the warning display that the variable “$ {var [key]}” is used
• If a non-existent variable is referenced in “Service task (data setting)”, etc., an error will occur

Changes of Functions for System Administrator

• none

Changes of Functions for System Engineer

• Changed the specification to authorize OAuth2 connection only when “redirect URL” registered in Questetra’s “OAuth2 client” and “redirect_uri” passed in the request to “authorization endpoint URL” match completely when using Questetra as an OAuth2 server.
  • Up until now, it could be authenticated by forward match, but after the specification change, it can be only by perfect match.

Non-functional Changes and Changes of External tool Functions

• none

---

Plans of Future Changes

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

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

---