12 APRIL 2022
This update includes some enhancements, and a resolved issue.
Enhancements
- Elasticsearch performance improvements: In our continuous efforts to improve performance, we have made the following updates to the Elasticsearch functionality.
- Indexing job HTML transformers: We have introduced HTML transformers that transform the indexing data to reduce the Elasticsearch database size and enhance the performance.
You need to define these transformers in the JSON while configuring the Elasticsearch connection.
For more details, see this article.NOTE
Using HTML transformers is optional, you may choose to continue using the Elasticsearch without HTML transformers. - Disable index changes in closed tables: We have disabled the index changes in closed tables to reduce the load and enhance the Elasticsearch performance. However, you can enable index changes by setting the value of
trackClosedTableChangesandhasClosedTableto true.
- Indexing job HTML transformers: We have introduced HTML transformers that transform the indexing data to reduce the Elasticsearch database size and enhance the performance.
- Azure Active Directory (Azure AD) authentication library update: With end of support for Azure AD Graph API soon, we have updated our applications to use the Microsoft Graph API as recommended by Microsoft.
For details, see this article. - Support OAuth authentication for sending emails: We now support sending emails using Microsoft Graph for Exchange Online. This allows an option to send emails more securely based on OAuth authentication. Sending emails using SMTP with basic authentication remains the same.
For more details, see this article. - Support HTTP Consumer service with OAuth 2.0 On-Behalf-Of flow: HTTP Consumers now support Microsoft identity platform and OAuth 2.0 On-Behalf-Of flow. This allows integration to external services using the current authenticated user.
For more details, see this article. - We have indexed some of the Cora SeQuence database tables and have updated some HotOperations procedures to enhance overall performance.
- You can now configure application variables to determine the number of items on which Team Leaders and Operations Managers can perform multiple actions.
| Role | Application variable | Value |
|---|---|---|
| Team Leader | Portal.HotOperations.TeamLeader.MaxSelectionSize |
|
| Operations Manager | Portal.HotOperations.OpsManager.MaxSelectionSize |
|
NOTE
If a Team Leader or Operations Manager selects more items than the maximum value configured or the maximum value allowed by the system (100), a message is displayed, and the action is cancelled.
For more information about application variables, see this article.
Breaking change
After the upgrade to V9.8.3, you need to update the integration with Azure AD according to the Microsoft Graph properties.
Resolved issue
| Component | Issue | Ticket # |
|---|---|---|
| ADSS | An error occurred on starting the ADSS service. | 552613 |
Deployment
Download the release package from the Cora SeQuence repository.
NOTE
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.
IMPORTANT
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.
