Genpact Cora Knowledge Center


Cora SeQuence 9.9 Release Notes

03 NOVEMBER 2022

Welcome to the Cora SeQuence Release Notes.

As they become available, additions and updates to these release notes can be found here.
The latest releases appear at the end of the list.

What's in the Release Notes?

  • About Cora SeQuence
  • What's new in Cora SeQuence V9.9
  • New feature
  • Resolved issues
  • Deployment

About Cora SeQuence

Cora SeQuence is an Intelligent Business Process Management Suite (iBPMS) that facilitates rapid build and change of high availability, mobile-enabled workflow applications. Cora SeQuence is built on the HotChange® technology, an architecture used for software development in the field of Business Process Management (BPM). HotChange® enables consultation in the field of design, development, implementation, and integration of information technology solutions for business processes. Business users and developers can seamlessly design and execute workflows on a single canvas using Dual View. Cora SeQuence is a low-code platform that also supports advanced development capabilities.

What's new in Cora SeQuence V9.9

Cora SeQuence V9.9 introduces a new and improved archiving mechanism to help you meet business and legal requirements for storing and retrieving data. Besides effective maintenance and costs, archiving also enables efficient data management and boosts your system's performance, by keeping the operational database lighter.

Main benefits

  • Flexible storage and purging policy configuration
  • User-friendly interface to search and retrieve archived data
  • Permission-based access to archived data
  • Support of a variety of storage solutions: Amazon S3 (Simple Storage Service), Azure Files, and network drives

New feature

  • The archiving feature extracts data from the Cora SeQuence database and moves it to the archive database, making sure that only operational data resides in the Cora SeQuence database.
    For more details, see this article.  

The new archive feature replaces the V9.4 archiving mechanism.

Resolved issues

ComponentIssueTicket #
Conversation ViewYou could not edit the subject of an existing email template.655946
When you downloaded an email with Chinese characters in its subject, the name of the downloaded file was wrong.994170
FormsThe Fetch/Return button did not refresh after you double clicked it.984706


Download the release package from the Cora SeQuence repository.

Contact Support to obtain credentials to access the Cora SeQuence repositories.

There several pre-build application deployment packages available, depending on the type of application that you are deploying. You install each Cora SeQuence application separately.

Site applicationsService applications
  • Administration
  • Flowtime
  • WebAPI
  • Job Execution Service (JES)
  • Background Runtime Service (BRS)
  • Active Directory Synchronization Service (ADSS)

When you deploy pre-built applications, you can choose between the Standard and Premium packages. The Premium package includes HotOperations. You can also build and deploy your own Cora SeQuence applications. 

Deploying the Flowtime Lite portal is similar to deploying the standard Flowtime application. If you deploy the Flowtime Lite portal on the same machine that hosts the standard Flowtime, use the application ID to distinguish between them.

Click here to see how to deploy Cora SeQuence in an environment with pre-built applications. 

For more details on installing and deploying Cora SeQuence, see this article.


When you upgrade from earlier versions, make sure that you follow this path V9.8.3 → V9.8.4 V9.8.5

For more information on database upgrade paths, see this article

Make sure that you have the latest PowerShell modules version. For PowerShell modules version mapping with Cora SeQuence version, see this article.
Click here to view a sample PowerShell script. Consider this sample for reference only, and do not copy-paste from here.

For development purposes, you can run Cora SeQuence with Microsoft SQL Server Developer Edition.

During upgrade, all product application folders are deleted and redeployed: 

  • Web and application 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.