2024-08-01: The update to Ver. 16.1.0 has been postponed from 2024-08-04 Mon. to 2024-08-18 Sun.
2024-09-30: Details about Ver. 16.1.1 are added.
2024-10-21: Details about Ver. 16.1.2 are added.
2024-12-09: Details about Ver. 16.1.3 are added.
Release Overview
Updating Date
- Workflow platforms for Rapid Update
- Ver. 16.1.0:
August 4th, 2024 (Sun)=> August 18th, 2024 (Sun) - Ver. 16.1.1: [TBD]
September 1st, 2024 (Mon) or 8thOctober 6th, 2024 (Sun) - Ver. 16.1.2: October 27th, 2024 (Sun)
- Ver. 16.1.0:
- Workflow platforms for Scheduled Update and Trial mode
- Ver. 16.1.0: Not updated
- Updated to Version 16.0.2 on August 4th, 2024 (Sun)
- Ver. 16.1.1: [TBD]
September 1st, 2024 (Sun)or 8thOctober 6th, 2024 (Sun) - Ver. 16.1.2: October 27th, 2024 (Sun)
- Ver. 16.1.3: December 15th, 2024 (Sun)
- Ver. 16.1.0: Not updated
Changes to be Noted
- [Throwing Message Intermediate Event (HTTP)] will replace [Receive Task (HTTP)]
- The script engine GraalJS (Nashorn Compatible Mode) will be discontinued in Service Tasks (Add-on)
- The existing [Slack: File Upload (Bots)] will be discontinued and [Slack: File Upload (Bots)] will be added as a new item
- If you are using this built-in automated step, you will need to replace the item
- Check out the plans for changes in future versions [Plans for Future Changes] at the bottom of this page
Details for Version Version 16.1.0
($.: appended 2024-08-05, $$.: appended 2024-08-13)
Changes of Functions for All Users
Workflow
- When deleting a process, you will now be prompted to confirm the deletion (#9962)
- Improved performance of the processing for retrieving the number of [Offered] items (#9761)
- $. Improved performance of Process Start (#10112)
- $. Improved performance of process Search (#10134, #10135)
- Fixed the following Bugs
- For File-type Data Items, the error message when a file upload fails may not be displayed correctly (#10046)
- In a newly released app, if multiple initial process starts are attempted at the same time, the process may fail to start (#10068)
- If you try to [Copy data from the other process] while an input error is displayed, an HTTP 405 error occurs (#10054)
Open Chat
- Fixed the following Bugs
- “Good!” from the same user may be registered multiple times(#10031)
Changes of Functions for Workflow Designers
- Fixed the following Bugs
- $. On the Data Item Setting screen, when you try to set columns for a Data Item other than the selected Data Item, the display position of the dialog shifts (#10023)
Date/Datetime-type
- Input checks with maximum/minimum values is now supported (#10001)
- Checks whether the settings are correct when setting initial values (#10004)
- $. In the case of a format error, the error message will now guide you to the correct format in both Japanese and English (#10129)
User/Organization-type
- Specific User/Organization can now be specified in the initial value settings (#10027)
Table-type
- In String-type sub-data items, spaces are now maintained and displayed as is (#9981)
- The display style was different between edit mode and other modes
- In a Select-type sub-data item, if a non-existent option is specified, an input error occurs now (#9983)
- In Numeric-type sub-data items, input checks can now be performed with the maximum/minimum values of the row-wise (horizontal) calculation results. (#9991)
- Date type sub-data items can now be checked for maximum and minimum values (#10021)
Operator
- Changed the display label of the select box for “The same user as a user who operated tasks in the Swimlane ‘XX'” to “The same User as a user who operated tasks in the Swimlane (the same organization)” (#6803)
Node/Overall Tasks
- On the settings dialog screen, the button label is now changed to [Close] from [Cancel] if the settings have not been changed (#9967)
- Changed the label of the workflow diagram resize slider (top right) from “Node Size” to “Font Size” (#10028)
- $. For items that display process logs, process logs (automatic processing logs) are now displayed even for nodes that are not included in the latest version (#10099)
- The Automatic Processing Log is displayed even for Debug Processes on the node details screen
- It will be easier to refer to the Process Log of the Debug Process in the developing version
- Fixed the following Bugs
- $. Allowed Hosts/Networks information is displayed on the node details screen for items that cannot receive HTTP requests (#10098)
Start Event
- It now prevents starting a Debug Process if the license limit is exceeded (#10069)
- Fixed the following Bugs
- In debug processes, even if one Process Start Organization is determined, the Process Start Organization is empty (#10083)
Terminate End Event
- $. Added an option to delete the Process on exit (#9338)
Human Task
- When changing the Split type in the settings to “The token moves to a Destination according to the satisfied condition.”, the initial setting of the transition condition is changed to “Never move to Destination” (#10125)
Throwing Message Intermediate Event (email)
- Replaced the URL of the process details screen set in the Body with the new format (#9352)
- Ver. Automatically replaced when updating to version 16.1
- The following two patterns are replaced:
/OR/ProcessInstance/view?processInstanceId=#{processIntanceId}to/OR/ProcessInstance/#{processInstanceId}/view/OR/ProcessInstance/listView?processInstanceId=#{processIntanceId}to/OR/ProcessInstance/#{processInstanceId}/view
- Not replaced if the process ID is referenced to Data Items, etc.
Message Start Event/Receive Task (Form)
- Form language can now be specified by specifying a query parameter (#9088)
?locale=enfor English,?locale=jafor Japanese- Button names and input error messages will be in the specified language
- The display items on the form (subject to app definition) such as Data Item names will follow the definition (language switching is not possible)
- $$. For URLs in Message Start Event (Form), the initial value of the input field when displaying the form can now be specified with the query parameter(#10051)
- [Receiving task (Form)] is not applicable
- The parameter name is the same as for [Message Start Event (HTTP)], etc.
- If you want to set Japanese, etc., URL encoding (percent encoding) is required
- e.g.:
/System/Events/MessageStartForm/2/1/key/view?title=test&q_var1=foobar
Timer Start Event
- Added [Timer Start: Number of Organizations] (#9974)
- A new process will be started at the specified timer date and time for each target organization
- The target organization is stored in an Organization-type Data Item
- Changed the name of [Timer Start: the number of choices] (#10049)
- The new name is [Timer Start: Number of Choices]
- Debug Processes can now be started on the three Timer Start Events as follows (#10050)
- [Timer Start: Number of Choices], [Timer Start: Number of Organizations], [Timer Start: kintone: Number of Records]
- Only one randomly determined Debug Process will be started, not multiple Processes
Gateway
- Added [Never move to Destination] to transition conditions (#10055)
- If there are no other Split conditions set to the same transition destination, the token will not flow to the transition destination set to [Never move to Destination]
- The default setting of the transition condition is changed to “Never move to Destination” from “Always move to Destination”
- $. In XOR/OR gateways, the oldest flow drawn on the workflow diagram becomes the default flow (#10124)
- Typically, the first outgoing flow connected to a gateway becomes the default flow
- Changed specifications and internal implementations in the following automated processing steps
- Gmail
- Gmail: Remove Label from Email Message (#9937)
- Start: Gmail: Email Message Received (#9938)
- $$. Gmail: Get Email Message (#10086)
- Reply-To header value can now be saved
- Google Sheet
- Google Sheets: Append New Rows (Table type data) (#10010)
- When specifying a table sub-data item in the settings, the field name can now be selected in the select box
- Google Sheets: Update & Get Cells (#10034)
- Spreadsheet ID/Sheet title can now be specified by Data Item, not just fixed value
- Download Choice Data (#10035)
- Spreadsheet ID/Sheet title can now be specified by Data Item, not just fixed value
- Google Sheets: Get Row (#10036)
- Spreadsheet ID/Sheet title can now be specified by Data Item, not just fixed value
- Google Sheet: Copy Sheet (#10037)
- Spreadsheet ID/Sheet title can now be specified by Data Item, not just fixed value
- Google Sheets: Append New Rows (Table type data) (#10010)
- Google Vertex AI
- $$. Google Vertex AI: Gemini: Chat (#10166)
- Changed the models can be selected in the select box
- Added: Gemini 1.5 Pro / Gemini 1.5 Flash
- Removed: Gemini 1.0 Pro Vision
- The following changes have been made according to the Gemini 1.5 Pro specifications
- Removed the item for checking the maximum number of attachments
- Audio files can now be specified in attachments
- Changed the upper limit for Temperature from 1 to 2
- Changed the models can be selected in the select box
- $$. Google Vertex AI: Gemini: Chat (#10166)
- Gmail
Amazon Web Services
- Changed specifications, and internal implementations in the following automated processing steps
- $$. Amazon Bedrock: Anthropic Claude: Chat (#10141)
- Added models can be selected in the select box
- Claude 3.5 Sonnet / Claude 3 Opus
- Added models can be selected in the select box
- $$. Amazon Bedrock: Anthropic Claude: Chat (#10141)
Microsoft 365
- Added the following automated processing steps
- Lists
- Microsoft Lists: Add List Item (#9932)
- Add a list item to a specified list in Microsoft Lists
- Microsoft Lists: Update List Item (#9933)
- Update the contents of a list item (1 item) in Microsoft Lists
- Microsoft Lists: Delete List Item (#9934)
- Delete list items in Microsoft Lists
- You can also delete multiple list items at once by specifying one list item ID per line
- Microsoft Lists: Add List Item (#9932)
- Lists
- Changed internal implementations in the following automated processing steps
- Excel for Business
- Microsoft 365 Excel for Business: Insert New Row (#9988)
- Outlook for Business
- $. Microsoft 365 Outlook for Business: Get Email Message (#10096)
- Reply-To header value can now be saved
- $. Microsoft 365 Outlook for Business: Get Email Message (#10096)
- Excel for Business
Open AI
- Changed specifications and internal implementations in the following automated processing steps
- $$. OpenAI ChatGPT: Chat (#10139)
- Changed the models can be selected in the select box
- Add: gpt-4o / gpt-4o-mini / gpt-4-turbo
- Removed: gpt-4-32k / gpt-4-turbo-preview / gpt-4-vision-preview
- Added a setting item “I1-D: Fidelity of image understanding” corresponding to the parameter that specifies the level of detail of the attached image
- Setting item “Organization ID” is now deprecated due to changes in the “API Key” specification
- Changed the models can be selected in the select box
- $$. OpenAI DALL-E: Generate Image (#10140)
- Setting item “Organization ID” is now deprecated due to changes in the “API Key” specification
- $$. OpenAI ChatGPT: Chat (#10139)
Box
- Added the following automated processing steps
- Box: Move Folder (#10089)
- Move an existing folder to a folder specified by the folder ID
- Box: Move Folder (#10089)
- Changed internal implementations in the following automated processing steps
- Box: Search Folder (#9987)
kintone
- Changed internal implementations in the following automated processing steps
- kintone: Add New Record (#9993)
- kintone: Update Record (#9994)
- kintone: Delete Record (#9995)
- kintone: Get Record (#9996)
- Start: kintone: Record Created (#9997)
Slack
- Added the following automated processing steps
- Slack: Upload File (Bots) (#10033)
- Successor to the existing item [(Deprecated) Slack: Upload File (Bots)] which will be deprecated in #9940
- There are differences in the settings (channel designation changed from name to ID) so it has been added as a new item.
- Slack: Upload File (Bots) (#10033)
- Changed specifications, internal implementations in the following automated processing Steps
- Slack: Post Chat (Bots) (#9939)
- The deprecated setting “C1-deprecated: OAuth2 Settings (due to scope change)” has been deleted
Slack: Upload File (Bots)=> (Deprecated) Slack: Upload File (Bots) (#9940)- This item is deprecated due to the deprecation of the Slack API that was used
- Changed the name to “(Deprecated) Slack: Upload File (Bots)”
- Added a new item “Slack Upload: File (Bots)” as a successor (#10033)
- lack: Post Chat (Incoming Webhook) (#9941)
- $. Start: Slack: Message Received
- URL etc. are now displayed on the settings screen (#10103)
- API key is now required (#10122)
- Slack: Post Chat (Bots) (#9939)
Stripe
- Changed internal implementations in the following automated processing Steps
- Stripe: Create Customer (#9947)
- Stripe: Update Customer (#9948)
- Stripe: Search Customers (#9949)
- Stripe: Create Product (#9950)
- Stripe: Search Products (#9951)
- Stripe: Create Draft Invoice (#9952)
- Stripe: Add Item to Draft Invoice (#9953)
- Stripe: Finalize Draft Invoice (#9954)
- Stripe: Send Invoice (#9955)
- Stripe: Charge by Invoice (#9956))
- Stripe: Update Metadata of Customer/Product/Invoice (#9957)
Twilio Sendgrid
- Changed internal implementations in the following automated processing Steps
- Twilio SendGrid: Add or Update Contact (#10008)
- Twilio SendGrid: Add or Update Contact (Custom Fields) (#10009)
Trello
- Changed internal implementations in the following automated processing Steps
- Trello: Create Card (#9989)
DocRaptor
- Changed internal implementations in the following automated processing Steps
- DocRaptor: Generate PDF (#9990)
Converter, etc.
- Added the following automated processing steps
- $. Converter (Copy File) (#10152)
- Duplicates the attachment of a File-type Data Item to a specified File-type Data Item
- If there is only one file, you can also use it to change the file name
- $. Converter (Copy File) (#10152)
- Changed internal implementations in the following automated processing Steps
- (Any Website): Download File (#9944)
- Converter (Table type data to Excel-CSV File) (#9945)
- Converter (Date to Japanese calendar text) (#9946)
- $$. Converter (TSV File to Table type data) (#10011)
- Changed the item name from “Converter (Excel-CSV File to Table type data)”
- Character encoding can now be specified when importing files
- Improved error messages
Throwing Message Intermediate Event (HTTP) => Receive Task (HTTP)
- Migrate the [Catching Message Intermediate Event (HTTP)] to the [Receive Task (HTTP)] (#10067)
- The specifications are the same as those of [Catching Message Intermediate Event (HTTP)], but the following features (#10091, #10092) have been added
- The settings in the Workflow App will not change
- The icon will change in the workflow diagram (red circle => gray rounded rectangle)
- Icon replacement and position adjustment will be done automatically when updating to Ver. 16.1
- The URL for the Receive Task (HTTP) is added
- URL format:
/System/ReceiveTask/HttpPost/{APP ID}/{NODE NUMBER}/receive - The name of the root element is changed in the XML of the error response
- URL format:
- The URL used in the [Catching Message Intermediate Event (HTTP)] can still be used for the time being
- Old URL format:
/System/Event/IntermediateMessage/{APP ID}/{NODE NUMBER}/receive - Scheduled to be discontinued in Version 19.0 (April 2027)
- Old URL format:
- $$. Added a setting to deny all access to new URLs,
/System/ReceiveTask/HttpPost/, when IP address filtering is enabled in a workflow platform- This is a measure to prevent unintentional access to new URLs
- When changing the access URL in the HTTP message senders, please also change the IP filtering setting
- Added the ability to set a “deadline” in the [Receive Task (HTTP)] (#10091)
- In the [Receive Task (HTTP)], an API for checking whether the token has arrived at the step and is ready to receive has been added (#10092)
/System/ReceiveTask/HttpPost/{APP ID}/{NODE NUMBER}/receive/check- GET request, HTTP 200 is returned if available
- The response if not available is the same as
/System/ReceiveTask/HttpPost/{APP ID}/{NODE NUMBER}/receive
- The response if not available is the same as
- Before actually sending a request that includes business data, it will be possible to check whether it is in a state where it can receive the data
- Fixed the following Bugs
- If an HTTP request is received and a token is moved at the same time in the same process, the HTTP reception process may fail
- HTTP 500 is returned as a response.
- If an HTTP request is received and a token is moved at the same time in the same process, the HTTP reception process may fail
Message Start Event (HTTP) / Receive Task (HTTP)
(The Task processing API, (/API/PE/Workitem/{workitemId}/{workitemId}/Form/save), also handles Table-type data items in the way as follows)
- In Table-type Data Items, the handling of leading and trailing spaces and line breaks has been unified to the following specifications (#9977, #9980)
- String-type sub-data item: Spaces are maintained as is, and an input error occurs if there is a line break
- Numeric-type sub-data items: Even if the numeric text contains spaces or line breaks before or after it, it will be interpreted as a number
- Even though the contents of the element can contain spaces and line breaks, it is recommended that only numeric text is included
- Select-type sub-data item: Spaces are maintained as is, and an input error occurs if there is a line break (regarding the value of the selection ID)
- Date-type sub-data item: Even if there are spaces or line breaks before or after the date text, it will be interpreted as a date
- Even though the contents of the element can contain spaces and line breaks, it is recommended that only date text is included
- $$.
localeparameter can now specify a language (#10090)- Error messages are returned in the specified language
Message Start Event (Webhook)
- $. In the URL detail, the string of ‘(API key)’ is temporarily indicated until the API key is set (#10127)
Receive Task (Webhook)
- $. An API for checking whether the token has arrived at the step and is ready to receive has been added (#10105)
- The similar feature as Receive Task (HTTP)
/System/ReceiveTask/Http/{APP ID}/{NODE NUMBER}/{PROESS ID}/{API KEY}/receive/check
HTTP Authorization Settings
- $. Adjusted the display layout style (#10066)
- Fixed the following Bugs
- The “Client IDs” set in “OAuth2 Client Credentials” that are referenced by the built-in automated processes are unknown (#9979)
- “Client IDs” are set individually by the user, but the values of these IDs cannot be seen after they have been set
- The “Client IDs” set in “OAuth2 Client Credentials” that are referenced by the built-in automated processes are unknown (#9979)
Script Task
- $. Added “ApiKey” header to the allow list in HttpClient [Custom HTTP Headers] of Throwing Message Intermediate Event (HTTP)/Script Task (#10114)
- Deprecated methods of the AddableDate class are changed to “postponed indefinitely (obsolete date undecided)” (#9104)
getFirstTimeInMonth(),getLastTimeInMonth()
- Warning messages are output to the process log when deprecated methods are executed (#9301)
HttpClientWrapper.getOAuth2Token(String),HttpRequestWrapper.authSetting(String)
- When processing an instance of the ScriptListArray class, a change to a cell value is immediately reflected in the arithmetic column / summary row (#9970)
- In the specification up to Ver. 16.0, the values of arithmetic columns / summary rows were not reflected during script processing, but were updated together when the script processing was completed
- When processing an instance of the ScriptListArray class, if an invalid value is set by changing a cell value, a script error occurs when calling a method of the instance (#9972)
- In the specification up to Ver. 16.0, values were not validated during script processing, but were validated together at script completion
- For example, errors occur in the following cases
- A String-type column contains a linefeed
- A Numeric-type column contains a string that cannot be interpreted as a number
- A Date-type column contains a string that cannot be interpreted as a date (YYYY-MM-DD)
Service Task (Add-on)
- Allowed items to be deprecated by definition files (#10030)
- Specified by
<deprecated>true</deprecated> - The deprecated items do not appear in the palette (cannot be newly placed)
- Processes with the items run correctly in the latest released versions
- In app settings, the items cause app definition errors
- Specified by
- $. Added a
form-typeto define a setting item in definition files that is used to select a sub-item of a Table-type data item (#9527)form-type="SELECT_LIST_SUB_DATA"- Used with
depends-on - The sub-items for selection appear only when
depends-onis specified with a config element that isform-type="SELECT"and a table-type data item is selected for the setting item defined by the element on the Task setting screen
- Added the configuration item form-type=”QGROUP” to select the organization in the definition file (#9526)
- The settings screen displays a component for selecting an Organization
- Changed an
engine-typefield is required in definition files (#9924) - Abolished the scripting engine “GraalJS (Nashorn Compatible Mode)” (#9764)
- Service task definition files are migrated to
<engine-type>3</engine-type>when updating to Ver. 16.1- However, if the file has not been successfully migrated (“rewrite” failed), the definition file is not rewritten
- Even if the definition file is not rewritten, the script engine “GraalJS” is used at runtime
- However, a definition error will occur in the app settings because the obsolete script engine is specified
- To correct app definition errors, it is necessary to manually update the service task definition files individually
- Details: Correspondence for Script Engine GraalJS (Nashorn Compatible Mode) Abolition (April 2024)
- Service task definition files are migrated to
Changes of Functions for System Administrator
System Summary
- Added “Number of started processes” (#9861)
- Excluded debugging processes from the total
- Debugging processes are excluded from the count in the “Number of running processes” (#10076)
- Applies to values counted after Ver. 16.1 update
- Past data up to Ver. 16.0 remains the totaled values including debug processes.
User
- Error message is no longer displayed on the [User List] screen when the license limit is reached (#10057)
- Changed that the error message is displayed on the [New User] or [Import Users] screen
- When returning from the user details screen to the list screen, the filter/display column settings remains as they were set (#9925)
- Chips indicating the specified filter conditions are displayed above the list (#9958)
- When deleting a user, the user is prompted to confirm the deletion
Organization
- $. Improved the message displayed in the “Download all” section of the “ImportOrganization List” screen (#10088)
- Since it is not possible to bulk update organizations, the statement “It can be used to update organizations” has been removed
- $. Improved the efficiency of calculations for data update processing executed when deleting an organization (#10126)
License
- Menu name [Extension Key] is changed to [License]
- Added links to the procedure page for changing the contract details, etc.
IP Address Fintering
- $$. The default values when changing the IP filtering setting from Disabled to Enabled are now as follows (#10170)
- All are allowed in “Global Configuration”
- Deny everything under /System/
- However, all to Message Start Event / Receiving Task (form) are allowed
- (same as the default value in the workflow platform)
- $$. Increased the number of path prefixes that can be added from 30 to 40 (#10171)
Changes of Functions for Questetra REST API Developers
- Added API for specifying and updating the affiliated organization and the role for each user at once (#9544)
/API/UGA/Quser/setMembership- Both Membership and RoleMembership are handled
- Specify Memberships/RoleMemberships in the request body of a POST request in JSON format
- The maximum number of Memberships or/and RoleMemberships that can be specified together is 10000 in total
- $. The API for adding Process/App authorization can now be specified without using the leader parameter (#9604, #9921)
/API/Admin/SystemAuthority/addToQgroup/API/Admin/ProcessAuthority/addToQgroup- No Position:
qtitleId=none(same asleader=false) - With Position:
qtitleId=any(same asleader=true) - If both
qtitleIdandleaderare specified, it results an error - The
leaderparameter will be discontinued in Ver. 19.0 (April 2027)
- $. In the API for setting affiliation, if the qtitleId overlaps, an error JSON is returned (#9921)
/API/UGA/Membership/setand/API/UGA/RoleMembership/set- Up until version 16.0, the response was an HTTP 400 error with no response, but from version 16.1 onwards, in addition to the HTTP 400 error, an error JSON is returned
- Added API for obtaining a list of process logs (#9795)
/API/Admin/ProcessLog/list
- Added API for pausing/resuming apps (#9857)
- Pause:
/API/PMM/ProcessModel/{processModelInfoId}/stop - Resume:
/API/PMM/ProcessModel/{processModelInfoId}/restart
- Pause:
- $. In the API to [Release] App (
/API/PMM/ProcessModel/{processModelInfoId}/release), changed note specification from query parameter to request body (#10002) - Extended refresh token validity period from 30 days to 35 days when accessing Questetra REST API with OAuth2 (#9911)
- Fixed the following Bugs
- In the Questetra REST API execution environment (Swagger UI), the following API requests did not work (#10040)
/API/OR/ProcessInstance/stop,/API/OR/ProcessInstance/delete- It is stated that the Content-Type is application/x-www-form-urlencoded
- In the Questetra REST API execution environment (Swagger UI), the following API requests did not work (#10040)
Non-functional Changes and Changes of External tool Functions
- Upgrade database
Details for Version Version 16.1.1
(Appended on 2024-09-30)
Changes of Functions for All Users
Workflow
- Fixed the following Bugs
- When specifying the filter condition “contains” for String/Discussion-type Data Items in the Process/Task search, the search may not work properly (#10233)
Open Chat
- Fixed the following display layout issues
- Posts from Questetra bot (Ques-kun) to [Timeline] were displayed shifted up or down (#10198)
- When displaying [Good! to everyone] or search results, it may overflow if the User or Organization name is long, it may overflow (#10199)
Changes of Functions for Workflow Designers
- When editing the [Work Manual], changed the font of the input text area to a monospaced font (#10223)
- When placing a new [Receive Task (HTTP)], a random API key is now set by default (#10257)
- Fixed the following Bugs
- When editing an App, copying a node may fail (#10190)
- In the [Work Manual], the correct marker may not be displayed in nested lists (#10218)
Changes of Functions for System Administrator
- Fixed the following Bugs
- When changing Position settings, if the settings are changed so that there is no System Administrator, the message “An error has occurred” is displayed (#10255)
- Change the message to be appropriate
- When changing Position settings, if the settings are changed so that there is no System Administrator, the message “An error has occurred” is displayed (#10255)
Details for Version Version 16.1.2
(Appended on 2024-10-21)
Changes of Functions for All Users
- Improved task search performance (#10290)
- Fixed the following Bugs
- When attempt to start a paused application, a system error may occur without any appropriate error message being displayed (#10277)
Changes of Functions for Workflow Designers
- Fixed the following Bugs
- Timeout May Occur When Updating Values of a Table-type Data Item With Auto-processing Step (#10289)
- An app definition error does not occur even if a deleted Data Item or a Data Item other than a File-type is specified in the [Attachments] setting of the [Throwing Message Intermediate Event (Email)] (#10298)
Changes of Functions for System Administrator
- Fixed the following Bugs
Changes of Functions for Questetra REST API Developers
- When attempt to execute the following API in [REST API Reference] (API execution platform), a 406 error occurs (#10280)
/API/OR/Workitem/listCsvUtf16: Download Task search results in CSV format
Details for Version Version 16.1.3
(Appended on 2024-12-09)
Changes of Functions for Workflow Designers
- Fixed the following Bugs
- The Debug Process may not be started with the [Timer Start: Number of Choices] (#10336)
- The debug process could not be started if the Type of data source was [Add-on] or [String type data item]
- The initial value of “Title” cannot be set in Timer Start Events such as [Timer Start: Number of Choices] and events that start Processes in cooperation with external services such as [Start: Gmail: Email Message Received] (#10337)
- The User or Organization replacement does not work in the Event settings when importing an App archive in which the following Start Event is placed (#10360)
- [Start: Google Calendar: Event Started], [Timer Start: Number of Organizations]
- A validation error does not occur if the number of decimal places exceeds in the Numeric subdata item of a Table-type Data Item (#10371)
- In the Web UI such as the Task Operating screen, the input value is rounded to the number of digits, so no problems occur
- Problems occur Task processing API or when receiving data via HTTP reception
- Calculations in the calculated columns/total rows are performed as is without causing a validation error, so the calculation results may differ
- The Debug Process may not be started with the [Timer Start: Number of Choices] (#10336)
Changes of Functions for Questetra REST API Developers
- Fixed the following Bugs
- When the API for bulk Operator change contains an empty string in the fromQgroupIds / toQgroupIds parameters, a 500 error occurs (#10343)
- When the parameter contains an empty string or only spaces, a 500 error occurs
/API/Admin/ProcessModel/{processModelInfoId}/AllocationRule/update
- When the parameter contains an empty string or only spaces, a 500 error occurs
- When the API for bulk changing the memberships (affiliation) contains empty string in the memberships / roleMemberships array, a 500 error occurs (#10344)
/API/UGA/Quser/setMembership,/API/UGA/Membership/set,/API/UGA/RoleMembership/set
- When executing the API to bulk changing Operator the processor settings from the [REST API Reference] > [Workflow REST API] screen, specifying multiple fromQgroupIds and toQgroupIds results in a 400 error (#10363)
- When the API for bulk Operator change contains an empty string in the fromQgroupIds / toQgroupIds parameters, a 500 error occurs (#10343)
Plans for Future Changes
We are planning to alter the following specifications and system platform in future versions.
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
- Old 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 the HTTP sender to specify parameters using field names
- In the Membership API of Questetra REST API, the request parameter
roleand theroleproperty 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
- Please use the new Task processing API (
Schedule for Version 19.0 (April 2027)
- The following URL format used in the [Catching Message Intermediate Event (HTTP)] will be discontinued
/System/Event/IntermediateMessage/{APP ID}/{NODE NUMBER}/receive- Please use the [Receive Task (HTTP)] URL of the following format
/System/ReceiveTask/HttpPost/{APP ID}/{NODE NUMBER}/receive
- If you use [IP Address Filtering], you must change the settings due to the URL change.
