04 MAY 2021
This update includes some resolved issues.
|Non-administrative users with Read and Write permissions to a lookup table couldn't see the table.
|A non-global admin user with Read and Write permissions on a workflow with two lookup tables couldn't see the workflow in the Administration site.
|From the web interface, when you forwarded an email with the original email as a .eml attachment, the following error occurred:
Cannot insert the value NULL into column 'fldContentType', table 'dbo.tblAttachments' from email listener
Download the release package from the Cora SeQuence repository.
Contact Support to obtain credentials to access the Cora SeQuence repositories.
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.
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.
With Cora SeQuence applications, also upgrade the database to this version.
For more information on database upgrade paths, see this article.
Before upgrade, make sure to update the PowerShell modules to the latest 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 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.