2022-05-26 / Version Info

Release Overview

Date Release

Changes to be Noted

  • [Advance Notice] After 2019, it will not be possible to import App-archives that were created about 3 years ago or more at that time
  • Check out also the plans of changes in future versions [Plans of Future Changes] at the bottom of this page.

Details for Version 11.7

Changes of Functions for Normal User

Workflow

  • For the File type Data Item, changed the timing of actually deleting canceled attachment files to the time of data updating (at the time of [Finish “task”], [Save and Quit]), from the Process ending
  • On the Process Detail screen, changed the indication of candidates for operating Human Tasks and Team Tasks to “Anyone, Somebody and N others”
    • Although all the candidates were displayed in the dialog so far, it has corresponded so that several to be displayed on the original Detail screen
    • On the screen for printing, it maintained unchanged as undisplayed
  • In the [Heat Map] legend, changed the notation of “Event” to “Event/Receive Task”
  • Improved the performance of Process/Task search
  • Fixed following Bugs:
    • In [Organizational Performance], a communication error in accessing the API occurs during operation of “narrowing down by month” and “cancellation of narrowing by Process”

Open Chat / Dashboard / Account setting

  • none

Changes of Functions for Process Owner (Workflow Administrator)

  • none

Changes of Functions for Workflow Designer

  • The notation of the link to the manual is unified in “Help”
  • When a validation error occurs in suspended App, it is notified only when an error is detected for the first time
  • Corresponds validation check on all Apps upon starting Workflow platform (Questetra BPM Suite)
  • [Advance Notice] We will not support App archives created about 3 years ago or more
    • Scheduled to be implemented from 2019
    • Apps 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
  • Fixed following Bugs:

Message Start Event/Receive Task (Webhook)

  • Correspond so that content of HTTP response can be configured
    • The response is defined in the same format as “Service Task (Data assignment)” (Expression Language is also available)
    • In two Processes of a parent-child relationship (subprocesses), not only data transmission from child to parent but also data acquisition by parent from child can be realized
  • Correspond “GET/PATCH/DELETE” method in receiving HTTP request
  • Correspond to forcibly terminating “Receive Task (Webhook)”
  • Correspond to recording to “Process Log” when processing fails
    • For “Message Start Event (Webhook)”, in cases where the node can be identified
    • For “Receive Task (Webhook)”, in cases where the token is identified
  • Correspond so that the process log of “Message Start Event/Receive Task (Webhook)” can be referred to at the following place
    • In the Workflow Diagram of the released version of the App Detail screen, open the detailed screen from the properties of “Message Start Event/Receive Task (Webhook)”
      • Regarding a specified node, you can see logs throughout the entire Process
      • Authorization as “App Administrator” or “Process Manager” is required
    • Open [Process Log] on Process Details screen in “Administrator Mode”, or “Auto-Process Log” from Process Record of “Receive Task (Webhook)”

Message Start Event (Email)

  • Correspond so that a Workflow App using “Message Start Event (Email)” becomes an error on Workflow platform where “Message start event (mail)” is not enabled.
    • Whether to be an error or not in a Workflow App will also change if you enable/disable at [Message Start Event (Email)] < [App External Connectivity] < [System Setting]

Receive Task (Form)

  • Added a new BPMN Task icon, “Receive Task (Form)”
    • It is a Receive Task version of “Message Start Event (Form)”
    • You can publish forms that allow users who do not have user accounts on workflow platform will be able to enter data in the middle of a Workflow
    • The specification of the URL is the same as “Receive Task (Webhook)”

Timer Intermediate Event

  • Correspond so that the timer date and time can be designated using the Expression Language

Service Task (Google Drive)

  • Correspond to “Error Boundary Event”
    • It becomes possible to transition to the connection destination from the Error Boundary Event at the end of the error
  • Correspond so that to be able to upload files to Google Team Drive folder
    • When specifying upload destination folder with “folder ID”, correspond to so that Team Drive can be designated
    • When specifying with “path”, it supports only My Drive as before

Script Task / Service Task (Add-on)

  • Correspond to “Error Boundary Event”
    • It becomes possible to transition to the connection destination from the Error Boundary Event at the end of the error
  • Correspond so that “Auto-Processing Log” to be output to “Process Log”
    • In addition to displaying on the Process Detail screen, you can also check logs in [Process Log]
  • Correspond to be able to use “Nashorn” as a script execution engine
    • Change the default execution engine from “Rhino” to “Nashorn”
    • E4X/data/retVal are not available in Nashorn
    • let/const are available in Nashorn
  • In the definition file of “Service Task (Add-on)”, it is possible to specify the execution engine by <engine-type> element
    • 0: Rhino (default), 1: Nashorn

Process Log

  • In the downloaded CSV file, combine “Task ID” and “Event ID” into one, and changed its name to “Node Instance ID”
  • Correspond so that started nodes to be recorded in the log at Process start
  • In the Process Log list, correspond so that the detailed contents to be displayed by clicking [+] to expand
  • Improved the messages (notation) focusing on around “Abnormal End”
  • Correspond so that Users with the authorization of “Process Manager” or “Data Viewer” to be able to view the Process Log of the corresponding App
    • Changed our policy so that even other than “System Administrator” can view
  • Correspond so that to be able to view the Process Log of the corresponding Process on the Process Detail screen
    • [Process Log] button is displayed in Administrator mode
  • Delete logs related to token/logs of Task generation from the Process Log

Changes of Functions for System Administrator

  • Fixed following Bugs:
    • Typo in [Google Connectivity] < [System Setting]

Changes of Functions for System Engineer

  • Deleted the definition of “Message Start/Catching Intermediate Event (HTTP)” from [API manual (Swagger Spec)]
    • Changed to the same correspondence as “Message Start Event/Receive Task (Webhook)”

Non-functional Changes and Changes of External tool Functions

  • Set the upper limit to the database connection time so that a processing that is unfinished for a long time will not affect system performance
  • Upgraded the version of jQuery to 3.3 from 2.2

 

Plans of Future Changes

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

Schedule for 2018

  • In accessing Questetra, unnormalized URL (such as consecutive slashes, etc.) will be prohibited (Spring-Summer 2018)
  • 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 (Autumn 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/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 2018)
    • 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]}”
  • In the “Script task” and “Service task (Add-on)”, we will abolish data retrieving / updating method of the following format. (Autumn 2018 or after)
    • 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)

Schedule for 2019

  • 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 (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 <view /> 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. (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
%d bloggers like this: