26 APRIL 2021
This update includes some resolved issues.
|ADSS||Configuring ADSS to work with the AzureKeyVault for the connection string had issues.|
|Case attachments||An attachment with a comma in its name was added as two different attachments.|
|Case conversations||RE: and FW: were added more than once in the email subject when you replied to or forwarded an email conversation.|
|Database||Files were not successfully copied from the database to the external storage because of connection issues with the database.||317723|
|When importing a workflow with a variable, the variable was not created in the UWF table in the database.||344819|
|ElasticSearch||While searching for an instance in Flowtime, the results appeared broken.|
|Email Listener||The Email Listener did not create instances for email attachments with special characters.||349659|
|Flowtime||The system prompted an error when you selected the Revert to Saved View option for a grid view.||356465|
|An error was received on loading the Shared View.|
|The filters were not working for saved views.||364490|
|JES||JES crashed and had unexpected issues.||339900|
|The Start Workflow job did not run as scheduled after being enabled.||92492|
|JES logs had errors on several JES hosts.||335870|
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.
|Site applications||Service applications|
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.