28 OCTOBER 2026
Welcome to the Orchestration AI Release Notes.
As they become available, additions and updates to these release notes can be found here.
What's in the Release Notes?
- About Orchestration AI
- What's new in Orchestration AI?
- New features
- General enhancements
- Resolved issues
- Known issue
- Breaking changes
- Limitations
- Deployment
About Orchestration AI
Orchestration AI solution facilitates Agentic AI capabilities, bringing intelligent, context-aware assistance into rapid creation of business process applications that work on top of legacy systems to orchestrate best-of-breed digital solutions, and harness human expertise.
Orchestration AI combines process orchestration with Agentic AI and enables organizations to automate tasks, support decision-making, and dynamically adapt to changing business conditions. Built on cloud infrastructure and enhanced for Azure and Power Platform, the solution delivers increased value not just in the case management but other domains too.
With Orchestration AI, an organization can transform customers’ experience, increase self-service actions, and gain greater operational visibility. The Agentic AI capabilities further enhance these outcomes by providing real-time insights, guiding users through complex processes, and reducing manual effort. The solution enables companies to respond to evolving business and regulatory requirements with greater agility, while lowering development time and cost.
What's new in Orchestration AI?
Orchestration AI V11.5 introduces new capability to expose Workflows as MCP tools for AI Agents (available for SaaS offering with Agentic Fabric enabled), new deployment tool for implementation and continued platform improvements.
New features
- JES host grouping: For Improved scalability for multi-host solutions. JES deployments can now be optimized by grouping hosts, with a simplified job management interface.
Every JES host registers with a group name, and every job is assigned to a host group. A job runs only on hosts inside its group. JES (Job Execution Service) hosts execute scheduled and system jobs. Previously, each job pointed at one named host or at any host.
For details, see this article. - Health Check Workflows: We have introduced a new built-in command Return Health Check Result to get better visibility into system health and to surface custom health check workflow results to the integration dashboard.
For details, see this article.
General enhancements
- Deployment Set Tool updates: We have enhanced the Deployment Set Tool with the following functionalities:
- Import and Export a Deployment Set to, and deploy one from, an external file storage location (file connection).
- Manage Deployment Sets through a redesigned UI.
- Support all configuration types under the global settings.
- Align the order of the modules for export/import process.
- File Handling at scale: The activities File Command and File Listener now support configurable folder-scan limits, and consistent bulk-delete behavior across all storage types.
The List Files activity is now renamed as File Command to better reflect its capabilities, this is not a breaking change, no action is required to adjust existing implementations.
For details, see this article. - Decoupling template data from instance data: Improve deployment stability by removing the risk of unintended cascading deletes for activity and workflow templates.
- Database Storage Optimization: Large data from Error Handler and Email activities can now be offloaded to external storage, easing database load and reducing storage costs.
- System Maintenance: The cleanup jobs are now consolidated and enabled by default, requiring less manual upkeep.
- Observability Enhancement: Workflow execution trace ID is now persisted and exposed via the workflow object, making it easier to trace and troubleshoot issues.
- Process Lab improvements for faster troubleshooting: Connect to workflow instances from a filterable instance list and preview Error Handler message.
Resolved issues
| Component | Issue | Ticket # |
|---|---|---|
| Email editor | Email editor showed issues when email body message contained large embedded images of over 200 KB. | 5345623 |
| Portal | While scrolling down, anchoring the grid handlers had issues. | 5707240 |
Known issue
For details, see this article.
Breaking changes
- Deprecation warning: In future release the following capabilities will no longer be available:
- Customized applications: Build and deploy your own Cora SeQuence applications.
- We are deprecating the SDK-like infrastructure that supported this scenario:
- access to our NuGet feed (having Genpact* packages)
- VSIX Visual Studio extension
- access to the boilerplate application builders
- For JES, the existing jobs are migrated automatically to a group called
Default. Review the job assignments and plan new groups where needed. - List Files activity is renamed to File Command activity.
- SSB Cleanup system job is renamed to SSB Housekeeping.
Limitations
The Deployment Set feature in the Phase 1 (V11.4) release has some known technical limitations.
Refer to the Limitations and workarounds section in the article to understand current behavior and recommended workarounds.
Deployment
Download the release package from the Orchestration AI repository.
NOTE
If the files you are looking for are not in the repository, then contact Support to get access to the new repository location and 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 Orchestration AI 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 Orchestration AI platform support, see this article.
