v11.0 2016-05-23: Added “Process Summary Chart” to [Dashboard]

Release Overview

Date Release

Changes to be Noted

  • The specification of Options Master (Options XML) has been changed t that an option in which either of Options ID (value) or Display label (display) is empty will become Invalid
    • “Empty strings” will also be invalid even if it has defined in methods other than Options Master (Specification unification)
  • [Abort Task (Token will not move)], the handling at deadline, has been abolished
    • Existing configuration will behave as [No Action]
    • Please use the setting option which utilizes “Boundary Event': [Abort Task (Token will move to Timer Boundary Event)]
  • For [Message Start Event (HTTP)], input check is carried out with an initial value being set
    • “Required error” occurred so far in the cases where Required data item which an initial value has been set and has set as “editable”, does not receive target parameter.
    • Hereafter, an initial value has been set, and Required error will not occur
  • Of [Message Start Event] and [Catching Message Intermediate Event (HTTP)], HTTP response to be returned at the time of processing error has been changed to “400” from “500”
    • For such a program that has been defined the processing based on the HTTP response code, you will need to revise them
  • Check out also the plans of changes in future versions at [Plans of Future Changes] the bottom of this page.

Details for Version 11.0

Normal User

Workflow

  • File size of attachment to File type data item to be displayed on Task Operating screen, etc. (Only if the file is attachable)
  • Changed the time display format in [Operation History and Current Status] on Process Detail screen, to “Status, Date and time, Elapsed time from the previous state”
  • Changed the display of [Status (Process Diagram)] to show the path which the Issue has passed
  • Unified the display when the value in a Dataitem which has been set as [display only] is “empty”, to display nothing (empty string)
  • Changed not to use list in HTML when displaying the values in “Radio button / Select / Search select” type of Select type data, in Process Detail screen, etc.
  • Will change the invalid Content-Type to application/octet-stream when attaching to File type data item or to a message on Open Chat
  • Increased the number of displaying Data items on Task Operating screen for Smart-phone from 10 to 20 per page
  • Fixed following Bugs:
    • A communication error occurs and not able to search upon trying to search for the first time, if a value has been input to User type data item (search select) when opening Task operation screen
    • The layout of screen for error message of OAuth connection has collapsed

Open Chat (Task Feed) / Dashboard / Account Setting

  • Unified the Download URL of files attached to Message / Comment
  • Fixed following Bugs:
    • Some of the characters that are used in a User name or File name would not be escaped

Process Owner (Workflow Administrator)

  • [Process summary chart] is now available on Dashboard
  • Changed the displaying width of the path (flow) on the Process Diagram Graph in [Organizational Performance] according to the number of passage of Issues
    • The more Issues have passed, the wider the path line is displayed

Workflow Designer

  • [Abort Task (Token will not move)], the handling at deadline, has been abolished
    • Existing configuration will behave as [No Action]
    • Please use the setting option which utilizes “Boundary Event': [Abort Task (Token will move to Timer Boundary Event)]
  • Changed not to increase the value of [Process Sequence number] upon Process Start on Debug execution
  • Changed the Name of Swimlane to be mandatory
  • Fixed following Bugs:
    • Width of Swimlane is spreaded although it is not necessary when moving icons after changing the setting of [Size] to “Large” and placing Items, then changing the setting to “Small”
    • For Process Model and PRocess, [Delete] may not be completed properly

Process Data Items

  • You are now able to define your own [Field name] in Process Data items setting
    • You can use it for [Message Start Event] or [Service Task (PDF generation)], instead of the Variable name using Data definition number
  • For File type data item, “The maximum value of total file size” becomes capable to be specified as an element of Input check
  • An asterisk (*) is indicated on Required Item in left panel in the Process Data Items Setting screen
  • Added [help] button on Process Data items setting screen
  • Table type data item is allowed to be deleted even if the sum of the “values” in Table type data was referred by a Numeric type data item
    • Error alert will be indicated on the formula in Numeric type data item

Select Type Data Item

  • Nesting in Select type data items is available now
    • Available if the subtype was “Radio button” or “Select”
    • Options of Child item will be filtered and shown when a Parent item is selected (Narrowing down by the parent item)
    • Target to be display is that the beginning of the Options ID matches the Options ID of the Parent
  • Options which either of Options ID (value) or Display label (display) is empty will become Invalid in an Options Master (Options XML)
  • An error occurs on Process Model if an Option has been defined that its Options ID or Display label is empty応
  • Fixed following Bugs:
    • The number of Options may differ in comparison of the List of options displayed from [(Common) Process Model file] with the List of options displayed on Task Operating screen

Throwing Message Intermediate Event (Email)

  • Allows transmission of an Email which Content-Type of the attachment is incorrect

Throwing Message Intermediate Event (HTTP)

  • Allows addition ofcustom HTTP header to Send request
    • Header that begins with “X-“, and ‘BoxApi” which we have added to our permission list are available
    • However, some of header, such as “X-Forwarded-For”, are unavailable (Error message upon specified)
  • Added an option of “Standard format”, which is to send raw data (dot as decimal point, no thousands separator) when specifying Numeric type data item to a value of Send parameter
  • Available to specify arbitrary Content-Type (combobox) in specifying Request body
  • Response of “application/javascript” etc., is possible to be saved in String type data item
  • HTTP request in “application/json” (POST / PUT / PATCH) is no longer available to create newly

Message Start Event / Catching Message Intermediate Event (HTTP)

  • Reference of Process data item using “Field name” is now available
    • Values are acceptable also in the Field name which has set in respective data item, instead of “data[X].XXX” format parameter
  • Values are received as raw data (dot as decimal point, no thousands separator) into Numeric data item
    • In “data[X].usdecimal”, values are received with a dot as decimal point, even though the setting og Numeric type data item was comma
    • Conventional “data [X] .input” is also available (Deprecated)
    • Behavior of receiving values in “Field name”, is the same as “data[X].usdecimal”
  • When empty string is sent to Datetime data item in [Catching Message Intermediate Event (HTTP) or Task Handling API, the values will be cleared
    • It will be able to clear the value of the date-time data item at the data [X] .datetime format parameters
  • For [Message Start Event (HTTP)], input check is carried out with an initial value being set
    • “Required error” occurred in the cases where Required data item which an initial value has been set and has set as “editable”, does not receive target parameter. An initial value has been set, and Required error will not occur.
  • Unified the format of XML upon error for [Message Start Event (HTTP)] and [Catching Message Intermediate Event (HTTP)]
  • Changed the parameter name which to be contained in XML upon error in [Message Start Event] or Task Handling API, from data[X].input to data[X].datetime
  • Ignores if receiving data other than file data in File type data item in [Message Start Event] or Task Handling API
    (Not to occur “Unknown error”)

Message Start Evnt (Form)

  • Fixed following Bugs:
    • The Initial value of “Checked” in Select type data item (Checkbox) results in being Unchecked
    • Initial values in some Process data items are not capable of cleared in [Message Start Event (Form/HTTP)]

Script Task

  • Reference of Process data item using “Field name” is now available
    • Reference: “Field name”, “data.get(“Field name”)”, “data.get(“Data definition number”)
    • Overwriting: retVal.put(“Field name”,”value”) retVal.put(“Data definition number”,”value”)
  • Fixed following Bugs:
    • Error occurs upon using try/catch statement

Service Task (PDF generation)

  • Reference of Process data item using “Field name” is now available for Template PDF
    • Both of “Field name” and conventional “data[X].XXX” are available

System Administrator

  • Added [System summary] menu
    • Added a Widget for monitoring the transition of actual number of Users
    • Added a Widget for monitoring the transition of total file size
  • Reformed the processing for [User deletion]
  • The timing of Tokens leaving from node (Tasks etc.) to be recorded in [Process logs]

System Engineer

  • In response of API for “Retrieving Process Instance” (/API/OR/ProcessInstance/view), the name of Process data items to be included
  • Changed the contents of output concerning File type data of APIs to retrieving list of Processes etc., to be the same as the API of “Retrieving a List of forms for Task output” (/API/PE/Workitem/Form/viewXml)
  • Changed response of [Message Start Event] and [Catching Message Intermediate Event (HTTP)] in case of errors of invalid parameter etc., to HTTP status code of 400s
    • Responded 500s so far. Changed errors caused by Users in the aspect of Service monitoring, etc.
  • Removed the following API
    • Deleting Process /API/PIM/ProcessInstance/delete)

Application / Use Environment / System Platform

  • Added [X-Frame-Options:SAMEORIGIN] on HTTP response header (Security enhancement)
    • In the case you use Questetra with embedded screen on other Web sites, the screen of Questetra will no longer be displayed
    • (2016-05-24 added)

 


Plans of Future Changes

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

Due Version.11.1

  • 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
    • 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.
    • Unification with other Process data items

Due Version.11.2

  • In [Throwing Message Intermediate Event (HTTP)], HTTP request in ‘application/json’ format (POST / PUT / PATCH) will be abolished.
    • 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