05 NOVEMBER 2025
Welcome to the Cora Orchestration Release Notes.
As they become available, additions and updates to these release notes can be found here.
What's in the Release Notes?
- About Cora Orchestration
- What's new in Cora Orchestration?
- General enhancements
- Resolved issues
- Deployment
About Cora Orchestration
Cora Orchestration is an Azure-based Intelligent Business Process Management Suite (iBPMS) that combines workflow orchestration with generative AI and agentic capabilities to help enterprises increase productivity via process automation, reduce errors and accelerate innovation by embedding AI into core operations.
Cora Orchestration combines workflow orchestration with generative AI and Agentic capabilities to help enterprises:
- Increase productivity via autonomous process execution.
- Reduce errors through adaptive, AI-driven decision-making.
- Accelerate innovation by embedding AI into core operations.
- Improve agility with a scalable, AI-first architecture.
Using Cora Orchestration, an organization transforms customers’ experience, increases self-service actions, and improves visibility. The product allows companies to respond to business and regulatory needs with lower development time and cost.
What's new in Cora Orchestration?
Cora Orchestration V10.9 introduces updates and enhancements that enable building scalable, maintainable, and intelligent solutions, accelerating development while ensuring operational resilience.
General enhancements
- Convert email conversation items to EML files at runtime: You can use the new built-in command to automate, at runtime, the conversion of email conversation items to EML files for auditing or archiving purposes.
For details, see this article. - Rule-based dynamic email sending: The Email Sender job now supports a dynamic email sending mode, which allows emails from case conversations to be dispatched through multiple sending connections based on YAML-defined rule sets.
For details, see this article. - Set the default display mode of the Attachments View: You can now configure and set the default display mode of the Attachment View in the form. For example, you can choose to set the List and Preview tabs as visible by default or hidden, or display or hide the action buttons.
For details, see this article. - Open Config Sets in read-only mode for access-controlled users: We have enhanced the Config Set to enable the users, other than workflow developers, full read access to documents in ConfigSets. This enhancement is most suitable for support teams and non-technical users who require access to the documents.
- We have enhanced the UI/UX for internal source-control in the AppStudio.
- We have improved the configuration and validation of global integration settings, like Credentials, Email Sending Connections, Semantic Kernel, Translation Services, Message Bus pipelines, Service Bus Listener, Email listener, Connection Strings, and Kafka connections.
Resolved issues
| Component | Issue | Ticket # |
|---|---|---|
| Database | SQL Always Encrypted had compatibility issues. | 4175032 |
| Deployment | Listener activities were imported with an incorrect job scaling option, (“Single” instead of “Limited” or “Infinite”). | - |
| File Listener | Unnecessary SQL calls during the execution of the File Listener activity despite disabling the duplicate detection option (potential performance impact). | 4276739 |
| SQL Service Broker | Intermittent errors “Failed to renew Service Broker”. | - |
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 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.
