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 |
|---|---|
| You can now configure the Email Contact node to send a plain text email. | 519204 |
| You can now enter values for the original value and the current entity value in the text box added, for validation of the Field Value Changing Condition node, when added in a Before Update family policy. | 367694 |
| To enhance usability and simplify entity value comparison, a new input node named Previous Entity has been added in the Before Update family policy. | 367691 |
| You can now configure the behavior of a field to display the Asset Finder. | 148940 |
| 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 |
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 |
| To enhance usability, node icons for Query Entity, Python node, and State Transition have been refreshed. | US596295 |
| Description | Tracking ID |
|---|---|
| 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 indicating that the specified string was not in the form required for an e-mail 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, 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 to the family policy. These issues have been resolved. | DE207252 |