v11.12 2019-10-07 Set an Upper Limit on the Number of Options Displayed

Release Overview

Date Release

Changes to be Noted

  • When the sub-type of Select type is “radio button/select box/check box”, an upper limit will be applied for the number of items displayed on the Task Operating screen (Displays up to 1000 items)
  • In [Throwing Message Intermediate Event (HTTP)], corresponding so that “variables” cannot be used when OAuth2 is specified in the security settings
  • [Notice: Scheduled for Jan. 2020] “Field name” of Data Item will become a required item
  • [Notice] For the new App editing function (HTML / Javascript version), IE11 will not be supported
  • [Notice] At the same time as Microsoft ends support for Windows7 (January 14, 2020), Questetra will also end support for Windows7
  • Check out also the plans of changes in future versions [Plans of Future Changes] at the bottom of this page

Details for Version 11.12

Changes of Functions for Normal User

  • Set padding at the beginning of the input field for String-type Data Items
  • Introduced a cache mechanism for counting of [Last month] [This month] of “Performance Check” to improve performance

Changes of Functions for Workflow Designer

  • Added the following items that can be connected with cloud services as the standard
    • Seervice Task (Box: Search Folder)
    • Seervice Task (Box: Delete Folder)
    • Seervice Task (Box: Create Shared Link to Folder)
  • Renamed “Service Task (Google Drive: Delete File)” to “Service Task (Google Drive: Delete File / Folder)”
  • Corresponding to the following connection and arrangement in the Workflow Diagram
    • Allow one node to connect to multiple “End Events”
    • Allow “End Event” and connected nodes to be placed on different Swimlanes
    • Allow Start Event other than the normal type (such as a “Message Start Event”) and the node connected to it to be placed on a separate Swimlane
  • Corresponding to the setting of the operator of a Swimlane where the normal “Start Event” is placed so that relative designation with another Swimlane can be specified
    • If the Operator setting is relative only, the Process cannot be started from this Start Event
  • Changed the markup processor for “Work Manual”
    • There are possibilities that the display may change
  • Corresponding not to delete debug Process when saving Workflow App
    • The debug Process is deleted when a new version is [Released]
  • Fixed following Bugs:
    • Upon the deadline of a Human Task, the processing for moving the token to Boundary Event may not proceed
      • Corresponding so that automatically to process again when token processing stops
    • It may be possible to [Release] even though errors remain on the App editing screen

Throwing Message Intermediate Event (HTTP)

  • Corresponding so that “variables” cannot be used when OAuth2 is specified in the security settings
    • Please change your settings since a setting error occurs if “Variable” is used in Ver. on and after 11.9
  • Corresponding so that error details are displayed in case of authorization error when getting token in OAuth2 setting

Annotation

  • Fixed following Bugs:
    • Blank lines/single-byte spaces in Annotations are disregarded in Workflow diagram on the Process details page
    • In the Workflow diagram on a Process details page, if there are Annotations which its text is empty, other Annotations may not be displayed

Data Itms

  • When the sub-type of Select type is “radio button/select box/check box”, an upper limit will be applied for the number of items displayed on the Task Operating screen
    • Do not display more than 1000 choices
    • If there are more than 1000 choices, use Search Select
    • Be careful when defining choices via HTTP or using Options Master (XML)
  • Added a check regarding the length of the initial value in the Title/String-type Data Item
    • Title: 256 characters
    • String-type Data Item: 8000 characters
  • [Notice] “Field name” of Data Item will become a required item (Scheduled for Jan. 2020)
    • If it is empty, it will be set automatically when releasing the new version of Questetra BPM Suite in January 2020

Variables

  • Fixed following Bugs:
    • The message “Do you want to save with the error remaining?” is not displayed when saving the App even if there is an error in the variable settings

App editing function (Modeler)/App settings property

  • As a preview version, releasing new App editing function (HTML5 Modeler) which uses HTML/Javascript
    • It can be used until version 1 of a creating new App is released
  • You can continue to use the current Flash version
  • We plan to make a complete transition from Flash version to HTML/Javascript version in the first half of 2020
  • [Notice] IE11 will not be supported in HTML/Javascript version

Non-functional Changes and Changes of External tool Functions


Plans of Future Changes

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

Schedule for January 2020

  • In Service Task (Google Drive: Upload File), for the upload destination folder, specifying with the folder path will be discontinued in the future version
    • You can do the same by uploading files after creating a folder by “Service Task (Google Drive: Create Folder)”
  • 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
    • 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
  • “Field name” of Data Item will become a required item (Scheduled for Jan. 2020)
    • If it is empty, it will be set automatically when releasing the new version of Questetra BPM Suite in January 2020
  • At the same time as Microsoft ends support for Windows7 (January 14, 2020), Questetra will also end support for Windows7

Scheduled for June 2020

  • 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 element is specified will be included in the search results

Scheduled for January 2021

  • In the “Script task” and “Service task (Add-on)”, we will abolish data retrieving / updating method of the following format. (on and after July 2019)
    • 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)
  • 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 element is specified will be included in the search results

%d bloggers like this: