Genpact Cora Knowledge Center

Support

Cora SeQuence 9.2.1 Release Notes

17 FEBRUARY 2020

This update includes a new feature and product enhancements. 

New features and enhancements

  • Analytics dashboards: To improve system performance, you can now set up caching for dashboard's data.
    For more information on analytics dashboards, see this article
  • SAP: The SAP activity is now available with the Premium package.
  • Administration application performance: First-time loading of Administration pages, components, and activities have been improved. 

Heads up!
Support for WS-Federation authentication method ends by December 2020.

Deployment 

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.

Deploying SAP

If your implementation requires integration with SAP, you need to run additional scripts after you deploy the Cora SeQuence database and applications.
For more details, see this article.

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

IMPORTANT
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.