v10.4.2 2016-01-18: Fixed Bugs in Displaying of Task Operating Screen, etc. and Advance Notice of Specifications Change

Release Overview

Date Release

Changes to be Noted

  • We are going to change our support policy for IE to meet Microsoft policy after January 12th 2016, which we will support only the latest version of IE available to respective OS.
  • Check out also the plans of changes in future versions at [Plans of Future Changes], the bottom of this page.

Details for Version 10.4.2

Normal User


  • Fixed following Bugs:
    • On Task Operating screen in which [Advanced layout] has been used, the choice of empty label (representing the non-input) does not appear in the pull-down when entering Select type data item (Select box).
    • In Task Operating screen, an error message is displayed when you close the dialog without selecting a file when you upload a file to the File type data item or to Open Chat post, at the file selection operation of the second and subsequent times.
    • In Task search, it is unable to search Human Tasks which Step-names are blank. (Mandatory error occurs)
    • In Task Operating screen for smartphones, Data item name is displayed with surrounded by a frame, if the Process data has been set as “Display only”.

Open Chat (Task Feed) / Dashboard / Account Setting

  • None

Process Owner (Workflow Administrator)

  • Fixed following Bugs:
    • Email for notification of “Tasks that have no operator” will not be sent if the Task has been set its Deadline, even if Operator of the Task does not exist.

Workflow Designer

  • Fixed following Bugs:
    • In [Message Start Event (Form)], despite initial value has been set on Select type data item (Checkbox), it is not checked in the Operating screen. (Initial value setting is not enabled.)

System Administrator

  • Fixed following Bugs:
    • Logo does not appear at top left on Process Modeler screen if “Logo(small)” has been set in [Logo] menu in [System Setting]

System Engineer

  • None

Application / Use Environment / System Platform

  • Edge of Windows 10 has been added to Supported browsers
    • However, functions of [Process Model setting] (for Workflow designer) is excluded.
  • Changed cipher suite priority order for SSL
    • Higher cryptographic strength to utilize preferentially.


Plans of Future Changes

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

  • For Options master (Options XML), we will change specifications that an Option becomes invalid when any one of the choices ID (value) / label (display) is blank.
    (Scheduled to change in next Major version [ver. 10.5])

    • Also “setting as blank” is invalid when you define the option in other methods than the Options master. (specification unification)
  • In [Catching Message Intermediate Event] and [APIs for Task processing (/API/PE/Workitem/Form/save)], we will change specifications of behavior related to Select type data item (Checkbox) and File type data item.
    (Scheduled to change in Major version after next [ver. 10.6])

    • We will change that Value of Select type (Checkbox)/ File type to be maintained when the permission setting is “Editable” and the corresponding parameter is not transmitted.
    • In the current specification, value will be cleared.
    • This is for the unification of behavior to meet with other Data types which is to maintain value if not sending parameter.
    • Unifying in “to maintain value if not sending parameter” and “to clear value if sending blank value parameter”
  • In [Throwing Message intermediate Event (HTTP)], we will change specification that if the value of “Title” is blank, it will exclude from sending parameter.
    (Scheduled to change in Major version after next [ver. 10.6])

    • Unification with other Process data items.
  • [Abort Task (Token will not move)], the handling at deadline, will be abolished
    (Scheduled to change in next Major version [ver. 10.5])

    • Existing configuration will continue operating for the time being, but it will not work at the time of abolition and after.
    • Please change to the setting option which utilizes ‘Boundary Event’: [Abort Task (Token will move to Timer Boundary Event)]
  • In [Message Start Event (HTTP)] and [Catching Message Intermediate Event (HTTP)], HTTP response to be returned at the time of processing error will be changed to “400” from “500”
    (Scheduled to change in next Major version [ver. 10.5])

    • For such a program that has been described the processing based on the HTTP response code, you will need a change
  • In [Throwing Message Intermediate Event (HTTP)], HTTP request in ‘application/json’ format (POST / PUT / PATCH) will be abolished.
    (Scheduled to change in [ver. 10.7])

    • Please change the settings using the feature that has been added in Version 10.4, which is capable of sending request specifying any part of Content-Type / Body.