23 JUNE 2022
This update includes some resolved issues.
|Administration||When you upgraded from V8.x to V9.x, some activities were not mapped in the web.config files, and thus failed.||573620|
|There was a wrong parameter for the |
type="PNMsoft.Sequence.MessageBus.SqlServiceBroker.SqlServiceBrokerCleanupService, PNMsoft.Sequence.MessageBus.SqlServiceBroker, Version=220.127.116.11, Culture=neutral, PublicKeyToken=0a1a1b90c1c5dca1" enabled="false" />Correct parameter
type="PNMsoft.Sequence.MessageBus.SqlServiceBroker.SqlServiceBrokerCleanupService, PNMsoft.Sequence.MessageBus.SqlServiceBroker, Version=18.104.22.168, Culture=neutral, PublicKeyToken=0a1a1b90c1c5dca1" cleanup="true" />
|If a solution included only one subgroup, the solution's task list was empty.||583854|
|When you added a workflow to a category or sub category, the workflow wasn't added successfully in a single attempt.||-|
|When you created custom actions in Cora SeQuence API, some states were missing.||-|
|Conversation Items||After upgrade, the hardcoded translation values in Custom conversation types changed.||-|
|HotOperations||Some workflows had duplicate activities.|
An improved locking logic that reduces the risk of duplicate activities was added to the workflow execution logic.
After you upgrade, add the following instance lock duration property to the Flowtime web.config file:
<workflowExecution … instanceLockDuration="90000" />
|There were issues with non-active ssb queues in ssb.DialogsMap.||607826|
|JES||JES crashed when the “To” field was empty (Email Sender Job).||583065|
|JES jobs crashed intermittently, and you had to restart the JES.||588015, 590796, 618258, 626615, 626947|
|Security||HTTP headers didn't include X-XSS-Protection value as 0, as recommended for OWASP.||-|
The enhanced execution logic may expose parallel execution attempts, and affect the existing solutions' behavior.
If your solution does not behave as expected, check for the following error in the event log:
“Failed to acquire exclusive lock”
This error occurs when there are parallel execution requests for the same instance. Only the locking request executes the instance while other requests get blocked, which reduces the risk of ending up with duplicate activities.
To mitigate the error, it’s recommended to look for the root cause of the parallel execution, and resolve it.
For example, a custom code in a Form that triggers the Submit action prematurely can be a root cause of the parallel execution.
Alternatively, you may disable the locking by setting its value to zero.
<workflowExecution … instanceLockDuration="0" />
Download the release package from the Cora SeQuence repository.
Contact Support to obtain credentials to access the Cora SeQuence repositories.
There are seven 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.
When you upgrade from a version earlier than V9.8.4, you need to upgrade to V9.8.3 first.
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.