2025-04-20 Ver.17.0 Chat Feature will be revamped

2025-04-16: Added the new name of the chat feature, [Collab Chat]
2025-04-21: Added new changes to the details for version 17.0.0
2025-05-19: Added the details for version 17.0.1
2025-05-21: The update to Ver. 17.0.1 has been postponed from 2025-05-25 Sun. to 2026-06-08 Sun.
2025-06-05: Added new changes to the details for version 17.0.1
2025-07-07: Added the details for version 17.0.2
2025-08-08: Added the details for version 17.0.3

Release Overview

Updating Date

• Workflow platforms for Rapid Update
  • Ver. 17.0.0：2025-04-20（UTC）
  • Ver. 17.0.1: 2025-05-25 (UTC) 2025-06-08 (UTC)
  • Ver. 17.0.2: 2025-07-13 (UTC)
• Workflow platforms for Scheduled Update and Trial mode
  • Ver. 17.0.0: Not updated
    • Updated to Version 16.2.2 on 2025-04-20 (UTC)
  • Ver. 17.0.1: 2025-05-25 (UTC) 2025-06-08 (UTC)
  • Ver. 17.0.2: 2025-07-13 (UTC)
  • Ver. 17.0.3: 2025-08-17 (UTC)

Changes to be Noted

• The chat feature will be revamped (the name will also be changed from [Open Chat] to [Collab Chat])
• Old format URL in Message Start Event (Form) will be discontinued
• When inputting CSV data for [Import Users], the format “!Organization name” to specify the affiliation as a Leader has been discontinued
• The following APIs will be discontinued in Questetra REST API:
  • The APIs for searching Organization/Role affiliation without pagination
  • The API to obtain processing form screen information
• Check out the plans for changes in future versions [Plans for Future Changes] at the bottom of this page

---

Details for Version 17.0.0

($.: appended 2025-04-21)

Changes of Functions for All Users

Workflow

Start

• Changed the design of icons and buttons on the App Details screen (#10400)

Process Details

• Change display style of Offered candidate/Team Task assignee (#10474)

File-type

• Attachment files that are determined to be malware now results an input error (#10519)
  • Files suspected of being malware will be flagged as such
  • Task processing etc. will result in an input error, and Message Start Events etc. will result in an input error, causing the processing to fail
  • Malware detection may not be completed immediately, so even if a file is under suspicion of being malware, it may not result in an input error in the processing step
    • Upon completion of the malware check, a notification will be displayed within the Process details and subsequent Steps to indicate any suspected malware
• For files other than those labeled “No threat”, additional statuses such as “Identified as malware”, “Checking in progress”, and “Not subject to malware check” will be displayed (#10592)
• Files suspected of containing malware will no longer be available for download (#10593)
  • If a file is identified as malware, it will be unavailable for download

Collab Chat (formerly named Open Chat)

It will transform from being an open communication tool where all users can search and view messages into a communication tool between members who are participating in a channel.

Ver.17.0 Open Chat will be revamped (April 2025)

• $. The chat feature is renamed from “Open Chat” to “Collab Chat” (#10624)
• The concept of “Channels” was introduced to allow communication limited to participants (#9985, #10597)
  • Like business chat tools such as Slack, communication is centered on channel participants
  • The concept of Following/Followers will no longer exist
  • Users select a channel to post to
  • There are two types of channels: Public Channels and Private Channels
    • Public Channels
      • Channels that users can join themselves
      • Posts can be viewed by non-members
      • Only participating members can post
    • Private Channels
      • Users cannot decide whether to participate or not
      • Participating members are determined by Organization affiliation, App/Process permissions, and addition by administrators
      • Only participating members can view/post
  • Types of Channels
    • User-Created Channel
      • User-Created Public Channel
        • Public Channel
        • “Topics” created up to version 16.2 will be migrated to “Public Channels”
      • User-Created Private Channel
        • Private Channel
        • Channel admins can add/remove admins/members
        • The user who creates the channel becomes the first channel administrator
    • Automatically created channels
      • Organization Channel
        • Private Channel
        • One channel per organization is automatically created
        • Users who belong to the target organization and its subordinate organizations will be channel participants
        • The root organization channel is the channel in which all users are participating members
        • Supports “Share Posts with: Organization” up to Ver. 16.2
      • App Channel (e.g. #m100)
        • Private Channel
        • The following users who can view the App will be participating members
          • Users who can start Processes for the App
          • Users who can view any of the Processes for the App
          • Users who have any of the App Authorizations for the App
      • Process Channel (e.g. #p12345)
        • Private Channel
        • The following users who can view the Process will be participating members
          • The user who starts the Process and the users who are the Operators/candidates for the Tasks
          • Users who have either [Process Manager], [Data viewer], or [Data viewer (only Progress Information)] for the App in which the Process was started
  • Every post is associated with only one channel
    • Posts associated with multiple channels (topics) cannot be made
    • It is not possible to link a post with a different channel later
    • The hashtag “#sample” in the message acts as a link to the specified Channel
    • In principle, mentions will only be valid for members participating in the channel (Ver. 17.0)
• Only channel members can be mentioned using @username (#10504)
  • User mentions only work if you specify channel members
    • You cannot mention users outside of a channel
    • If the format for mentions is used for Users outside the channel, it will be treated as normal text
  • Only channel members will appear as candidates for mentions
• Organization mentions (%organization name) now only work in Organization Channels (#10602)
  • An Organization mention only works if the Organization and its subordinate Organizations are specified in the Organization Channel
    • You cannot mention Organizations outside of a channel
    • If the format for mentions is used for Organizations outside the channel, it will be treated as normal text
  • Only the eligible Organizations will appear as candidates for mentions
  • All Organization mentions work in the Root Organization Channel
    • However, there is a limit to the number of target users (1000), so if this limit is exceeded, the mention will not work (as in Ver. 16.2 and earlier)
• Support for switching the display area on the right side on and off is now available (#10509)
  • It will be hidden by default
  • The main display area has been widened
• Posting messages from the timeline displayed on the right side is now possible(#10565)
• Clicking on a User name no longer displays the right side panel (#10619)
• Changed message search to a channel-specific search function (#10576)
• Removed the following functions
  • [Good!] and [Good! to Everyone] (#10437)
  • [Popular Topics] (#10510)
• Prevent messages from being posted if they contain attachments determined to be malware (#10520)
  • Files suspected of being malware will be flagged as such
  • Messages cannot be posted with suspicious files attached
  • Malware detection may not be completed immediately, so even if a file is suspected of being malware, an error may not occur when posting a message
    • Once the malware check is complete, a message will be displayed indicating that malware is suspected
• For files other than those that are not suspected of malware, “Identified as malware”, “Checking in progress”, “not subject to malware check,” etc. is displayed(#10592)
• Files suspected of containing malware will no longer be available for download (#10593)
  • If a file is identified as malware after uploading, it will no longer be available for download

Dashboard

• Discontinued Popular Topics (#10583)

Account Settings

• Changed supported languages (#10384)
  • Supported languages: Japanese and English
  • labs: Korean, Traditional Chinese, Simplified Chinese
    • labs French, German, Portuguese and Spanish discontinued
    • Added Traditional Chinese (Taiwanese) to labs
  • The language settings of users who have specified a discontinued language will be forcibly changed to English when updating to Ver. 17.0.
• Changed the format of the notification email when an account is locked to HTML email (#10405)
  • Sent when there are consecutive failed password login attempts
• Shorten the fixed message part of the subject line in deadline notification emails (#10498)

Changes of Functions for Workflow Designers

New App

• App archives (qar files) exported using workflow platform Ver. 13.3 (March 2022) or earlier will no longer be able to be imported (#10418)

App Settings/List

• The update user is now recorded when editing App definitions, Properties, Work Manuals, and Releasing apps (#10144)
  • It can now be added to display columns in App list
• In the App list, Apps that you have updated will now appear at the top of the list (#10145)
• Added Star (★) as a sorting item in the App list (#10528)
  • [System Settings] < [App Authorization] also supports this

App Authorizations

• Changed the display style of Authorized Users (#10489)

Variable => App Config Variables

• App-specific Variables renamed to App config Variables (#5627)
• Changed the name of the workflow platform common System Variables to System Constants (#5627)
  • Only ${var[applicationRoot]}

Workflow Diagram

• Fixed grammatical errors in the message for App Definition Errors (settings errors) (#10539)）

Human Task

• Fixed grammatical errors in the message for App Definition Errors (settings errors) (#10539)

Timer Start Event

• Changed the format of error notification emails for processing failures to HTML emails (#10320)

Message Start Event (Form)

• Discontinued old format URLs (#9511)
  • Old format URL: /System/Event/MessageStartForm/view
  • Redirects to the current format URL will be stopped, and users will no longer be able to access the form page by accessing the old format URL

Throwing Message Intermediate Event (email)

• Fixed grammatical errors in the message for App Definition Errors (settings errors) (#10539)

Update Data/Gateway

• Added malware check feature to file object (QfileView) (#10591)
  • Available when referencing a File-type Data Item in a SpEL expression
  • For details, see the Script Task section

AI Agent

• $. Added a new Step [AI Agent] (#9580)
  • Eligible in Basic/Advanced/Professional edition
  • An Auto-step for generating text data with AI: AI interprets instructions, reads the necessary data items, and overwrites the items
  • Usage is limited based on the contract edition and number of contract users

Update CSV Data

• Added the option to specify whether to use double quotes when saving query results in CSV/TSV data (#10348)
  • In addition to ‘Always’ (enclosed in double quotes), you can now select ‘Only when necessary’
• Added an option to save query results to allow each cell’s value to be saved as a separate Data Item (#10512)
  • You will be able to set the first cell from the top left to String-type Data Item A and the second cell to String-type Data Item B, and so on
  • For example, you can collect “total number of days worked” and “total number of hours worked” at the same time and save them as separate data items
  • You can specify String-type (single line) as the Data Item to save
• Added an option to not treat the first line as a column name (header line) for input CSV/TSV data (#10522)
  • Column names are automatically given as “col1” and “col2”
  • It can also handle simple multi-line strings (without tabs)
    • Treated as TSV data with one column

Start: XXX/Timer Start: XXX/Automatic Processing Task (Almost all of Advanced and above)

• Set a limit on the number of characters that can be entered into text fields/text areas (#7183)
  • Limit: 50,000 characters per input field
  • Limit: 500,000 characters for all input fields combined
• Fixed grammatical errors in the message for App Definition Errors (settings errors) (#10539)

Google

• Changed specifications and internal implementations in the following automated processing steps
  • Google Drive: Search Folder (#10486)
    • Removed the deprecated setting item [C1-deprecated: OAuth2 Settings]

Amazon Web Services

• Added the following automated processing steps (Service Task)
  • Amazon Bedrock: Stability AI: Generate Image (#10495)
    • Generate images using Stability AI running on Amazon Bedrock
    • Three models available: Stable Image Ultra, Stable Diffusion 3 Large and Stable Image Core
    • This is the successor to [Amazon Bedrock: Stable Diffusion: Image Generation], the deprecation of which was announced in Ver. 16.2.1.
• Changed specifications and internal implementations in the following automated processing steps
  • Amazon Bedrock: Anthropic Claude: Chat (#10428)
    • Cross-region inference is now supported
    • Specifying PDF as input is now supported
    • Updated available models
      • Removed models scheduled for retirement in 2025-07, such as Claude 2
      • Added Claude 3.7 Sonnet
    • Supports Extended Thinking Mode
    • If the response is empty, the Process will now end abnormally

OpenAI

• Changed specifications and internal implementations in the following automated processing steps
  • OpenAI ChatGPT: Chat (#10515)
    • Added “o1” and “o3-mini” to available models
    • If the response is empty, the Process will now end abnormally

GitHub

• Added the following automated processing steps (Service Task)
  • GitHub: Create/Update Textfile (#10594)
    • Create/update a text file in the specified GitHub repository
  • GitHub: Get File (#10595)
    • Retrieves the specified file from the specified repository on GitHub
      • You can also get the hash value of a file

Throwing Message Intermediate Event (HTTP)

• Changed the format of error notification emails for processing failures to HTML emails (#10311)
• Now it logs information about HTTP requests to the [Process Log] (#10407)
  • Error notification emails will no longer include request details
    • Considering security, we will move towards not including Data Item values in notification emails
  • If you want to check the details, refer to the [Process Log]
• Fixed grammatical errors in the message for App Definition Errors (settings errors) (#10539)

Message Start Event (HTTP)

• Changed the format of error notification emails for processing failures to HTML emails (#10318)
• When a Process fails to start, information about the HTTP request is now logged in the [Process Log] (#6255)
  • Error notification emails will no longer include request details
• Revised the conditions for sending error notification emails when launch fails, and reduced the frequency of sending them (#10453)
  • Changed so that error notification emails will not be sent in the cases where the app cannot be identified, the node cannot be identified, or the API key is incorrect
  • It is not recorded in the [Process Log]

Receive Task (HTTP)

• Changed the format of error notification emails for processing failures to HTML emails (#10313)
• Improved error messages in HTTP responses when the received HTTP request is valid (#10148)
  • In cases where the App ID, node number, Process ID, and API key are all correct, but the device is not ready to receive HTTP requests (the token has not reached the Receive Task)
• When reception fails, information about the HTTP request is now recorded in the [Process Log] (#10452)
  • Error notification emails will no longer include request details
• Revised the conditions for sending error notification emails when reception fails, and reduced the frequency of sending them (#10459)
  • If any of the App ID, the node number, the Process ID or the API key is incorrect, the error notification email will not be sent

Receive Task (Webhook)

• Improved error messages in HTTP responses when the received HTTP request is valid (#10148)
  • In cases where the App ID, node number, Process ID, and API key are all correct, but the device is not ready to receive HTTP requests (the token has not reached the Receive Task)

Script Task

• Changed the format of error notification emails for processing failures to HTML emails (#10315)
• Added methods for malware checking to the QfileView class (#10591)
  • getMalwareScanStatus(): Returns the malware check status
    • null: Files saved before malware checking was enabled
    • “SCANNING”: Scanning in progress
    • “NO_THREATS_FOUND”: No threat found
    • “THREATS_FOUND”: Files identified as malware
    • “UNSUPPORTED”: Files that cannot be checked, such as encrypted files
    • “ACCESS_DENIED”, “FAILED”, “UNKNOWN”: Cases that do not occur during normal operation
• Added the following methods to the FeedServiceWrapper class (#10547, #10621):
  • createPublicChannel(String): Creates a public channel
    • This is implemented in version 16.2.2, but as of version 16.2.2, this method does nothing even if it is called
    • This will be effective after updating to Ver. 17.0.
• Added the following methods to the FeedServiceWrapper.FeedMessageWrapper class (#10547):
  • setChannel(String): Specify a Channel
    • From version 17.0 onwards, posts are not automatically associated with Processes, so you need to explicitly specify the posting destination
    • Specify the posting destination using either setChannel(String) or setShareQgroup(QgroupView)
    • If neither is specified, posting a message will result in an error
    • setChannel(String) and setShareQgroup(QgroupView) are mutually exclusive
    • setChannel('g{organization ID}') also specifies the Organization Channel

Questetra Form JavaScript API

• Added malware check items to the File-type Data Item values (#10590)
  • For details, see the Script Task section

Changes of Functions for System Administrator

• Implemented malware check for File-type Data Items/chat attachments (#10132)
  • The contents of compressed files such as zip files are also checked, but encrypted zip files are not checked

User

• When inputting CSV data for [Import Users], the format “!Organization name” to specify the affiliation as a Leader has been discontinued (#9543)
• Fixed the following Bugs
  • When inputting CSV data for [Import Users], if a non-existent Organization name is specified at the beginning of the Organization affiliation specification, no Organization is displayed as the Main Organization on the confirmation screen (#10478)
    • The first valid Organization will now be treated as the Main Organization

System Authorization

• Addition/removal of System Authorization is now output to the [System Log] (#10457)
• Changed the display style of the list of authorized Users (#10488)

App Authorization

• Changed the display style of the list of authorized Users (#10489)

Collab Chat (formally named Open Chat)

• Added the authority to create Public/Private Channels as a System Authorization (#10546)
  • Public Channel Creator and Private Channel Creator
  • By default, all users are granted the privileges
  • [Collab Chat] < [Channel Creators] menu added
• Allow System Administrators to manage Channel Administrators for Private Channels (#10502)
  • [Collab Chat] < [Channel Administrators] menu added

Changes of Functions for Questetra REST API Developers

• Discontinued the APIs that have been scheduled as deprecated
  • The APIs for searching Organization/Role affiliation without pagination (#9504)
    • /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
  • The API to obtain processing form screen information (#9505)
    • /API/PE/Workitem/Form/viewXml
• The API for retrieving a list of Users (/API/User/Quser/list) now also supports searches including subordinate Organizations (#10505)
  • Parameter: includeDescendants (boolean)
    • false: Search for Users who belong directly to a specified organization
    • true: Search for Users who belong to the specified Organization or subordinate Organizations
• Added the ability to sort Apps by Star (★) on top when using the API to retrieve a list of Apps (#10523)
• Added an item related to malware checks to the File-type Data item values in the API for retrieving process details, Process list, and Task list (#10589)
  • The malwareScanStatus attribute indicates whether the file is Scanning, No threats, Malware detected, or Cannot be checked

---

Details for Version 17.0.1

(Appended 2025-05-19, $.: Appended 2025-06-05)

Changes of Functions for All Users

Workflow

File-type

• $. Extended the deadline for malware detection of attached files to 2 hours (#10718)
• $. If the malware check results cannot be obtained, the check status will be changed to “Unable to check” (#10719)

Collab Chat (formerly named Open Chat)

• Added the ability to see the target channel on the screen displaying a specific thread (#10648)
• Added a link to return to the channel page after setting up members for a Private channel (#10645)
• Changed latest post timestamps in the User-created channels list to relative format (e.g., “X minutes ago”) (#10667)
• Enabled display of relative timestamps for latest posts in channels that existed before the Ver.17.0 update (#10696)
• Improved performance in the channel list on the left side menu of Collab Chat (#10668)
• Created a separate section for App channels that lists channels for specific Apps (#10644)
• $. Extended the deadline for malware detection of attached files to 2 hours (#10718)
• $. If the malware check results cannot be obtained, the check status will be changed to “Unable to check” (#10719)
• Fixed the following bugs:
  • HTML tags are enabled in the poster’s name in notification emails (#10641)
  • Incorrect count of new messages when threads are linked to multiple channels (#10652)
  • System error occurs when posting with mentions to non-members in a Process channel (#10703)
  • System error occurs when clicking a relative timestamp link in a Public channel the user hasn’t joined (#10685)
  • Message/comment post form appears in Public channels the user hasn’t joined (#10693)
    • Now hidden as expected
  • $. When a user who does not belong to any organization attempts to open the Collab Chat screen, a system error occurs (#10731)
  • $. When a post that mentions a user who is not a member of a process channel is submitted in that channel, a system error occurs (#10703)

Changes of Functions for Workflow Designers

AI Agent

• $. Apply usage limits as follows (#10640)
  • Set a daily usage fee limit for Generative AI models
    • The usage fee for Generative AI models is calculated based on the total number of input and output tokens
    • If the limit is exceeded, the service task will fail to process
    • The limit resets every day, allowing the service task to be used again
  • The limit is calculated by multiplying the number of user accounts (number of seats for annual contracts, actual number of users for monthly contracts) by a coefficient specific to each edition

• Fixed the following bugs:
  • Typo in the model name of the [AI Agent] Task (#10672)
  • Workflow apps with an [AI Agent] Task turn to a white screen when clicking the visibility/editability settings button in the Data Item tab (#10671)
  • Misalignment in the display position of app name in the App Edit screen (#10675)
  • Zoom icon appears in front of the Task Edit window (#10681)

Changes of Functions for System Administrators

• In [Channel Creator] permissions, added support to return to the permissions list after adding a permission (#10666)
• In [Collab Chat], enabled deletion of Public channels (#10695)

---

Details for Version 17.0.2

(Appended 2025-07-07)

Changes of Functions for All Users

• Fixed the following bugs:
  • Some error pages have a corrupted page layout (#10781)

Workflow

• Fixed the following bugs:
  • The “Start a new Process with these data” button is displayed on the print page for process details (#10778)
  • When the process names cannot be displayed completely in the “Status” column in heat maps, etc., unnecessary horizontal scroll bars are displayed (#10795)

Collab Chat

• The search query for channel searches has been limited to 100 characters ( #10780)
• Added comments to some threads migrated from Ver. 16.2 indicating which channel the thread belongs to (#10791)
  • Applies to threads migrated from Ver. 16.2 that currently belong to multiple channels
    • This does not apply to threads created in Ver. 17.0 or later, as they belong to only a single channel
    • Exceptions to this rule include threads that existed before Ver. 16.2 and belong to multiple channels
      • When displaying only a thread, it may not be possible to identify all the channels to which it belongs
  • These comments are posted with the username of Questetra and the icon of Quest-kun
  • They are added to near the top of the thread as older posts
• Fixed the following bugs:
  • In the left side menu, unread information for channels of apps for which the user has only been granted App Administrator privileges may be incorrect.(#10771)
  • In channel search results, clicking “More” may not retrieve old threads ( #10809)

Changes of Functions for Workflow Designers

• Fixed the following bugs:
  • When updating data item editing permission settings in bulk on the App edit screen, a system error occurs if the number of columns in the data rows of the TSV file for bulk update is larger than the number of nodes (#10747).

---

Details for Version 17.0.3

(Appended 2025-08-08)

Changes of Functions for All Users

• Fixed the following bugs:
  • It may be possible to bypass the “Need to change password at the next login” setting and log in without changing the password (#10859)
    • Even if the password change is bypassed once, the “Need to change password” status remains the same

Changes of Functions for Workflow Designers

• Minor change in system prompt in [AI Agent] (#10871)
• Fixed the following bug:
  • Date-type data items specified in [Timer Intermediate Event] do not cause errors in the process even if they are changed to unsupported subtypes (#10832)

Changes of Functions for Questetra REST API Developers

• Fixed the request parameter description in the task processing API (/API/PE/Workitem/{workitemId}/{workitemId}/Form/save) (#10905)

---

Plans for Future Changes

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

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 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

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.