17 JUNE 2020
This update includes a new feature and resolved issues.
- Graph API support for Email Listener.
Microsoft has announced to end support for basic authentication for several Office 365 email service protocols. For more information, see this page.
This will impact all Cora SeQuence and Cora OpsManager customers that have Email Listener activities configured with Office 365 mail service with any protocol other than Graph API and with basic authentication. For example, an Email Listener activity that uses Office 365 mail service with the EWS protocol and basic authentication will fail to connect.
The new Graph API protocol for email listener activity uses OAuth 2.0 authentication, and provides more secure access to data. For more details, see this article.
|OData||OData, the REST-based protocol for querying and updating data, did not work with delegation.||85325|
|Flowtime grid||Highlighted tab in grid displayed irrelevant data.||87253|
|File writer||Opening an Open XML file gave an error.||86876|
|Form grid||Calculated column broke the combo box functionality.||77782|
|Administration||Chrome V83 did not support some of the Cora SeQuence Administration functionalities.||88034|
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.
You need credentials to access the Cora SeQuence repositories. Contact Support to obtain credentials.
Before upgrade, make sure to update the PowerShell modules to the latest version.
Click here to view a sample PowerShell script. Consider this sample for reference only, and do not copy paste from here.
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.