v11.13 2020-01-20 Enhanced Automatic Setting Function for Business Data

Release Overview

Date Release

• Mon. Jan. 20th, 2020

Changes to be Noted

• In “Service Task (Google Drive: Files Upload)”, the method with folder path for specifying the upload destination folder is abolished
• “Field Name” on Data Items become mandatory
• At the same time as Microsoft ends support for Windows7 (January 14, 2020), Questetra will also end support for Windows7
• The new App editer (HTML5 version) will not support IE11
• [Advance notice] In April 2020, Flash version of the App editing function will be discontinued
• Check out also the plans of changes in future versions [Plans of Future Changes] at the bottom of this page.

---

Details for Version 11.13

(★: Appended on January 14, 2020)

Changes of Functions for Normal User

Workflow

• Change the design of Workflow diagram (Status) displayed on the Process details screen
  • Single-color display instead of gradation
  • Changed Swimlane colors and icons
  • Normal swimlane and team swimlane colors are unified
  • Match the label text color of the ReceiveTtask (Form) with the color seen in Process Modeler
• Changed the display of the token on the Workflow diagram displayed on the Process details screen
  • Enlarged for easy-to-find its location
  • Added color-coding for “running” and “finished (normal end / abend)”
• Fixed following Bugs:
  • When the Process details are opened from My Tasks, etc., the Task highlighted in Operation History is not highlighted on the Workflow diagram

Changes of Functions for Workflow Designer

• Added official item for data processing
  • Converter (Table-type data to Excel-CSV File)
  • Converter (Excel-CSV File to Table-type data)★
  • Generator (Text file)★
• Process Modeler used for App editing become switchable between HTML5 version and Flash version
  • You can switch for each Workflow App unless there is an error
  • With this release (version upgrade to Ver. 11.13), the existing Workflow App will be set to use the Flash version
  • When creating by New App or New App from Archive, you can select a modeler to use
  • When duplicating an App, the modeler settings used in the original Workflow App are inherited
  • The workflow diagram (Status) displayed on the Process Detail screen is the same type of the Process Modeler (HTML5 / Flash) selected at the App edit★
• In the HTML5 version, the name of a Workflow App is shown★
• In the HTML5 version, if an App contains an error in the setting of workflow diagram/Data Item, it will be displayed on the respective tab
• The HTML5 version will not support IE11
• Fixed the background color of the version list table on the App details screen★

Workflow Diagram

• Improved flow connectivity check of workflow diagrams so that faster processing★
• For the HTML5 version ;
  • Added error message when trying to place nodes/swimlane/annotations beyond the system limit
    • Nodes (150), Swimlanes (50), Annotations (100)
  • Change the design of the Workflow diagram
  • Become possible to change node size (Normal/Large/X-large)
    • Flash version is also available in the Size setting in Preference
  • On Swimlanes, display the name label also on the right end★
  • A completion message such as “Succeeded to add node” is now displayed★
  • An error is displayed immediately on the workflow diagram when a setting error occurs in a node/swimlane due to a change in the Data Item setting★
  • When displaying an error, changed display location of error message★
  • Enhanced the checking for simultaneous editing on Apps by multiple Users/browsers★
  • Reduced unnecessary communication processing so that improve performance

Service Task (Data Assignment)

• Individual outputting of Name/Email address/ID when inserting User-type/Organization-type Data Item become possible
  • E.g. #{#q_user?.name} , #{#q_user?.getEmail()}
• Outputting the value of each cell when inserting a Table-type Data Item become possible
  • E.g. #{#q_table?.get(0, 3)} , #{#q_table?.getSummary()?.getCol(3)}
• Individual outputting Choice ID when inserting Select-type Data Item become possible
  • E.g. #{#q_selects?.get(0)?.value} (the first choice ID),#{#q_selects?.get(1)?.getDisplay()} (the secong choice label)
• The delimiter is changed from ” (space)” to “, (comma)” when multiple choices output in Select-type Data Item (Check Box)
• Reference to the object of the Start User/Start Organization become possible
  • E.g. #{processInstanceInitQuser.getEmail()} , #{processInstanceInitQgroup.getEmail()}
• Added a method (#join) to join the elements (mainly lists) by specifying a separator★
• Added a constant (#NL) that represents a line feed code (\n)★
• Selection of Data Items for which “field name” is not set becomes unavailable for selecting in Data Reference (input helper of EL expression)
  • Please operate after setting “field name” (required item) when referring to Data Items
• When the “variable” of the App is updated, it is immediately reflected in the “EL input helper”★
• “Value or Expression” dialog screen in HTML5 version now displays the Data Items name to be set
• Addressed an issue where could not save the App if trying to use some XML tags in settings★

//Example of join method
#{
  #join(
    #q_table?.rows?.![
      #join(cols, ' | ')
    ],
    #NL)
}

//Output example
1-1 | 1-2 | 1-3
2-1 | 2-2 | 2-3

Service Task (Google Drive: File Upload)

• Abolished the method with folder path for specifying the upload destination folder
  • If the method for specifying with the folder path remains, the setting is automatically changed to “Specify by folder ID” and “ID is blank (unspecified)”
  • When actually running, the file will be uploaded directly under My Drive of “User who connects to Google Drive”
  • You can do the same as with folder path by uploading a file after creating a folder with “Service Task (Google Drive: Create Folder)”

Service Task (Box: Create Folder)

• Correspond not to become script error when an error that the same name folder exists

Service Task (Add-on)

• On the setting screen, improved the display that indicates “Nothing to select” in the field specified by form-type =”SELECT”★

Message Start Event (Email)

• To the Subject setting field, added a message of “This will be put into title of the Process”★

Message Sater Event/Receive Task (Webhook)

• Added a button to copy the URL to the clipboard on the HTML5 version property screen

Receive Task (Form)

• Fixed following Bugs:
  • When there is a Data Item which has been set both to “No display” and to smaller column size, the layout may not be displayed correctly
    • Displayed with a different layout on the actual Operating screen even while preview display is correct

Throwing Message Intermediate Event (Email)

• Unified the format for embedding data to the same one as for referencing data in “Service Task (Data Assignment)”
  • For Data Items, use Field Name
  • The same as the format that can be set to String-type Data Item in Service Task (Data Assignment)
  • The same formulas used in the Service Task (Data Assignment) are available
• If there is a reference to a deleted Data Item, processing will fail when the event is executed

Throwing Message Intermediate Event (HTTP)

• When “Access URL” of “Message Start/Catching Message Intermediate Event (HTTP) on the same Workflow platform is in the deprecated URL format (request parameter)”, setting error will occur
  • No error occurs if another Workflow platform URL is specified
• Fixed following Bugs:
  • An error occurs when trying to search by entering the Base URL of the accessing server after selecting Connect to Event in the outside server in [Connecting to Message Start / Catching Message Intermediate Event (HTTP)]★

Message Start Event/Receive Task (Webhook)

• Added a button to copy the URL to the clipboard on the HTML5 version property screen

Gateway

• The followings are done on the HTML5 version
  • Design adjustment of setting dialog of Split condition setting
  • While the setting dialog is displayed, it does not close even if you click outside the dialog

Annotation

• Set an upper limit for the number of text characters (256 characters)
• In the HTML5 version, Annotation on workflow diagram becomes moveable★

Data Items

• Field names become required
  • Not applicable for Guide Panel-type
  • If blank it will be automatically given at the time of this release (version upgrade to Ver. 11.13)
• To Numeric-type an upper limit on the number of prefix/suffix characters is set (20 characters)
• Becomes an error when trying to add a Data Item that exceeds the number of system limit
  • Up to 300 including Title
• The followings are done on the HTML5 version
  • Multiple Data Items batch addition become available
    • By Specifying a CSV (TSV) file containing 4 items of Item name/Field name/Data-type/Required
  • Changed the addition method of Data Items to selection from menu palette
  • Added confirmation dialog when deleting data items
  • Delete (Trash)icon is not to be displayed when multiple Data Items are focused★
  • Added the columns setting button also to group of buttons displayed when the Data Item is focused on the Items list★
  • Form Preview becomes available also from Data Items setting screen★
  • Add a link to help page to each Data-type
  • Fixed following Bugs:
    • In the Choice setting of the Select-type Data Item, the content being edited may not be reflected

Changes of Functions for System Administrator

• In the display of System Authorization etc., the background color becomes alternatively between even and odd rows in the table★
• Fixed following Bugs:
  • Automatic Processing Log may not be displayed on the detail page of Incoming HTTP – Message Start Event (HTTP), etc. in [App External Connectivity]★

Changes of Functions for System Engineer

• [Advance notice] In the API (/API/OR/ProcessInstance/listCsv) that retrieves the process search results in CSV format, add the “Node name where the token is staying” to the output item★
  • You will be able to realize automated processing according to the token position, etc.
  • If you are performing data processing that depends on the column order of the data (CSV) acquired by the API, it may be necessary to modify

Non-functional Changes and Changes of External tool Functions

• At the same time as Microsoft ends support for Windows7 (January 14, 2020), Questetra will also end support for Windows7

---

Plans of Future Changes

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

Schedule for April 2020

• For “Message Start Event (HTTP / Form)”, “Catching Message Itermediate Event (HTTP)”, we will abolish the following form of URL which includes processModelInfoId / nodeNumber and key (“Form” only) in the request parameter
  • 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
  • If “Throwing Message Intermediate Event (HTTP)” on the same Workflow platform is the sender, a setting error will occur if the URL in the request parameter format is specified
  • If “Script Task” on the same Workflow platform or HTTP request from an external environment is the sender, the deprecated URL format cannot be detected on the workflow platform. Please confirm and correspond individually.
  • For users (Business Plans) whose transmission has been detected API request in the deprecated form, we have been sending guidance asking for correction individually (Ocober, November, December)
• Flash version of the App editing function will be discontinued
• In the API (/API/OR/ProcessInstance/listCsv) that retrieves the process search results in CSV format, add the “Node name where the token is staying” to the output item
  • If you are performing data processing that depends on the column order of the data (CSV) acquired by the API, it may be necessary to modify

Schedule for July 2020

• For the APIs of “Querying for all Process Instances records” and “Querying for Task records operated by the User”, change to explicitly specify to include Data Items as display items in search results
  • Currently, Data Items specified as search conditions are automatically included also in search results
  • After the specification change, only Data Items for which the element is specified will be included in the search results

Schedule for January 2021

• In the “Script Task” and “Service task (Add-on)”, we will abolish the data retrieving/updating method of the following format
  • 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)

---