2023-12-17 Ver 15.2 Enable Define Position and to be Specified for Organizational Affiliation

Release Overview

Updating Date

• Workflow platform for Rapid Update:
  • Version 15.2.0: December 17th, 2023 (Sun)
  • Version 15.2.1: [TBD] January 21st, 2024 (Sun) or 28th
• Workflow platform for Scheduled Update and Trial mode
  • Version 15.2.0：Not updated
    • Updated to Version 15.1.2 on December 17th, 2023 (Sun)
  • Version 15.2.1: [TBD] January 21st, 2024 (Sun) or 28th

Changes to be Noted

• You will be able to freely define the Job Title to be specified when assigning a User to an Organization
  • The existing “Leader” position will be treated as one of the Job Titles (it will be automatically migrated when updating)
• Task processing API will be renewed
  • Adds new Task Processing API targeting field name parameters only
  • Two existing APIs for retrieving Form screens and processing Tasks will be deprecated
• Content negotiation will now be performed in [Message Start Event/Catching Message Intermediate Event (HTTP)]
• The Java library (swagger-java-client) for accessing the Questetra REST API will be deprecated
• The old format URL will be deprecated in [Message Start Event (Form)]
• In [Message Start Event/Catching Message Intermediate Event (HTTP)], old format reception parameters including data definition number will be deprecated
• The “!Organization name” format (specifying the leader) in CSV for [Bulk User Registration] will be deprecated
• In the Script Task, the method that returns a list of Users and the Organizations to which they belong as leaders/staff will be deprecated
• In the Membership API of the Questetra REST API, the request parameter role and the role property included in the response will be deprecated
• Check out the plans for changes in future versions [Plans of Future Changes] at the bottom of this page

---

Details for Version 15.2.0

($.: Appended 2023-12-18, $$.: Appended 2023-12-25)

Changes of Functions for All Users

• Fixed the following Bugs:
  • In the user name display at the top right of the screen, if the user name is long, it may overlap with other display elements depending on the window width (#9503)
  • On the error page of [Message Start Event (Form)], there are cases where two quotation-marks (‘) are displayed in English messages (#9550)

Workflow

Process Start/Process Details

• In [Bulk Start], the error message that is displayed when a User cannot start a Process is unified with that of the normal Process [Start] (#9499)
• Added displaying Titles (*described later) in the Position column on the App details screen in [Start] (#9516)
  • Changed to display Title instead of Leader or Staff
• Fixed the following Bugs:
  • On the Process details screen, if the Step name is long, it is displayed outside the display area (#9478)

Task Operation

• $. Set the upper limit of the number of Tasks that can be selected in [Execute selected tasks sequentially] to 100 (#9585)
• Fixed the following Bugs:
  • If there is an input error in the Title Data Item, two error messages are displayed at the top and bottom of the input field (#9365)
  • On the Task Operating screen for smartphones, if the App name/Step name/Organization name/User name is long, it will be displayed outside the display area (#9479)

Open Chat

• Liked posts are now displayed on the timeline (#9298)
  • Although posts from Users you don’t follow won’t be displayed on your timeline, posts you’ve liked will be displayed

Account Settings

• [Profile] now displays the position in an organization that you belong to (#9514)

Changes of Functions for Workflow Designer

• $. Improved workflow engine (#9582)

New App

• When creating a [New App from Archive], it is now possible to change the Title referenced in the App definition (#9497)
  • Re-assigning (specifying) Titles is possible in the same way as Users/Organizations/Roles

Data Item/Questetra Form JavaScript API

• When using [Bulk Update Data Editing Permission], if the specified file has only a header line (no update data), the message “Updated” will no longer be displayed (#9451)
  • If the specified update data is the same as the existing setting value, the setting value will not be changed but the message “Updated” will be displayed
• Upgraded jQuery from 3.6.4 to 3.7.1 (#9308)
• Fixed the following Bugs:
  • When retrieving a Table-type Data item in the Questetra Form JavaScript API, if the value is unset and “editable”, a List object with 1 row is returned (#9431)
    • According to the specifications (documentation), it is correct to return an empty List object (with 0 rows)
  • In the Questetra Form JavaScript API, child choices are not updated even if the parent value is updated in a dependent Select-type Data Item (#9566)

Operator

• When specifying an Operator by selecting Organization/Data Item/Swim lane, it is now possible to specify the Position (#9469)
  • You can specify one from 4 patterns: [Unspecified (regardless of Position)], [With Position (any Position)], [No Position], [Specific Position (specify individual Position)]

Add-on Manage

• When updating an existing add-on, a warning will now be displayed if the registered name and the file name you are trying to upload do not match (#9347)
  • The purpose is to prevent the file from being overwritten by the wrong file
  • A warning message will be displayed, but you can continue to overwrite it
• $. Logs are now output to [Process Log] when add-ons are added/updated/deleted (#9386)

Terminate End Event

• Added help button (link to help page) (#9423)

Human Task/Message Start Event (Form)/Receive Task (Form)

• Changed internal implementation (library used) of form screen/form preview screen (##9213, #9215, #9217)
• Old format URL in Message Start Event (Form) is now deprecated (#9481)
  • Old format URL: /System/Event/MessageStartForm/view
  • Until discontinuation, it will be redirected to the current format URL
  • Will be discontinued in Version 17.0 (April or May 2025)

Throwing Message Intermediate Event (email)

• $$. A DKIM signature in the questetra.net domain is now added to all outgoing emails
  • If the sender (From address) is the default, it will be a “First Party Signature”
  • If the sender (From address) has been changed, it becomes a “Third Party Signature”

Gateway/Split by Task peration

• Added the following comparison condition to the Split condition that specifies a User-type Data Item (#9482)
  • [is equal to], [is not equal to], [is the member of the organization of], [is the member of the PARENT organization of], [is the member of any CHILD organization of], [is the member of any UPPER organization of], [is the member of any LOWER organization of], [is the member of the role of]
  • User-type Data Items/Process Start Users can be specified as the comparison target of the comparison condition (#9477)
  • Conditions for determining affiliation to an organization, such as “belongs to a specified organization,” can be specified using Position
    • [Unspecified (regardless of Position)], [With Position (any Position)], [No Position], [Specific Position (specify individual Position)]
• Added the following comparison condition to the Split condition that specifies a Organization-type Data Item (#9366)
  • [is equal to], [is not equal to], [is the member of the organization of], [is the PARENT organization of], [is the CHILD organization of], [is the UPPER organization of], [is the LOWER organization of]
  • Organization-type Data Items/Process Start Organization can be specified as the comparison target of the comparison condition (#9477)
• Added the condition “matches the regular expression” to the Split condition that specifies the Title/String-type Data Item (#9531)
• Improved the display and error message in specifying Split conditions when there are incorrect settings such as the comparison target value not being set (#9471)
• Fixed the following Bugs:
  • When specifying a conditional expression using SpEL expression, error details may not be displayed if the conditional expression is invalid (#9461)

SpEL in Update Data or Split /Script Task

• [Update Data] now supports updating the values of User-type/Organization-type Data Items (#9339)
  • If the evaluation result of the SpEL is String, it is assumed to be the User’s email address/Organization name and overwritten
  • If the SpEL evaluation result is QuserView/QgroupView, it will be overwritten with that User/Organization
  • In SpEL, quserDao, qgroupDao, and qroleDao objects can now be used
    • e.g. #qgroupDao.findPrimaryQgroup(#q_user): Update with the Organization to which the User specified in the User-type Data Item (#q_user) mainly belongs
      • If you specify to update the Organization-type Data Item with this SpEL in [Update Data], the Organization-type Data Item will be overwritten with the Organization to which the specified User mainly belongs
  • If a specific user is specified, it will always be overwritten with that User/Organization (#9545)
• Added the following methods to QuserDao
  • Method to determine whether a specified User belongs to a specified Organization or Role: isMemberOfQgroup(QuserView, QgroupView), etc. (#9483)
  • Search by title: findMembersOfQgroup(QgroupView), etc. (#9486)
  • Search with query: findByQuery(String)(#9500)
• Added the following methods to QgroupDao
  • Determine the ancestor/descendant relationship of an Organization: isParentOf(QgroupView parent, QgroupView child), etc. (#9455)
  • Search ancestor/child/descendant Organizations: findChildQgroups(QgroupView parent), etc. (#9490)
  • Search by job title: findByQuser(QuserView, boolean), etc. (#9501)
  • Search with query: findByQuery(String), (#9500)
• Added the following methods to QroleDao
  • Search with query: findByQuery(String) (#9500)
• Added the following methods to QuserView/QgroupView
  • Determine whether a User/Organization has been deleted: isDeleted() (#9488)
    • Mostly used to determine whether Users/Organizations recorded in past Process Data Items have been deleted
    • QuserDao/QgroupDao cannot search for deleted Users/Organizations
• Added QtitleDao, a class to search for Title (#9485)
  • Can be used as qtitleDao in Script Tasks, and #qtitleDao in SpEL
  • findById(long): Search by ID, findByName(String) : Search by name, findByQuery(String): Query search
• Corrected QuserDao/QgroupDao/QroleDao methods so that they do not return an exception (NullPointerException) even if the argument is null (#9484)
  • Changed to return null or empty list
• $. When accessing Table-type Data Items, no error will occur even if the specified row does not exist (#9242)
  • Null is returned instead of occurrence of error
• In the workflow diagram displayed on the App details screen, the [Delete] button is now displayed as inactive on the settings screen for the [Update Data] step (#9570)
  • Though it does not work the button was clickable

Automatic Processing Steps that Cooperate with other Cloud Services/Processing Data

• Added the following automated processing steps (Service Task)
  • Microsoft 365
    • Outlook
      • Start: Microsoft 365 Outlook for Business: Email Received (#9428)
        • Receiving an Outlook email starts a new Process
      • Microsoft 365 Outlook for Business: Get Email Message (#9428)
        • Get the source of the email specified by ID, parse the body/attachments, etc., and save them in Data Items
      • Microsoft 365 Outlook for Business: Remove Category from Email (#9439)
        • Remove categories from Outlook emails
    • OneDrive for Business
      • Start: Microsoft 365 OneDrive for Business: File Uploaded (#9533)
        • Start a Process when a file is uploaded to a specified folder in OneDrive
      • Microsoft 365 OneDrive for Business: Download File (#9440)
        • Download the specified file in OneDrive
      • Microsoft 365 OneDrive for Business: Create Sharing Link (#9480)
        • Create a URL to a specified file/folder in OneDrive and make it visible to anyone with the link
      • Microsoft 365 OneDrive for Business: Delete Sharing Link (#9480)
        • Delete the specified shared link from the specified file/folder in OneDrive
      • Microsoft 365 OneDrive for Business: Move File / Folder (#9520)
        • Move specified files/folders in OneDrive
  • Box
    • Box: Cancel Sign Request (#9416)
      • Forcibly cancel a signing request
      • (Even if you delete the Box file for the sign request, the sign request will not be canceled)
  • Slack
    • Slack: Get User ID (#9372)
      • Get a Slack user ID by a Questetra User or an email address
    • Slack: Get User Name (#9382)
      • Get Slack username and email address by Slack user ID
  • Twilio SendGrid
    • Twilio SendGrid: Send Email (#9373)
      • Send an email by specifying To/Cc/Bcc and email body
      • In addition to the functions of [Throwing Message Intermediate Event (email)], you can achieve the following:
        • You can confirm that the email has been opened
        • You can embed inline images in HTML emails
  • Trello
    • Trello: Create Card (#9346)
      • Create a new card
    • Trello: Get List ID (#9419)
      • Get ID by list name
    • Trello: Get Label ID (#9430)
      • Get ID by label name
    • Trello: Get Member ID (#9438)
      • Get ID by member name
  • WordPress.com
    • WordPress.com: Publish Post (#9556)
      • Publish a draft article on WordPress.com
  • $. Amazon Web Services
    • $. Amazon Bedrock: Anthropic Claude: Chat (#9587)
      • Sends messages to Anthropic Claude’s model running on Amazon Bedrock and saves answers
    • $. Amazon Bedrock: Stable Diffusion: Generate Image (#9589)
      • Generates images using Stability AI’s Stable Diffusion running on Amazon Bedrock
    • $. Amazon S3: Upload File (#9590)
      • Uploads files to a specified folder in Amazon S3
    • $. Amazon S3: Download File (#9591)
      • Downloads the file specified by the object key from Amazon S3
  • $. OpenAI
    • $. OpenAI DALL-E: Generate Image (#9588)
      • Generates images using OpenAI DALL-E
• Changed specifications, internal implementations or fixed bugs in the following automated processing Steps (Service Tasks)
  • Box
    • Start: Box: File Uploaded (#9434)
      • Changed internal implementation
    • Box: Delete File (#9452)
      • Changed internal implementation
    • Box: Cancel Sign Request (#9383)
      • The expiration date (number of days until the deadline) can now be specified
      • Changed the timing of auto-step completion from “Signed” to “the sign request email sent”
  • kintone
    • kintone: Search Records (#9316)
      • Limited the Authorization setting type to Token Fixed Value
    • kintone: Upload File (#9317)
      • Limited the Authorization setting type to Token Fixed Value
    • kintone: Download File (#9318)
      • Limited the Authorization setting type to Token Fixed Value
  • Slack
    • Slack: Post Message (Block Kit supported) (#9441)
      • It is now possible to select and configure the Slack app registered by Questetra (used for [Slack: Chat Post (Bots)] and [Slack: File Uploading (Bots)])
  • Twilio SendGrid
    • Twilio SendGrid: Send Bulk Email (#9512)
      • When using SendGrid Design (email templates), the categories set in Design are now inherited as the category of the delivered email
      • $$. Changed the layout of the Settings screen
  • OpenAI
    • OpenAI ChatGPT: Chat (#9562)
      • OpenAI organization (OpenAI-Organization header) can now be specified
      • Added “gpt-4-32k” to model options
      • Any model can now be specified in a text input
      • The upper limit of the number of tokens (max_tokens) can now be specified
      • Image files can now be specified to input
      • Works only when [gpt-4-vision-preview] is specified as input in [model]
  • $. Microsoft 365 OneDrive
    • $. Microsoft 365 OneDrive for Business: Copy File / Folder

Message Start Event/Catching Message Start Event (HTTP)

• Old-style reception parameters including data definition numbers (data[XX].input, etc.) is now deprecated (#9390)
  • Scheduled to be discontinued in Version 18.0 (April 2026)
  • Changes are required on the HTTP request sender side
• A warning message is now output to the Process log when old format reception parameters are used (#9391)
  • Output only when an event processing ends normally
• The list of [Process logs] (automatic processing logs) for the event is now displayed from the event settings screen (#9437)
• Numeric-type Data Items in which an arithmetic expression has been set cannot now be set to Editable (#9435)
  • When updating to Version 15.2, the setting will be automatically migrated from Editable to No display (#9456)
• If a file is already attached to a File-type Data Item that is set as Required, a mandatory error will not occur even if the parameter of the File-type Data Item is not received in [Catching Message Intermediate Event (HTTP)]
• When the size of an HTTP request received with multipart/form-data exceeds 100 MB, it now returns 413 status code (#9569)
  • Until Version 15.1, the status code was 400, and the error HTML was returned
  • On and after Version 15.2, the status code is 413, and the response body is empty
  • This is a common response for all processes that receive HTTP requests in multipart/form-data, such as Task processing APIs
• $. Content negotiation is now performed during HTTP communication (#9218)
  • When specifying the Accept header, please set it to allow “text/plain”
  • If a method other than POST is specified or an incorrect Accept header is specified, the request will fail
• Fixed the following Bugs:
  • The [Data Visibility from Parent Process] button is displayed in [Catching Message Intermediate Event (HTTP)]

Script Task

• Decoding from Base64 to binary even in formats that are not URL Safe is now supported (#9392)
• Added decodeFromStringToByteArray(String) method to Base64UtilsWrapper
  • RFC 4648: Base64 Encoding is now supported
• Fixed the following Bugs:
  • Changes in the display order may not be reflected correctly in setting header/sending parameters (#9221)

Throwing Message Intermediate Event (HTTP)/Script Task HttpClient

• Added the following headers to the allowed list in [Custom HTTP Headers]
  • “Prefer” (#9415)
  • $$.: Notion-Version (#9600)
• When the sent HTTP request is redirected, the Authorization header is now included to the redirect destination (#9474)

Changes of Functions for Questetra REST API Developer

• Added APIs to collectively specify and update members for each Organization/Role (#9154)
  • /API/UGA/Membership/set, /API/UGA/RoleMembership/set
  • Specify in JSON format in request body
  • Changes are made all at once to make users belong to the specified Organization/Role
  • Regarding Organization (Membership), it is also possible to specify the Position
  • The maximum number of affiliated users that can be specified at once is 10,000, and if the number of affiliated users already exceeds 10,000 in an Organization/Role, a 400 error will occur
• Set the upper limit to 1000 for APIs that retrieve User list, etc. (#9417)
• Support for job titles in Membership API (#9463)
  • Added parameter qtitleId to specify title ID in add/update
  • Response now includes Title ID and Job Title
  • Request parameter role and role property included in response is now deprecated (Ver. 18.0)
    • Until the discontinuation, it will be treated as follows:
      • The request parameter role = _leader operates as if the role ID = 1 (initial name is “Leader”) is specified
      • role in the response property means that the user holds one of the positions
      • Immediately after updating to Version 15.2, the behavior is the same as up to Version 15.1, but If the role with “Job ID = 1” is deleted or the name is changed from “Leader”, the behavior will change
• Added support for searching by qtitleId in /API/User/Membership/list (#9492)
  • Search by job ID across organizations
• $. Added API to reference job titles (#9462)
  • /API/User/Qtitle/find: Returns the position that matches Position ID (id) or Job title (name)
  • /API/User/Qtitle/list: Returns a list of Positions that meet the search criteria
• $. Position (qtitleId parameter) is now supported in API that adds System privileges/App privileges (#9513)
  • /API/Admin/SystemAuthority/addToQgroup, /API/Admin/ProcessAuthority/addToQgroup
• Added new Task processing API targeting field name parameters only (#9422)
  • /API/PE/Workitem/{workitemId}/Form/save
  • Parameters are specified by the field name of the Data Item
  • Parameters using data definition numbers (such as data[XX].input) are not supported
  • 400 is returned on validation error
• Unify the error response when a workitemId that cannot be processed is specified in the two APIs related to Task processing (#9378)
  • /API/PE/Workitem/Form/viewXml, /API/PE/Workitem/Form/save
• Corrected so that error HTML is not returned for requests to Questetra REST API (#9532)
• Internal implementation changes for the following APIs:
  • Task processing: /API/PE/Workitem/Form/viewXml, /API/PE/Workitem/Form/save (#9214)
• Discontinuation of Task processing API
  • Scheduled to be discontinued in Version 17.0 (April 2025): /API/PE/Workitem/Form/viewXml (#9421)
  • Scheduled to be discontinued in Version 18.0 (April 2026): /API/PE/Workitem/Form/save (#9422)
  • Please use /API/OR/ProcessInstance/view to obtain Process detailed data regarding Data Items etc. required when executing Task processing
• Deprecated Java library (swagger-java-client) for accessing Questetra REST API (ends support) (#9384)
• Fixed the following Bugs:
  • In the task processing API, a validation error may occur even though a Numeric-type Data item with an arithmetic expression does not receive a parameter value (#9436)

Changes of Functions for System Administrator

• Added support for defining Position alongside Organization/Role (#9197)
  • Position is a common item throughout the workflow platform (likewise Organization or Role)
  • When you assign a User to an Organization, you can select one Position
    • For example, Mr. Smith can be set to 'belong to the sales department as manager', 'belong to the marketing department as section manager', and 'belong to the development department as (no title)'
  • Added display of a list of Users in this Position on the Title Details page (#9491)
  • The following correspondence will be implemented with the update to Version 15.2
    • The Positions ‘Position ID = 1’, and ‘Name = Leader’ are automatically registered
    • Regarding belonging to an Organization, belonging as Leader will be converted to a Position with “Position ID = 1”, and belonging as Staff will be converted to belonging as “(No title)”
• In [Bulk User Registration] by CSV input, Position can now be specified (#9465)
  • In the 4th column onward, specify the Position when belonging to the Organization by writing ‘Organization name!!Title name’
  • The format “!Organization name”, up to Version 15.1, that specifies the affiliation as Leader is treated as belonging to the Position with “Position ID = 1”
    • The format of “!Organization name” will be discontinued in Version 17.0 (#9542)
• The CSV file downloaded from the User list now includes the Position (#9467)
• Positions are now supported in System Authorization/App Authorization
  • Conditions related to position can now be specified when granting permissions to Users belonging to a specific Organization
    • You can specify one from 4 patterns: [Unspecified (regardless of Position)], [With Position (any Position)], [No Position], [Specific Position (specify individual Position)]
• The warning when there is an Organization without a leader/member is no longer displayed on the [System Settings] screen (#9551)
  • As a response to introducing Positions
  • Only the error message “User who does not belong to any Organization” continues to be displayed
• An error page will now be displayed when IP address filter rejects (#9327)
  • Targets pages that Users view after logging in (authenticated)

Non-functional Changes and Changes of External tool Functions

• $. Improved parallel access (request) processing by the same user (#9524)

---

Details for Version 15.2.1

Changes of Functions for All Users

Open Chat

• Fixed the following Bugs:
  • Old post messages from around 2011 or earlier are not displayed (#9631)

Changes of Functions for Workflow Designer

Message Start Event/Catching Message Start Event (HTTP)

• Fixed the following Bugs:
  • If content negotiation fails during HTTP reception, 500 is returned (#9627)
    • 406 is now returned

Automatic Processing Steps that Cooperate with other Cloud Services/Processing Data

• Changed specifications, internal implementations or fixed bugs in the following automated processing steps (Service Tasks)
  • WordPress.com
    • WordPress.com: Publish Post (#9645)
      • Changed the scope of OAuth2 Authorization setting

Changes of Functions for System Administrator

• Fixed the following Bugs:
  • The notation “Leaders or staff members of” remains on the screen for granting new System Authorization / App Authorization  (#9659)

Non-functional Changes and Changes of External tool Functions

• Improved parallel access (request) processing by the same user (#9622)

---

Details for Version 15.2.2

(appended 2024-04-08, $. appended 2024-04-12, $$. appended 2024-04-23)

Changes of Functions for All Users

• Fixed the following Bugs
  • $.The Side menus of [Get Started] and [Samples] are not displayed (#9881)

Changes of Functions for Workflow Designer

Edit App

• Fixed the following Bugs
  • Deleting swim lanes or [Debug only this node] operation may result in an error (#9870)

Automatic Processing Steps that Cooperate with other Cloud Services/Processing Data

• Fixed Bugs in the following Auto-step (Service Task)
  • Google
    • Google Sheets: Append New Row (#9775)
      • Fixed an issue where an error could occur depending on the sheet title

Changes of Functions for System Administrator

• Fixed the following Bugs
  • In the system log, log type labels related to Positions are not displayed correctly (#9845)
  • In the system log, there is an error in the log type label in English (#9849)

Changes of Functions for Questetra REST API Developer

• Fixed the following Bugs
  • When using the API (/API/User/SystemAuthority/self) to acquire system authority held by the user, the response contains multiple identical authorities (#9871)

Non-functional Changes and Changes of External tool Functions

Questetra My Tasks (Google Chrome extension)

• Fixed the following Bugs
  • $$. New Tasks are not notified in the Chrome extension [Questetra My Tasks]
  • $$. There may be new Tasks that are not notified as new items (#9878)

---

Plans for Future Changes

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

Schedule for Version 16.0 (April 2024)

• The script engine GraalJS (new name: GraalJS (Nashorn Compatible Mode)) will be discontinued in scripts of Script Tasks/Service Tasks (Add-on)
  • It will be forced transition to GraalJS (Standard Mode)
  • Due to the migration of the script engine, if the following methods/properties are used, the operation specifications will be changed (*postponed from April 2023)
    • String#equals() method
      • Please change to a code that uses “===” or “==”
      • The equals() is a method of java.lang.String. Avoid using methods derived from java.lang.String, as the String class tends to support JavaScript Strings
    • Error#message property
      • Change to a code that uses Error#toString()
      • java.lang.Throwable, the entity of the Error object, does not have a message property. Use the toString() method defined in both JavaScript Error and java.lang.Throwable
  • Script Engine GraalJS (Nashorn Compatible Mode) Discontinued (April 2024)
• For scripts in Script Task/Service Task (Add-on), deprecated APIs (Java classes/methods) will be discontinued
  • A warning message will be output in the Process log when a deprecated API is executed
  • You can check the target App and Process by searching for “Only logs with warnings” in [Process Log]
  • Targets: APIs marked as “deprecated: 2024-04” in R2300: Java Classes available in Script Task
• The format using the parameter activityId in the API that starts a Process (/API/PE/ProcessInstance/start) will be discontinued

Schedule for Version 17.0 (April 2025)

• Old format URL in Message Start Event (Form) will be discontinued
  • Old format URL: /System/Event/MessageStartForm/view
  • Until discontinuation, it will be redirected to the current format URL
• In [Bulk User Registration] by CSV input, the format of “!Organization name” will be discontinued
• The APIs for searching Organization/Role affiliation without pagination will be discontinued
  • /API/User/Membership/listByQuser, listByQgroup
  • /API/User/RoleMembership/listByQuser, listByQrole
  • Please use the following API with pagination function
    • /API/User/Membership/list, /API/User/RoleMembership/list
• In the Questetra REST API, the API to obtain processing form screen information (/API/PE/Workitem/Form/viewXml) will be discontinued

Schedule for Version 18.0 (April 2026)

• The following methods related to HTTP authentication settings in Script Task/Service Tasks (Add-on) scripts will be discontinued
  • A warning message will be output to the Process log when a deprecated API is executed
  • You can check the target App or Process by searching for “Only logs with warnings” in [Process Log]
  • Subject
    • httpClient.getOAuth2Token(String settingName)
    • httpClient.begin().authSetting(String settingName)
• In [Message Start Event]/[Catching Message Start Event (HTTP)], old-style reception parameters including data definition numbers (data[XX].input, etc.) will be discontinued
  • A warning message is now output to the Process log when old format reception parameters are used
  • Please change so that specify using field names on the HTTP request sender side
• In the Membership API of Questetra REST API, the request parameter role and the role property included in the response will be discontinued
• In the Questetra REST API, the API for Task processing (/API/PE/Workitem/Form/save) will be discontinued
  • Please use the new Task processing API (/API/PE/Workitem/{workitemId}/Form/save) added in Version 15.2