Release Overview

Date Release

Changes to be Noted

  • In [Throwing Message Intermediate Event (HTTP)], setting error occurs in the following cases
    • Data Item that stores response and one that stores error is the same
    • OAuth2 has been specified in the security setting and there is no OAuth2 setting to be referenced
    • Upon specifying OAuth2 in the security setting, a setting error will occur if “variable” is used (Use of “variable” in OAuth 2 setting is deprecated)
  • Check out also the plans of changes in future versions [Plans of Future Changes] at the bottom of this page.

Details for Version 11.9.0

Changes of Functions for Normal User

Open Chat

  • Fixed following Bugs:
    • When previewing the attached image file, the download link may not be displayed if the file name is long
      • It occurs when the language setting is “English” and the file name is consecutive alphanumeric characters

Changes of Functions for Process Owner (Workflow Administrator)

  • none

Changes of Functions for Workflow Designer

  • Added the following Task icons that allow linkage with Cloud services
    • Service Task (Google Drive: Create Folder)
    • Service Task (Google Drive: Delete File )
    • Service Task (Google Calender: Insert Event)
    • Service Task (Slack: Post Chat (Incoming Webhook)
    • Service Task (Slack: Post Chat (Bots))
  • Changed the name of [Service Task (Google Drive)] to [Service Task (Google Drive: File Upload)]
  • Excluded Apps that Not-released (suspended) from the list of Apps containing errors displayed on the App List screen
  • Corresponded so that “Active” Apps cannot be deleted
    • Only Apps “before releasing version 1” and “Suspended” can be deleted
    • To delete an Active App, Suspend it before deleting
  • Enhanced the validation check on configuration contents upon saving an App
  • Corresponded to multiple line display of error message on the property screens of each Object on a Workflow diagram

Service Task (Data assignment)

  • Partially loosened the EL validation (input check)
    • e.g. Expression that differs success or failure at the time of execution depending on the contents of the data to be referenced
  • Corresponded so that include detailed contents in the message of an error found by EL validation

Script Task/Service Task (Add-on)

  • Corresponds so that system limit value, such as the number of HTTP requests, can be obtained within the script
    • e.g. You can get the maximum number of requests with httpClient.getRequestingLimit()
  • Added license element to definition file (XML) of [Service task (Add-on)]

Throwing Message Intermediate Event (Email)

  • Corresponded so that an event is handled as “end normally” when the delivery of the email to the mail server is successful
    • “Processing failure” if it could not give it to the mail server

Throwing Message Intermediate Event (HTTP)

  • Corresponded so that setting error occurs when the Data Item that stores response and one that stores error is the same
    • The value of the Data Item to store error will be “null” when no error occurs
  • Corresponded so that a setting error will occur when OAuth2 has been specified in the security setting and there is no OAuth2 setting to be referenced
  • Corresponded so that upon specifying OAuth2 in the security setting, a setting error will occur if “variable” is used
    • Use of variables in the OAuth2 setting is going to be deprecated in the future
  • Changed some display labels on the setting screen of OAuth2, etc.

Split Setting

  • In the setting of Split condition expression of the XOR/OR gateway, set the upper limit on the character string length of the fixed value to be compared
    • Maximum 500 characters- Setting error if exceeding 500 characters

Data Items/Editing permission setting

Changes of Functions for System Administrator

Changes of Functions for System Engineer

  • none

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 2019

  • 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 (Version 11.10.0, April – June, 2019)
    • 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 (Version 11.10.0, July – September, 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]}”
  • 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 (on and after July 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
  • In the “Script task” and “Service task (Add-on)”, we will abolish data retrieving / updating method of the following format. (since 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 (since July 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 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. (since July 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
  • “Variable” will not be available when specifying OAuth2 in the security setting of [Throwing Message Intermediate Event (HTTP)] (since July 2019)
    • Since on and after Ver. 11.9, setting error occurs if “variable” is used, so please change

2 thoughts on “v11.9 2019-02-04 Added Standard Task Icons, Enhanced Linkage with Google Drive/Slack”

  1. Pingback: Notice for Service Outage due to Upgrading on Feb. 4th, 2019 – Questetra Support

  2. Pingback: Cloud BPM v11.9 has Slack Integration for Easier Posting - Questetra

Comments are closed.

%d bloggers like this: