Fourth Quarter of 2023

Release Date: December 13, 2023

This topic provides a list of product changes released for this module on this date.

Table 1. Enhancements and New Features
The following enhancements and new features have been added.
Description	Tracking ID
To improve usability, the following enhancements have been made in the Reference Document generated through Email Contact node with attachment: The ID is generated in the following format: Email Attachment for Policy -<Name> The description field is updated in the following format: Policy: <policy name>; Instance: <instance ID>; Email sent to:<email address list>; Execution time (UTC):<timestamp of the email node execution in ISO format> To keep a file name unique and to avoid renaming an attachment while saving it to your local system, the attachment name is updated in the following format: ExecutionOutput_<policy name>_<instance id>_<timestamp MMDDYYYY-hhmmss>.csv	US593664
To improve usability, the policy execution history background clean up job has been improved. To facilitate this enhancement, additional options have been added to control the job start time, end time, and selection of timezone.	US541496

Table 2. Resolved Issues
The following issues, which existed in one or more previous versions, have been resolved.
Description	Tracking ID
Previously, instances upgraded from V4 Policy with Time Series node input failed to send email node when entity key was null. This issue has been fixed	DE209593
Previously, in an After Insert relationship family policy, a Query node did not return the predecessor and successor entities linked by the inserted relationship. This issue has been resolved.	DE208954
Previously, is Null node was converting input string value to the unreadable date format. This issue has been resolved.	DE207778
Previously, the Export Instances and Policy Instance Data Loader did not recognize the Measurement step node and all values were considered as Point value nodes. This issue has been resolved.	DE207705
Previously, when JSON Parser node configured with more than one Name and JSON path value then in return value node will have only one value available. This issue has been resolved.	DE207345
Previously, State Transition node execution log messages and execution history was showing Family id instead of Entity Key. This issue has been resolved.	DE207344
Previously, with State Transition Mode option, when a Record was already in the target state, Policy execution was showing success for state transition. This issue has been resolved.	DE206836

Release Date: October 6, 2023

This topic provides a list of product changes released for this module on this date.

Table 3. Enhancements and New Features
The following enhancements and new features have been added.
Description	Tracking ID
To enhance usability, when you view policy execution results in the design canvas, the node ID is now displayed in the node execution details window.	US595444
To ensure that the content protection and revert to baseline features work as expected, you can no longer modify the Family ID or the Trigger field in a baseline Family Policy record.	US581682
To enhance usability, the policy model can now be started from a Query node, thus the Query node is now consistent with the other Input nodes.	US495730
To enhance usability, the Convert Type node can now be configured to convert a column of values in a collection (for example, a query result), to a different data type.	US476079
To enhance usability, a new baseline policy, String Replace Sub-policy and an associated R Script have been delivered. You can use this policy to facilitate replacing a string with a different string in a single text value or a collection of text values.	US293831
To enhance the configurability of Essentials, for families where State Management is enabled, you can now define Family Policies to be triggered before and after the state of a record is saved. To facilitate this enhancement, the Before State Commit and After State Commit triggers have been added to the list of available family policy triggers.	US280338
To enhance usability, a new node named Query Entity has been introduced, which enables you to retrieve all fields of a record by providing the entity key and family ID of the record. This removes the requirement to create a catalog query to retrieve a record that is not the Current Entity.	US255674
To provide additional configuration capability, you can now configure a family policy to be executed when a new relationship is instantiated.	US236052

Table 4. Resolved Issues
The following issues, which existed in one or more previous versions, have been resolved.
Description	Tracking ID
Previously, for a Family Policy associated with the After Insert trigger or Update trigger, when you configured a create or edit recommendation linked to an EAM system notification, an error occurred. This issue has been resolved.	DE204690