10 SEPTEMBER 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?
- New features
- General enhancements
- Resolved issues
- Breaking change
- 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 optimizes business operations by orchestrating analytics, AI, and RPA, leveraging cloud infrastructure and capabilities, and focusing on delivering added value on Azure and Power Platform in the case management domain.
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.8 introduces features that enable Agentic solutions, enhance developer experience and improve security and compliance requirements. All new features and enhancements aim to revolutionize the way you work, and save you valuable time. Main benefits include:
- AI Agent integration
- Enhanced Config Set management tools for workflow developers
- Case automation capabilities
- Enhanced UI and UX
New features
- Integration with Azure AI Agent service: Elevate your solutions with the new AI Agent Consumer activity, enabling seamless workflow integration with AI Agent services from Azure AI Foundry.
For details, see this article. - External source-control support: We have integrated with Azure DevOps (Git) to commit and deploy Workflows.
- Additional capabilities for Config Sets: We have updated the Config Sets for the following additional capabilities:
- Config Set inheritance and YAML override: As a workflow developer, you can create a base Config Set to inherit its configuration and manage custom configuration with minimal changes and easier configuration maintenance.
For details, see this article. - Auto-lock for document editing: Improve collaboration between developers. When you edit a document, it automatically gets locked, so other developers can access the Config Set and work on other documents while the locked documents are in read-only mode.
- Change tracker in Config Set: You can view an audit log of changes done in the Config Set and review previous document versions with the Change Log option in the DocumentSet Editor. The log displays the changes in descending order, with recent changes on top of the list.
- System type ConfigSets: Enhanced ConfigSet management and read-only mode for application presets.
- Improved ConfigSet deployment with added merge options.
- Config Set inheritance and YAML override: As a workflow developer, you can create a base Config Set to inherit its configuration and manage custom configuration with minimal changes and easier configuration maintenance.
- As an Administrator, you can set the new
System.Persistence.ForceDefaultModeapplication variable to force default persistence mode on all workflow executions for one-click service request logging,
For details, see this article. - List Files activity: We have introduced a new List Files workflow runtime activity that generates a list of files in storage location and optimizes the file processing options.
For details, see this article. - Rule-based Case Automation: As a workflow developer, you can configure rules for open cases to automatically trigger other workflows according to all implementation needs and cover multiple use cases like time-based reminders and escalation processes. With case automation the case processing happens with minimal manual intervention thus increasing system efficiency.
For details on configuring rules, see this article.
General enhancements
- Portal enhancements: We have upgraded the portal with improved features for an enhanced user experience.
- Smoother portal grid transitions and user-state auto save: When a grid view is changed, a pop-up message is displayed to confirm saving the unsaved changes to the view.
- You can now export the portal grid data quickly to a lightweight CSV format.
- Enhanced observability for rule-set evaluation in runtime.
- Configure default lock duration in Message Bus pipelines: As a workflow developer, you can configure the
MaxAutoLockRenewalDurationproperty in the Message Bus pipelines to ensure long-running document processing tasks can complete successfully without timing out.
For details, see this article. - Enhanced Case handling: We have introduced a new built-in command Copy Case Conversation Items by Unique Id to copy specific conversation items by their unique Ids and let you decide whether to copy conversation attachments or not.
For details, see this article. - Enhanced built-in command activities to improve Case Conversations functionalities.
For details, see this article. - Message Bus Listener support for “Dead Letter Queue” (DLQ) and the ability to start instances in the master scope.
- Enhanced expression function UsersInGroup(rt, ) for generating group member lists.
- Enhanced developer experience in the App Studio and Global Integration Settings.
- Incremental database performance optimization.
- Incremental update of core libraries and security alignments.
Resolved issues
| Component | Issue | Ticket # |
|---|---|---|
| File connection | The configuration incorrectly allowed succeeding backslashes in the host and path fields. | 3656893 |
| Portal | Issue with overwriting system views. | 3981707 |
| View selector and grid filter section appeared below the grid after clicking the Collapse Header option. | 3804270 | |
| The image properties dialog in the email editor was cut of. | - |
Breaking change
The Database Listener and CRM activities are deprecated and are planned to be removed from the Administration site in the upcoming release.
To ensure compatibility in future upgrades, make sure your solutions do not include these activities.
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.
