Genpact Cora Knowledge Center


Cora SeQuence 9.4.1 Release Notes

05 AUGUST 2020

This update includes enhancements to the Conversations View and the Email Composer reusable components. 


  • Conversations View component: 
    • Now supports Comment conversation type to display all case related comments at one place from within the case.
    • Supports user id tagged built-in commands.
  • Email Composer component: 
    • Now supports event handling. Status hooks to events enable Email Composer to perform actions per implementation.
    • Supports signature template.


There are six 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. 

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.

Before upgrade, make sure to update the PowerShell modules to the latest version.
Click here to view a sample PowerShell script. Consider this sample for reference only, and do not copy paste from here.

With Cora SeQuence applications, also upgrade the database to this version.
For more information on database upgrade paths, see this article.

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

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.