Release Overview

Date Release

Changes to be Noted

  • Disable TLS 1.0 encryption (Paid Edition)
    • It is already discontinued in the Free version. If verification is necessary, please conduct it in the Free Edition environment.
    • Internet Explorer 9/10, you will not be able to use Questetra
    • On some terminals with Android 4.4, you will not be able to use Questetra
      • It is available on Android 4.4.2 and later
    • For accessing the API, you will not be able to connect from a program such as Java 6/7 which is not compatible with TLS 1.1 or later as standard
      • You can use it by using versions that are compatible with TLS 1.1 or later, or updating, etc.
  • Check out also the plans of changes in future versions [Plans of Future Changes] at the bottom of this page.

Details for Version 11.5.1

Changes of Functions for Normal User

  • none

Changes of Functions for Process Owner (Workflow Administrator)

  • none

Changes of Functions for Workflow Designer

Changes of Functions for System Administrator

  • In the processing of collective registration of the users etc., an upper limit to number of cases that can be registered at one time is to be set
    • Users: 1000, Organization / Role: 300
  • Improve the collective registration processing of users etc., to speed up
  • Fixed following Bugs:
    • [IE11] On the IP address restriction setting screen, unable to delete individual settings of “Message Start Event / Catching Message Intermediate Event”

Changes of Functions for System Engineer

  • Corresponded and corrected the following items in the API manual (Swagger Spec file)
    • Change the examples of the 400 error response to responses that actually to be returned
    • There is a mistake in definition of response of /API/UGA/RoleMembership/add
    • There is a mistake in the definition of the activeTokenNodeName attribute of the response of /API/OR/ProcessInstance/*
  • Published Ver. 11.5.1 version of client library (Java) created by Swagger Codegen
    • Corresponded to the problem in the above Swagger Spec file
    • Corresponded to problems that can not get Quser information from QuserApi.self ()

Non-functional Changes and Changes of External tool

  • Improved server side caching
  • Discontinued the support for TLS 1.0 encryption ()(Security enhancement)
    • We are promoting the use of the latest security protocol as an effort to strengthen security so that customers can use it safely
    • In the Free Edition, TLS 1.0 has already been invalidated. If you need operation confirmation, please use the Free Edition.
    • On Internet Explorer 9/10, you will not be able to use Questetra
    • On some terminals with Android 4.4, you will not be able to use Questetra
      • It is available on Android 4.4.2 and later
    • For accessing the API, you will not be able to connect from a program such as Java 6/7 which is not compatible with TLS 1.1 or later as standard
      • You can use it by using versions that are compatible with TLS 1.1 or later, or updating, etc.
    • Reference / Related information

 


Plans of Future Changes

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

Version to be scheduled

  • Accessing to Developer APIs in OAuth 1.0 will be abolished (In between January and March, 2018)
    • Please change to connection using OAuth 2.0, which is available since version 11.1
  • Since discontinuing OAuth 1.0 access to the Developer API, we will abolish the following external tools (In between January and March, 2018)
    • Google gadget which displays ‘Task List’ or ‘Start Process’
    • “You Got Task”, a Chrome extension (Old version Chrome Extension)
      • Please use the new Chrome extension, “Questetra My Tasks”
  • 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)]. Considering security etc., please set an appropriate key.
    • When sending the key parameter, do not use ${var[key]} and specify a fixed value that has been set for each event
  • 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)