20 JUNE 2023
This update includes some resolved issues.
Resolved issues
| Component | Issue | Ticket # |
|---|---|---|
| Conversation view | Adding tags to an old conversation changed the conversation date details. | 1285478 |
| When you downloaded a conversation email with multiple recipients, only the first recipient was displayed in the downloaded email's To and Cc fields. | - | |
| Any text changes made to an email conversation were deleted when the email was forwarded. | - | |
| When you downloaded an email, the sent time changed to the download time. | - | |
| Any user could perform view actions (like mark the conversation as read or unread and create new email conversations) to cases already fetched by another user. | - | |
| Email listener | Email Sender connections configured with Graph API could send emails to only one recipient. | 1271657 |
| Dashboard | A blank dashboard was displayed to Team Leaders and Operations Managers in the Case Management (Hot Operations) dashboards list. | - |
| The portal application froze when you switched between dashboards. | - | |
| Database listener | An error occurred when you associated a database listener with a database table and key. | 1271266 |
| Grid view | The portal application froze when you selected to view a dashboard and the fetched and assigned cases in tile view simultaneously. | 1288701 1286863 |
| The "Cases assigned to me" and "Cases in queue" grids displayed incorrect data. | 1255480 | |
| Session timeout | The session timeout interval shortened with every session. | 1291706 |
| Workflow | Validation of the system.DateTime expression failed. | 1211716 |
| URL navigation | If you entered an invalid portal URL address, the URL error continued to display even after you entered a correct portal URL address. | 1315128 |
Deployment
Download the release package from the Cora Orchestration repository.
NOTE
Contact Support to obtain credentials to access the repository.
There are six pre-built application deployment packages available, depending on the type of application that you are deploying. You install each Cora Orchestration application separately.
| Site applications | Service applications |
|---|---|
|
|
Click here to see how to deploy pre-built applications.
For more details on installing and deploying applications, see this article.
Check if you need to upgrade your database for this version.
For more information on database upgrade and pre and post-upgrade procedures, see this article.
Before upgrade, make sure that you update the PowerShell modules to the relevant version.
For more information, see this article.
Click here to view a sample PowerShell script. Consider this sample for reference only, and do not copy paste from it.
IMPORTANT
Use Microsoft SQL Server Developer Edition for development purposes only.
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.
For details on Cora Orchestration platform support, see this article.
