v11.6 2018-03-12 Corresponds to HTTP Start which can Receive Request Body as It Is

Release Overview

Date Release

Changes to be Noted

  • Accessing to Developer APIs in OAuth 1.0 will be abolished
    • Please change to connection using OAuth 2.0, which is available since version 11.1
  • With the elimination of OAuth 1.0 access to the software development API, the following external tools are abolished
    • Google gadget that displays “Task List” or “Start Process”
    • Chrome extension “You Got Task” (old Chrome Extension)
  • Check out also the plans of changes in future versions [Plans of Future Changes] at the bottom of this page.

Details for Version 11.6

Changes of Functions for Normal User


  • On Screen for Smartphone, enabled “Return” and “Delegate”
  • On Screen for Smartphone, enabled “Terminate” and “Delete”
  • On Process Details Screen for Smartphone, correspond so that URL string entered in String type Data Item to become automatically hyperlink
  • On Task Operating screen, added [Now] button also to the “year / month”, “month / date” and “year” of Date type Data Item
  • Fixed following Bugs:
    • [This Month] and [Last month] in performance Check, the number displayed on the side menu may not match the number of the actual list
    • Clicking on [Feedback] results “Page not found”
    • In Workflow diagram of “Status” on Process detail screen, the color of the edge of Service Task / Script Task icon is displayed in blue instead of gray

Open Chat / Dashboard / Account setting

  • none

Changes of Functions for Process Owner (Workflow Administrator)

  • none

Changes of Functions for Workflow Designer

  • Added “Message Start Event (Webhook)” and “Receiving task (Webhook)” that capable of storing HTTP request body into String type Data Item
  • Added logging function to “Script Task” “Service Task (Add-on)”
  • In “Script Task”, error contents at the time of processing failure are automatically recorded in processing log
  • On Message Start Event (form), display the system time zone of the Workflow platform in input area for Date / Datetime type data
    • [Now] button works according to the displayed time zone
      • So far, it worked according to the time zone of the client terminal
  • Corresponded so that emails whose attachment file names are unknown are also imported in “Message Start Event (Email)”
    • Those whose attachment file name is unknown in the part of Content-Disposition: attachment
    • Takes in with attached file name as “noname”
  • The terms of “API key” and “Security key” which is used in “Message Start / Catching Intermediate Event (HTTP)” to be unified as “API key”
  • In “Service Task (Data assign)”, added function to generate random alphanumeric character string / hash character string
    • randomString(int)、sha256(String)
  • In Operator setting, Improved notation (label) for two options “All subsequent tasks …”
  • In Workflow diagram on Process Modeler, disable “Not Snap to Grid mode (current default)” in item placement
    • Reduce the grid width of “Snap to Grid” and make only this mode to be available
  • In Process Modeler, restrict flow connection point of the Boundary Event to the lower side of icons
  • Change some BPMN icons (Transparent display changed to outline display)
  • In [Manage Add-on], enabled to record “memo”
  • In [Manage Add-on], corresponds so that the file name is automatically set in the name field when selecting a file to register
  • Fixed following Bugs:
    • Message Start Event (Form): An Error Message may be Displayed Despite the Process is Started
    • In “Message Start Event (Email)”, a mechanism to prevent multiple processes from starting by one email is not working effectively
    • When a boundary event is placed in “Human task”, no error will occur even if there is no normal output flow
    • If another header string was used in the header part in “Throwing Message Intermediate Event (Email)”, settings cannot be restored correctly
      • E.g., if “To:” “Cc:” “Bcc:” “From:” are used in the subject, its contents will be overwritten on other setting items
      • Even though there is no problem at the stage of saving the App, when you reopen the Process Modeler and resave it, it will be gone wrong despite you did not touch “Throwing Message Intermediate Event (Email)”
    • In “Team swim lane”, option setting of “Each Task is finished when every allocated user has executed it” may not be maintained
    • In Data Items setting, attempting to add a data item exceeding the maximum number causes Attribute setting part on the right side not to be switched after displaying the error dialog
    • When [Size setting] in [Preferences] is set as “Large”, icons of human task may be displayed larger than the assumed size
    • Possible to [Release] past versions which are not currently under development
    • [Debug execution] can not be executed if the name of the first Task is blank

Changes of Functions for System Administrator

  • Google gadget that displays “Task List” or “Start Process”
    • Response due to abolition of access to Developer API with OAuth 1.0
  • Fixed following Bugs:
    • In setting of Events in [IP address filtering], there is an error in the label of the select box and value (path) to be inserted

Changes of Functions for System Engineer

  • Abolished access with OAuth 1.0 to Developer APIs
  • Added API to acquire App list (/API/Admin/ProcessModel/list)
  • Added API to [Release] a version under development App (/API/PMM/ProcessModel/{processModelInfoId}/release)
  • In API for updating user information (/API/UGA/Quser/update), corresponded to always include primaryQgroup in response
  • Fixed following Bugs:
    • When operating as an OAuth 2 server, the access token can be used even after the expiration date of 12 hours
    • When operating as an OAuth 2 server, passing a nonexistent refresh token at refreshing of the token results in a system error
      • Error content is different from intentioned error

Non-functional Changes and Changes of External tool Functions

  • Changed certificate authority of server certificate to DigiCert from Symantec
  • In accessing Questetra, unnormalized URL (such as consecutive slashes, etc.) will be prohibited (Spring – Summer 2018)
    • Please pay attention to the URL for accessing from a link such as a bookmark or in-house portal, and the URL of API access
  • Unpublish the Chrome extension “You Got Task” (Old Chrome Extension)


Plans of Future Changes

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

Version to be scheduled

  • 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 <view /> element is specified will be included in the search results
  • 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 (Due to Fall of 2018)
    • 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/start/123/0/start
      • /System/Event/IntermediateMessage/123/4/receive
      • /System/Event/MessageStartForm/123/1/XXXYYYZZZ/view
  • For “Throwing Message Intermediate Event (HTTP)”, the variable ${var[key]} is now deprecated (due to be abolished in autumn of 2018)
    • The key can now be freely set for the calling [Message Start/ Catching Message Intermediate Event (HTTP)]. Consider security etc., please set appropriate key.
    • 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]}”
  • In the “Script task” and “Service task (Add-on)”, we will abolish data retrieving / updating method of the following format. (due to be abolished in autumn of 2018)
    • 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 accessing Questetra, unnormalized URL (such as consecutive slashes, etc.) will be prohibited (Spring – Summer 2018)