Second Quarter of 2024
Release Date: June 21, 2024
This topic provides a list of product changes released for this module on this date.
| Description | Tracking ID |
|---|---|
| Previously, when the output from an Email node was a CSV file, for a record with multi-line text, the text spilled to the next line in the exported CSV file instead of showing in a single line. This issue has been resolved. | 546036 |
| Previously, when you attempted to delete a Case node that was copied and pasted, the Policy Designer page became unresponsive. This issue has been resolved. | 172677 |
Release Date: April 5, 2024
This topic provides a list of product changes released for this module on this date.
| Description | Tracking ID |
|---|---|
| To enhance user experience, you can now export the summary of execution results of a Policy Instance in a Microsoft Excel spreadsheet. You can also filter summary of execution results and download the filtered result. | F74835 |
| When triggering an email using the Email Contact node, you can specify whether to include a message to state that all time values are shown in the UTC format. To facilitate this enhancement, a new check box named Include Time Zone message in email body has been added to the Email Contact node. | US616320 |
| During policy validation, in the To Address field in an Email Contact node, the syntax of the email address that you enter is now validated. If the syntax is incorrect, an error message appears. | US615877 |
| When configuring scheduled policy execution, if you observe daylight saving and you need not change scheduling time from the standard time to daylight saving, you can now use the new Disregard Daylight Saving Time check box. When you select the check box, the schedule will remain at the same scheduled time. | US619449 |
| To enhance usability, node icons for State Transition, Python, JSON Parser, and API nodes have been refreshed. | US596295 |
| To enhance the traceability of policy designs, you can now see when a policy model was last updated on the Policy Designer Overview page. To facilitate this enhancement, a new field named Last Policy Model Change Date has been added to the Policy family. This field is updated only if a substantive modification to the policy model is saved. The queries used by the Policies and Module Workflow Policies sections of the Policy Designer Overview page have been updated to display the new field. If you have previously modified these queries, in order to view the last policy model change date on the Policy Designer Overview page, you must copy the updated queries from the baseline folder and reapply your modifications. | US377128 |
| Description | Tracking ID |
|---|---|
| Previously, Policy instances were getting deactivated when uploaded from data loader for the Policies that have Point Value node. This issue has been resolved. | DE213015 |
|
Previously, when the Case Node input value was selected as text but not populated, you were still able to save the Policy. This issue has been resolved. | DE212205 |
| Previously, if an extra space was added before or after an Email ID, the Policy execution failed, and the Email Contact node displayed an error message, indicating that the specified string was not in the format required for an email address. This issue has been resolved. | DE211154 |
| Previously, the Email Contact node failed when Policy information was unable to fit in the Reference Document description field. This issue has been resolved. Now, Policy information is stored in the Long Description field of the Reference document. | DE210795 |
| Previously, when you executed an API node for a certain URL path of Essentials APIs, an error occurred. This issue has been resolved. | DE210448 |
| Previously, the schedule for background cleanup job was enhanced to provide additional options to control the job start time, end time, and selection of time zone. However, because of this change, the job start time was inconsistent. This issue has been resolved. | DE210437 |
Previously, if the entity key did not match with an available Policy, the Policy Trigger service displayed the NotExistException error and the job appeared in the Failed section of the Job Monitoring Dashboard. This issue has been resolved. | DE210056 |
| Previously, the Delete Relationship and Create Relationship node check did not happen if an existing relationship was already available for the given entity records. This issue has been resolved. | DE209749 |
| Previously, even if you removed the JSON Parser node from the Design workspace, a message appeared, stating that you must add at least one JSON path expression, and you could not save your changes until you deactivated the policy. These issues have been resolved. | DE207252 |