Fourth Quarter of 2022

Release Date: December 13, 2022

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.

DescriptionTracking ID
In order to facilitate the upgrade process, when your Essentials system is upgraded, the existing execution history records are removed. To ensure optimum performance of your Essentials system, if the execution history retention automated job is not configured, it will be configured to retain execution history records for a month, and to execute daily. You can modify the job configuration on the Policy Admin page.US561657
A new catalog query, Public\Meridium\Modules\Policy Manager\Queries\Family Policies with Upgrade Issues, is provided to identify any family policies that could not be successfully upgraded. You should review the upgrade logs for any family policy that could not be successfully upgraded and modify the policy model as appropriate.
Important: Failure to modify family policies that were not successfully upgraded may result in unexpected system behaviour when inserting, updating, or deleting records in the relevant families. For more information, refer to Upgrade or Update Policy Designer. Please contact APM Support Team: https://digitalsupport.ge.com/ in case of any difficulty with family policy modifications.
US533620
You can now review warnings and errors that occur during the post-upgrade processing of family policy records in the Family Policy UI. To facilitate this enhancement, you can now select the Upgrade Logs tab in the module navigation menu and view or delete the log information for a family policy that is upgraded from an earlier version.US525819
You must now specify the family ID or family key(s) for relationships that you want to delete in a family policy. To facilitate this enhancement, the Predecessor Family ID, Predecessor Family Key(s), Successor Family ID, and the Successor Family Key(s) sections are added in the Delete Relationship node properties window of Family Policies.
Note: When your Essentials system is upgraded, family policies containing the Delete Relationship node will be upgraded only where the family of the entities to be created can be determined automatically. For more information, refer to Upgrade or Update Policy Designer.
US520092
To enhance usability, additional output system fields have been added to the Current Relationship node. Now, the node contains the following output system fields:
  • Created By User Key
  • Created Date
  • Entity Key
  • Entity ID
  • Family Key
  • Last Updated By User Key
  • Last Updated Date
  • Predecessor Family Key
  • Predecessor Key
  • Relationship Definition Key
  • Site Key
  • Successor Family Key
  • Successor Key
US518099
To improve usability, the following output system fields have been added to the Current Entity node:
  • Created By User Key
  • Created Date
  • Last Updated By User Key
  • Last Updated Date
US518098
You can now use a new Collection output from the Sub Policy node. To facilitate this enhancement, now, when you execute a family policy containing a sub policy node that is not operating on a collection, the values returned from the sub policy are accessible in a collection output containing two columns, (Name and Value) in addition to the single-value outputs. US511936
To enhance functionality, the Family Key is now included in the outputs of the following entity and relationship family nodes:
  • Add Value to Health Indicator
  • Current Entity
  • Current User
US481771
You can now configure the catalog path input of the Query node to accept the output from a predecessor node. To facilitate this enhancement, select the switch to field input button () under query path to choose an input from another node.
Note: When the query path is sourced from a predecessor node, the results collection output from the query node can be used only when you do not need to select a specific column in the collection.
US414721
To improve performance, node-level execution history details are now maintained in a separate dedicated data store. As a result of this upgrade, you will no longer be able to retrieve the contents of the MI_POLICY_EXEC_LOG.PLOG_DATA_TX field in the policy execution history table using a query.US399196
The Email node has been enhanced. You can now:
  • Define a collection (for example, the output from a Query node) to be displayed as a table in the email body.
  • Configure the email to be sent as plain text.
  • Define the subject line of the email.
  • Suppress the automatic email text that shows details of the policy logic.
  • US293858
  • US293856
Table 2. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, if you configured a family policy for a relationship family that included a Cancel Transaction node, when the Cancel Transaction node was executed, the alert message was not displayed. This issue has been resolved.DE188184
Previously, when you attempted to export family policies for custom relationship families from the Configuration Manager, an error occurred, and the export was not successful. This issue has been resolved.DE183424
Previously, if you executed a family policy with a Query Time Series node configured with a number in the Max Readings input, and the time series query returned that number of readings, the node execution results included a Possible Data Truncation warning message. This issue has been resolved. Now, a Possible Data Truncation warning message is displayed only if no value is specified for the Max Readings input and the time series query returns 10000 readings.DE179766
Previously when you attempted to copy and paste a Case node, its predecessor node and the link between the nodes, the pasted Case node did not retain the configuration of the copied Case node. This issue has been resolved.DE158704
Table 3. Known Issues

The following known issues and limitations exist.

DescriptionTracking ID
If a Query node references a query with column aliases containing quotation marks, the policy model may not be upgraded correctly when your Essentials system is upgraded. You will need to modify and reactivate the policy.DE195101
When you create a Policy Recommendation using the Create Entity node, the recommendation is not linked to the equipment record automatically, even though the Equipment ID is provided.DE194635
When your Essentials system is upgraded, if the policy model contains multiple Sub Policy nodes that reference the same sub policy, the policy is not upgraded correctly and a warning appears in the Upgrade Log indicating that sub policy recursion was encountered. You will need to modify and reactivate the policy.DE194299
When your Essentials system is upgraded, if an entity key in a Delete Entity, Create Relationship, or Delete Relationship node is defined in a Point Value node in an instance, you may need to modify and reactivate the policy instance and the policy. This is as-designed; however, the product documentation does not cover this upgrade step.DE194296
Table 4. Obsolete Features

The following features are no longer available.

DescriptionTracking ID
The Content GUID output has been removed from all nodes in family policies.
Note: When your Essentials system is upgraded, any existing family policies that use the Content GUID output from any nodes will be upgraded to use the Entity Key output, and the behavior of the family policy may change. For more information, refer to Upgrade or Update Policy Designer.
  • US460179
  • US424533