08 MAY 2025
This update includes resolved issues and security updates across all components.
Resolved issues
| Component | Issue | Ticket # |
|---|---|---|
| Administration | The Access Level field couldn't be updated for users with extended properties. | - |
| Audit Log | The current user time-zone offset was not applied correctly in the Audit Log control. | - |
| Portal | Clearing a filter with a dropdown list of multiple selections didn't refresh the data in the grid. | 3570955 |
| Synchronization issues when switching between header filters and the filtering panel. | - | |
| Incorrect filtering counter after removing a filter that was loaded from a stored view. | 3578087 | |
| The case preview data was not refreshing correctly when clicking on case preview icons sequentially. | - | |
| The portal ignored the setting of the default solution and incorrectly navigated first time users to “All cases” instead of to "My Work”. | 3580643,
3573343 | |
| Incorrect tab focus navigation after closing the History tab. | - | |
| The current user time-zone offset wasn't applied correctly in the History view. | 3573931 | |
| Issue with loading the grids after changing the portal interface language to non-English options. | 3582736 | |
| Rich Text Editor | Issue with setting the table and cell dimensions from the table editing tool. | - |
| Issue with applying pre-set CSS styling in the table editor tool.
NOTE
|
- | |
| Issue with editing the cell and table size properties from the table editor wizard. | - | |
| Incorrect frame size for the image properties wizard. | - | |
| DocumentSet | Unnecessary alert when closing an unchanged YAML file while editing another YAML file. | - |
| An unclear error message encountered while saving a document with a long file name. | - | |
| Observability | The logger didn't create new rolling log files. | - |
| Security | General security hardening. | - |
| Solution Configuration | The "Address To" section in a solution crashed when no master workflow was set for the solution. | - |
| UX Studio | Conflict between security hardening and dynamic JS code in the form designer. | - |
Breaking changes
- Updated input validation for stored view names:
- The input validation for stored view names now restricts special characters. Allowed characters include alphanumeric, space, underscore, hyphen, ampersand, dot, and parentheses.
- Upgrade advisory: While upgrading from a previous version, make sure that the existing stored view names comply with the updated restrictions. Remove any invalid characters from the view names before the upgrade.
- Updated HTTP Header default value:
- The X-XSS-Protection HTTP header default value is updated to 1 in the IIS apps web config files.
<system.webServer>
<httpProtocol>
<customHeaders>
…
<add name="X-XSS-Protection" value="1" />
</customHeaders>
</httpProtocol>
</system.webServer> Deployment
Download the release package from the Cora Orchestration repository.
NOTE
Contact Support to obtain credentials to access the repository.
There are six pre-built application deployment packages available, depending on the type of application that you are deploying. You install each Cora Orchestration application separately.
| Site applications | Service applications |
|---|---|
|
|
Click here to see how to deploy pre-built applications.
For more details on installing and deploying applications, see this article.
Check if you need to upgrade your database for this version.
For more information on database upgrade and pre and post-upgrade procedures, see this article.
Before upgrade, make sure that you update the PowerShell modules to the relevant version.
For more information, see this article.
Click here to view a sample PowerShell script. Consider this sample for reference only, and do not copy paste from it.
IMPORTANT
Use Microsoft SQL Server Developer Edition for development purposes only.
During upgrade, all product application folders are deleted and redeployed:
- Web and App config files are overwritten in each release. You need to reapply your custom configuration settings after the upgrade.
- All custom files located in the application folders are also deleted. Custom files should be packaged as a custom application NuGet.
Files in the central configuration location are not changed.
For more details, see this article.
For details on Cora Orchestration platform support, see this article.
