This page lists planned changes to Questetra’s product specifications and system infrastructure. See the Updates by Environment page for rollout dates and update status.
Timing to Be Determined
- All applications and data items will become visible to all users (#11510)
- This was originally planned for Ver. 18.1, but was not included in Ver. 18.1.0. It is planned for a future version.
- Currently, application and data-item visibility depends on cases in applications for which users have viewing permission and cases they have worked on.
- In the future, all users will be able to see which applications exist and which data items each application contains.
- Visibility of cases and data-item values will not change. Users will not gain access to cases they could not previously view.
Planned for December 2026
- Access to areas outside /API/ using Basic authentication or Bearer authentication (OAuth 2.0 access tokens or personal access tokens) will be prohibited (#11639)
- All public APIs are under /API/. These credentials will no longer grant access to screens or other areas outside /API/.
Planned for April 2027
- Legacy request parameters that include data definition numbers (such as data[XX].input) will be discontinued for Message Start Events and Receive Tasks (HTTP)
- If a legacy parameter is used, a warning will be written to the Case Log.
- Update the HTTP sender to specify parameters by field name.
- This discontinuation, originally planned for Ver. 18.0, has been postponed by one year.
- The legacy URL used by Receive Tasks (HTTP), formerly called Intermediate Message Events (HTTP), will be discontinued
- /System/Event/IntermediateMessage/{appId}/{nodeNumber}/receive
- Use the following URL instead:
- /System/ReceiveTask/HttpPost/{appId}/{nodeNumber}/receive
- If you use IP address restrictions, update the settings to reflect the URL change.
- The flow parameter used to specify a transition path in the task-processing API (/API/PE/Workitem/{workitemId}/Form/save) will be discontinued.
These planned items were previously listed in the Version 18.1 article. As each change is implemented, it will be documented in the relevant Version article and this page will be updated.
