16 DECEMBER 2020
This update includes performance enhancements to the Attachments View component and some resolved issues.
- The Attachments View now has an improved preview performance for TXT and CSV files.
To enable or disable preview in the Attachments View, set the following parameter in the Administration and Flowtime web.config file:
- True (default)
- To add max preview size for Attachments View, set the following parameters in the Administration and Flowtime web.config file.
Also, the default max preview size has been updated for different types of files.
Parameter Supported files Default max preview size
PDF, JPEG, PNG, GIF, TXT, and CSV 4 MB
XLSX, DOCX, XLS, and RTF 1 MB
Earlier, the max preview size parameter was set in the Solution configuration.
|Email listener activities with Graph API protocol moved email to the processed folder without creating a new workflow instance.
|Same email sent to multiple email listeners created only single workflow instance.
|Web service input activity was not displayed in the input activity list.
|If you restarted one of the many running Graph API email listener jobs then all the running jobs stopped and got queued.
|Workflow Alias didn't get translated while changing the language in Flowtime.
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.