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 now generated as "Email Attachment for Policy -<Name>" The description field is now updated as "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 the filename unique and to avoid renaming the file while saving attachment the file to your local system, the attachment file name is updated as "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 time zone.	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, when you selected the Revert to Baseline button, the cache for the family policies was not cleared. Instead, the cache was cleared when you manually made any changes to the policy and saved the policy. This issue has been resolved.	DE207963
Previously, is Null node converted the input string value to an unreadable date format. This issue has been resolved.	DE207778
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 the configurability of APM, a new node named API has been introduced. The new node allows advanced policy users to configure policies to execute calls to the application programming interfaces (APIs) in APM. Note: To use this node, you must first configure the API Node Credentials in the Policy Admin page.	F39654
To enhance the analytical capability of policies, the Python node has been introduced. This node allows you to configure a policy to execute a Python script that is stored in the Catalog. Note: You must complete the Python analytic deployment steps prior to using this node. For more information on deployment, refer to the Configure Python Analytic Template for Policies section under Policy Designer Deployment in the APM Deployment guide.	F38982
To support the introduction of the Python node in Policy Designer, the Analytics Configuration section has been added in Policy Admin.	US602282
You can now add, update and delete API Node Credential Records. To facilitate this enhancement, a new section, Manage API Node Credentials, has been added in the Policy Admin page.	US599062
To enhance usability, a new node named State Transition has been introduced. The new node allows you to modify the state of one or more records in a policy.	US598769
To enhance usability, you can now send an email notification to all the users in a security group. To facilitate this enhancement, a new baseline policy Concatenate Text Email Example with associated R Script and Query have been delivered to the baseline APM database.	US596437
The Predix Time Series node has been renamed to Time Series node.	US596038
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
A new calculation node, JSON Parser, allows you to define an output collection to be created from an input JSON object, using JSON Path query expressions. The JSON Parser node can be used to transform the output from an API node into a format that can be used in successor policy nodes.	US587684
To enhance usability, the policy model can now be started from a Query node. Hence, 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 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 specified in the Policy Instance.	US255674
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

Table 4. Resolved Issues
The following issues, which existed in one or more previous versions, have been resolved.
Description	Tracking ID
Previously, when you deleted a policy with a large number of instances, many of the Policy Instance References Cleanup scheduled tasks remained In Progress until you canceled them. In some cases, the policy execution was interrupted. This issue has been resolved.	DE206613
Previously, when you attempted to create or edit a recommendation linked to an EAM system notification using a policy, an error occurred. This issue has been resolved	DE204690
Previously, if you were assigned to the Policy Viewer security group, you were unable to view Policy Events. This issue has been resolved.	DE204293
Previously, if you scheduled a policy with a large number of instances, not all instances were executed every time. This issue has been resolved.	DE203646
Previously, when you closed the Policy Admin page, even if you did not make any changes to the settings, a message appeared, stating that your changes would be unsaved. This issue has been resolved.	DE197820
Previously, when you executed a Create Entity or Edit Entity node in policy, if the family rules were configured to create a relationship based on the values written to fields on the new or updated entity, for example, a related record ID or entity key, the relationship was not created. This issue has been resolved.	DE194635

Table 5. Known Issues
The following known issues and limitations exist.
Description	Tracking ID
When your APM database is upgraded to V5.x, the upgrade logs for certain policy models that contain Create Relationship nodes indicate that the node was upgraded successfully; however, the upgrade fails. Workaround: Correct the policy configuration. For instructions, refer to KBA 000069050.	DE206553