Release Overview

Date Release

Changes to be Noted

Details for Version11.3.5

Changes of Functions for Normal User


  • Fixed following Bugs:
    • In the date item of the Table type data item, when focus out after entering, the value entered may return back to its original value
    • In using “advanced layout”, Task processing cannot be completed if “0x08 (BS)” is included in the Title or data item
    • In the legend of the chart in “This Month” and “Last Month” in “Performance check”, the label of “Others” is displayed as “$ {action.getText (” … “
    • On the list of the “Others” in “Process/Task Status Check”, it is not immediately reflected even if switching Show / Hide at the Side Menu column.

Open Chat / Dashboard / Account setting

  • Change the label of “Task” in notification emails to “Step Name”
  • Fixed following Bugs:
    • The user icon is not cached in browser, so access is occurring every time

Changes of Functions for Process Owner (Workflow Administrator)

  • none

Changes of Functions for Workflow Designer

  • Fixed following Bugs:
    • On Message on some pages, HTML tag is displayed as it is

Changes of Functions for System Administrator

  • Fixed following Bugs:
    • In App-shared Add-on, the cache of the icon is not deleted even if the definition file of a Service Task (add-on XML) has been deleted

Changes of Functions for System Engineer

  • Fixed following Bugs:
    • In the “Submitting the Task output” API, validation concerning qgroupId is not performed when processing team tasks

Non-functional Changes and Changes of External tool Functions

  • qbpms.api.key in qbpms.config is deprecated [other than SaaS]
  • Fixed following Bugs:
    • In case where qbpms.api.keyRequired = false in qbpms.config, the value of $ {var [key]} is not converted to empty in [Throwing Message Intermediate Event (HTTP)] etc. [SaaS other than]

Plans of Future Changes

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

Due Version 11.4

  • We will make the following changes as part of CSRF measures (security enhancement)
    • Abolished permalink of Process Start (/ PE / ProcessModel / listView? ProcessModelInfoId = XXX & nodeNumber = XXX)
    • Access by GET will be prohibited with respect to APIs of “Submitting the Task output (/API/PE/Workitem/Form/save)” and “Creating a Process Instance (/API/PE/ProcessInstance/start)”
  • We will delete the following deprecated APIs in “Membership Setting API”
    • /API/UGA/Membership/listByQgroup (Retrieving all Members of an Organization)
    • /API/UGA/Membership/listByQuser (Retrieving all Organizations for a User)
    • Respectively, please use ‘/API/User/Membership/listByQgroup’, ‘/API/User/Membership/listByQuser’ which have been added since version 10.1
    • These are postponed to version 11.4, though they were scheduled to be deleted at version 11.2
  • In Internet Explorer 8 and earlier, you will not be able to use Questetra (will not work)
    • Versions earlier than Internet Explorer 8 are already unsupported. Please use versions listed on System Requirements

Due Version 11.5

  • TLS 1.0 will be disabled
    • We are promoting the use of the latest security protocol as an effort to strengthen security so that customers can use it safely.
    • 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

Version to be scheduled

  • 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
  • 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


%d bloggers like this: