Version 18.0: Renamed “Process” to “Case” and Expanded Markdown Support

Overview

Update Date

• Ver. 18.0.0：2026-04-27（JST）
  • Applying to:: Workflow platforms with Rapid updates^*

*Workflow platforms for which the system administrators have requested immediate update to the new version

Changes to be Noted

• The term “Process” has been renamed to “Case” on the user interface. This establishes a three-tier structure of App/Case/Task. Note that the REST API paths and parameter names remain unchanged
• Workflow screens for smartphones (My Tasks, Tasks to Accept, New Start), App Detail screens, and New Start screens have been converted to Single Page Applications (SPA)
• After completing a task or editing data, users will be redirected to the Case Detail screen, with the left-side menu hidden by default
• The Throwing Message Intermediate Event (HTTP) will automatically convert parameters from the old `data[N].input` format and URLs to the new field name-based format
• The Task Processing API (/API/PE/Workitem/Form/save) and the Membership API role parameter are now deprecated and will be removed in a future release
• App archives created with versions older than 15.0 can no longer be imported
• In Script Tasks httpClient.getOAuth2Token(String) and httpClient.begin().authSetting(String) will be deprecated
• In Script Tasks qgroupDao.findByQuserAndPosition() and quserDao.findByQgroupAndPosition() will be deprecated
• Please refer to the Plans for Future Changes section at the end of this document for information about future version changes

Details for Version 18.0.0

(★: Added on 2026-04-27)

◆ Changes in Functions for All Users

• The 18.0 logo features The 36 Views of Mount Fuji, Surugadai in Tokyo (#11463)
• Added the America/Panama and Pacific/Honolulu time zones to the available options (#11337)

Workflow

• “Process” has been renamed to “Case” (#11481)
  • This change affects labels and messages on the screen (e.g., “Process ID” becomes “Case ID,” and “Process List” becomes “Case List”)
  • CSV download headers have been updated to reflect the change to “Case ID”
  • In the REST API documentation (Swagger UI), the Tag name is now “Case”
  • However, API paths, parameter names, and response property names (including ProcessInstance) remain unchanged
  • Class and method names in Script Tasks and the Form JavaScript API are not affected
• The App Detail screen, Start and First Step screens, and the Timer Start Event have been converted to Single Page Applications. (#11002, #11189, #11443, #11445)
  • The Timer Start Event completion page has been replaced with a completion dialog that displays the started Case subject and a link to Case Details
• The smartphone-specific screens [My Tasks], [Offered], and [Start] have been converted to Single Page Applications, with the UI adjusted to include Case Details and Task Processing (#11183, #11184, #11185, #11392)
  • The smartphone UI has been adjusted to align with the PC version
  • Button and icon sizes and margins in Case Details and Task Processing have been adjusted
• After task completion or data editing, users are now redirected to the Case Detail screen (#11458)
  • Completion messages are now displayed as Snackbars on the Case Detail screen
  • In case of an error, users are redirected to the Case Detail screen, and the error details are displayed in a Snackbar
  • In the task processing/data editing screen, the left-side menu is hidden, allowing for more usable main area
• Hide the left-side menu to expand the main area (#11457)
• The styles for buttons such as “Work Manual”, “Back”, “Details”, and “Back to List” have been refreshed, and the links have been updated (#11325, #11327, #11348, #11388)
  • Migrated to a MaterialUI base and for a more visually appealing style
• Fixed an issue where the user was not correctly redirected to the specified URL after successful additional authentication for suspicious login attempts (#11453)
• Improved the performance of task search and process search (#11395、#11494)
• Resolved an issue where long user names prevented the display of the Case ID/Subject in parentheses. (#11505)

Collab Chat

• Added support for Markdown (#10338, #11386)
  • Users can switch between plain text and Markdown
  • The same grammar and UI as String-type (Markdown) are used
  • Some specifications have been added, such as mentions
  • Supports links to channels (hashtags)
• Enhanced to support the “…More” option for Markdown format posts (#11376)
  • Modified to truncate display based on visual height (applies same specifications to plain text posts)
• Attachments (e.g., PDFs) now open in a separate window without requiring a download (#11100)
  • You can view content without downloading anything
• Mention notifications are now sent with a 30-second delay (#11006)
  • If the post is deleted within 30 seconds, no notification is sent
• Pressing Shift+Enter while viewing mention suggestions now only inserts the suggestion and does not post it (#11533)
• Fixed an issue where mentions would not become links if the user name or organization name contained special characters such as [ or ]（#10610、#10613）
• When the left-side menu is hidden, polling is paused to improve performance (#11470)
• Improved the HTML output for mentions and channel links (hashtags) (#11364, #11504)

◆ Changes in Functions for Workflow Designers

• Changed so that app archives created with versions older than 15.0 cannot be imported（#11286）
  • Support is limited to three versions prior. Version 18.0 supports archives exported from version 15.0 onwards
• All users can now view the app category list (#10880)
  • When you filter by category for a new project, all categories will now be displayed.
  • This change was previously announced in the Ver. 17.2 release notes under “Planned for Future Changes”. Please review if problematic category names are assigned
• The app operation manual now uses the same specifications as String-type (Markdown) (#11039)
  • This change was previously announced in the 17.2 release notes. The display might change if you are using HTML tags
• Added date filtering to the Case Log display on Node Detail pages (#10842)
  • The default filter condition is set to a “past 7 days range”
  • The same functionality is available via the “Reception Parameter, IP address filtering” button in the Message Start Event (HTTP) settings screen
• Bulk adding data items in the modeler has been modified to notify you if there are rows that could not be interpreted and were ignored (#11318)
• The app name is included in the subject line of error notification emails for automated processing steps (#11230)

Discussion-type Data Item

• Added Markdown formatting to Discussion-type data items (Discussion Markdown)(#11373)
  • The older version is Discussion-type (Text), the newer version is Discussion-type (Markdown)
  • Uses the same syntax as String-type Markdown
  • Markdown is supported in the following areas
    • Gateway/ Human Task switching condition (#11429): Specifies “Not Empty,” “Empty,” or “Includes Right Value”; targets Markdown text
    • SpEL Templates for Update Data (#11426): Embedding references to Discussion-type Markdown replaces it with Markdown text
    • Throwing Message Intermediate Event（HTTP）send parameters (#11427)
    • PDF Generation Fields (#11428): Embedded value is converted to Markdown text
    • Message Start Event/Receive Task (HTTP) API
• Implemented a 1 million character validation during the overall save of task processing or data editing in Bulletin Board Type Data Items (#11404)
  • Up to version 17.2, the validator checked only the board’s “Send” button. It did not check during task processing or data editing because the excess posts were not saved
  • From version 18.0, a validation error is displayed even during the entire save action
• Improved the internal implementation of the Discussion-type component (#11326)

Data Items Other than Discussion-type

• Validation of SpEL templates has been enabled for the initial values of subject / text-type data items (#11345)
  • The validation that was already performed in data update steps has now also been applied to the initial value settings of subject / text-type data items
• The error message displayed when invalid XML is uploaded in the option master upload has been improved (#11424)

Workflow Diagram

• The calculation logic for flow relay points in the JS modeler’s workflow diagram has been improved (#6024)
  • The flow margin (the minimum length to the first bend) changes depending on the font size/node size settings
  • Flows passing through the same location will be displayed with a slight offset, making them less likely to overlap

AI Agent

• Enabled reading (and limited overwriting) of Select-type data item values (#10874)
  • Reading: Available for all Select-type data items
  • Writing: Limited to options meeting all of the following criteria:
    • Options with a fixed type
    • 20 or fewer options
    • No dependent parent data item
• AI-generated responses can now be saved to Discussion-type data items (#11372)
  • This makes it easier to understand the AI’s thought processes, with prior case logs now stored in a more accessible form
• Added templates for instructions to AI (#11250)
  • Five types: “Summarize”, “Categorize”, “Information Extraction”, “Judgment/Evaluation”, and “Document Creation”
• Automatically includes constraint information, such as max/min values of editable data items, in the System Prompt (#11249)
• ★ Anthropic Claude Sonnet 4 is now scheduled for discontinuation (#11537)
• Anthropic Claude Sonnet 4.6 / Opus 4.6 are now supported (#11469)
• Support for the adaptive thinking / effort parameter has been added (#11492)
• When the temperature is set to 1 for Sonnet 4.6 / Opus 4.6, adaptive thinking mode is automatically enabled
• The current time information is now automatically included in the system prompt (#11391)
• The behavior has been changed so that processing fails if execution ends with an unintended stopReason (#11531)
• Set a limit of 30 data items that can be designated as editable in the [Editing permission for AI] screen (#11317)
  • Announced in Ver. 17.2; a validation error occurs when exceeding 31 items

Update CSV Data

• Added an option to designate Table-type data items as outputs when selecting “Save the entire table to a single data item” in [How to save query results] (#10352)
  • This assumes that SQL result column names match Table-type data item column names (not field names)
  • Fewer SQL result columns are allowed (non-existing columns are considered empty). Matching occurs by name, even if the order differs
  • All SQL results are handled as strings, interpreted according to each table item’s type (numbers without decimal points or commas, dates as yyyy-MM-dd format, selections as option IDs)

Collab Chat (Standard Items)

• Collab Chat: Posts can now be added to standard items (#11529, #11467)

Timer Start

• ★ In the following Timer Start Events, the term “Process” has been renamed to “Case”:
  • ★ Timer Start: Number of Choices (#11522)
  • ★ Timer Start: Number of Organizations (#11523)

Google

• The following automated process step has been added to the standard items:
• Google Drive: Copy File (#11328)
• ★ In the following Google-related start events, the term “Process” has been renamed to “Case”:
• Start: Gmail: Email Message Received (#11518)
• Start: Google Calendar: Event Started (#11519)

For the following automated process steps, specifications and internal implementations have been changed:

• Google Vertex AI: Gemini: Updated chat standard items（#11344、#11157、#11245）
  • Removed gemini-2.0-flash and gemini-2.0-flash-lite from model options
  • Allowed resolution specification on attachment files and designation of data item to store summary of thoughts
  • Enabled the attachment of other text files in `text/*` (CSV, XML, etc.) besides `text/plain`

For the following automated process steps, specifications and internal implementations have been changed:

• Gmail: Get Email Message (#11536, #11091, #11486)
  • An issue where some emails were not captured as part of the message body has been fixed
  • When the Content-Type of an attachment is invalid, it is now replaced with application/octet-stream before saving
  • When a filename is too long, it is now truncated before saving

Amazon Bedrock

• For the following automated process steps, specifications and internal implementations have been changed:
  • Amazon Bedrock: Anthropic Claude: The default chat items have been updated (#11528, #11460)
    • Sonnet 4.6 / Opus 4.6 have been added to the model options, and Sonnet 4 / Haiku 3 / Haiku 3.5 have been removed
    • Support for the adaptive thinking / effort parameter has been added

Microsoft

• ★The following automated process step has been added to the standard items:
  • ★Microsoft Teams: Post to Channel (#11554, #11527)
• ★In the following Microsoft 365-related start events, the term “Process” has been renamed to “Case”:
  • ★Start: Microsoft 365 OneDrive for Business: Upload File (#11524)
  • ★Start: Microsoft 365 Outlook for Business: Get Email Message (#11525)

OpenAI

• ★For the following automated process step, specifications and internal implementations have been changed:
  • ★OpenAI ChatGPT: Chat (#11538, #11459)
    • gpt-5.4 / gpt-5.4-mini / gpt-5.4-nano have been added to the model options
    • “original” has been added as an option for image detail

Other Cloud Services

• ★In the following start events, the term “Process” has been renamed to “Case”:
  • ★Start: Box: Upload File (#11517)
  • ★Timer Start: kintone: Number of Records (#11520)
  • ★Start: kintone: Record Created (#11521)
  • ★Start: Slack: Message Received (#11526)

Throwing Message Intermediate Event (HTTP)

• In the Throwing Message Intermediate Event (HTTP), configurations using the old parameter format (e.g., `data[N].input`) will be automatically converted to the new, field name-based format (#11340)
  • This conversion occurs automatically when you upgrade to version 18.0. It also applies when importing archives exported from versions 17.2 and earlier.
  • The conversion applies when the target is a Message Start Event or Receive Task (HTTP) and the destination can be specified using the app ID and node number
  • No user action is required. However, we recommend verifying that your message sending integrations function correctly after the upgrade
• Additionally, the old format path for the Receive Task (HTTP) (/System/Event/IntermediateMessage/…）in a Throwing Message Intermediate Event (HTTP) (/System/ReceiveTask/HttpPost/…） will be automatically converted to the new path (#11342)
  • This conversion will happen in version 18.0, before the old path is deprecated in version 19.0
• In Throwing Message Intermediate Events (HTTP), etc., the App ID and other information are now included in custom HTTP request headers (#11447)
  • The Questetra-Initiator header has been added, allowing identification of which workflow app the request originated from

Message Start Event／Receive Task (HTTP)

• The termination of old-format parameters starting with `data` in the Message Start Event/Receiving Task (HTTP) has been postponed for one year (#11477)
  • This new timeline aligns with the planned discontinuation of the old path for Receive Task (HTTP) in version 19.0
• Also, the descriptions of settings for Discussion-type data items on the node details page have been corrected (#11439)
  • Specifically, descriptions incorrectly referred to them as “Overwrite” when they are actually appended data
• When writing to a Discussion-type data item in the Message Start Event/Receive Task (HTTP), the item type name is now set if the process step name is empty (#11471)
• Fixed the message start event (HTTP) to return the correct 413 error when the number of parts in multipart/form-data is too large (#11312)
  • Previously, it should have returned a 413 error, but it was returning a 500 error

Script Task

• httpClient.getOAuth2Token(String) and httpClient.begin().authSetting(String) have been deprecated (#9509)
• qgroupDao.findByQuserAndPosition(QuserView, boolean) and quserDao.findByQgroupAndPosition(QgroupView, boolean) have been deprecated (#9509)
• An API supporting Markdown posts to Collab Chat has been added (#11462)
• An API supporting comment posting to Collab Chat threads has been added (#11466)

◆ Changes of Functions for System Administrators

• A limit has been implemented on count displays in case log and system log lists (#11419, #11421)
  • If the number of entries exceeds 100,000, the display will show “100000+” and you can only view up to the 100,000th result
  • To access other log entries, you will need to narrow down the results using filtering conditions
• An AI agent usage widget has been added to the overview dashboard under System Settings (#11468)
  • Usage is displayed as a percentage of the limit
  • Data from before the version 18.0 upgrade will be shown as 0
• Chips that indicate current filter conditions will be displayed in the organization and role lists (#11047)
• When returning to a list screen from the Organization, Role, or Position details, your previous search conditions and paging information will be retained (#11487, #11488, #11498)
• The placement of the “Apps referring to the organization” button on User/Organization/Role/Position detail screens has been standardized to align right (#11496)
• A reporting feature similar to CSP reports has been provided for HTTP connection destination restrictions (#11363)
• A tool for listing data items of a specific app has been added to the MCP server (#11493)
• Error handling for abnormal cases (such as when a user is logged out in the background) has been improved (#11322)

◆ Changes of Functions for Questetra REST API Developers

• The Task Processing API endpoint (/API/PE/Workitem/Form/save) will be deprecated (#9506)
  • Please use /API/PE/Workitem/{workitemId}/Form/save, which was added in version 15.2, instead
• The role parameter property in /API/UGA/Membership/add and similar API endpoints will be deprecated (#9507)
  • Please use the role-related APIs introduced after the role implementation
• A new API is available to start a new case by reusing data from an existing case (#11448)
  • /API/PE/ProcessInstance/{processInstanceId}/reuseAndStart
• A new API is available to download system logs in CSV format (#11262)
  • /API/Admin/SystemLog/listCsv
• Support for Discussion-type Markdown data items has been added to the task processing, case details, case list, and task list REST APIs (#11373)
  • Similar to String-type Markdown, the API returns values transformed from Markdown into HTML text
• APIs exclusive to Professional Edition are now explicitly documented as such in the REST API Reference (#11383)
• A maximum count limit of 100,000 has been set for counts in /API/Admin/ProcessLog/list and /API/Admin/SystemLog/list (#11420)
  • If the count exceeds 100,000, hasMore=true will be returned
• A bug has been fixed to return a 400 error (Bad Request) instead of a 500 error (Internal Server Error) for invalid request parameter names (#11435)
  • This applies when non-List/Map/array parameter names are appended with []
• The 403 error behavior of the process start API (/API/PE/ProcessInstance/start) has been clarified (#11455)
  • A 403 error is returned when the app cannot be viewed, and a 400 error is returned when the app can be viewed but the process cannot be started

Plans for Future Changes

The following specification changes and system infrastructure updates are planned for future versions.

Schedule for Version 18.1 (August 2026)

• All apps and data items will become visible to all users (#11510)
  • Currently, the visibility of apps and data items is determined based on whether the app has data access permissions or was involved in processing
  • In the future, we will make it possible for all users to see what apps are available and what data items each app contains.
  • There are no changes to the visibility specifications for the cases themselves or the values ​​of the data items (cases that were previously inaccessible will not become visible)

Schedule for Version 19.0 (April 2027)

• 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
  • Discontinuation that were scheduled to be in Ver. 18.0 will be postponed for one year
• The URL format used in the Catching Message Intermediate Event (HTTP) will be deprecated
  • /System/Event/IntermediateMessage/{AppID}/{NodeNumber}/receive
  • Use the following URL format for the Receive Task (HTTP)
    • /System/ReceiveTask/HttpPost/{AppID}/{NodeNumber}/receive
  • If you are using IP Address Restrictions, you will need to make configuration changes to align with the URL changes
• The flow parameter used to specify branching destinations in the Task Processing API (/API/PE/Workitem/{workitemId}/Form/save will be deprecated