Fourth Quarter of 2022
Release Date: December 13, 2022
This topic provides a list of product changes released for this module on this date.
| Description | Tracking ID |
|---|---|
| To facilitate the upgrade process, when your Essentials system is upgraded, the existing Policy Execution History records are removed. To ensure optimum performance of Essentials, 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 |
| In order to simplify the module deployment, the existing query, Public\Meridium\Modules\Policy Manager\Queries\Time In Queue (SQL), has been modified to work on all database types and is renamed Public\Meridium\Modules\Policy Manager\Queries\Time In Queue. This query is used in the Time In Queue graph on the Policy Designer Overview and the Recent Policy Executions dashboard. As a result, the following items which are no longer required have been removed from the catalog:
Note: If you have previously modified any of the above mentioned catalog items, you have to copy the updated item from the baseline folders to the public folders and then, re-apply your changes. | US557648 |
The Policy Designer data model has been enhanced and the following queries have been modified:
If you previously modified any of these queries, you must copy the relevant query from the baseline folder to the public folder and reapply your modifications. | US551776 |
| Policy Instance records are now linked to Policy records by the new Policy Has Policy Instance relationship family. To facilitate this change, the Policy Key field has been added in the Policy Instance family and the Policy GUID field has been removed. Note: Do not configure Family Policies to be triggered when the Policy Has Policy Instance records are deleted. | US551771 |
| The Policies list on the Policy Designer Overview is updated to show any policies that have been inactivated during the upgrade. Note: Review the upgrade logs for any policy that has been inactivated and modify the policy as appropriate before re-activating it. For more information, refer to Upgrade or Update Policy Designer. Contact APM Support Team: https://digitalsupport.ge.com/ in case of any difficulty with policy modifications. | US542244 |
| You can now view an updated Average and Max Wait Times graph in the Policy Overview page. To minimize configuration effort, the graph now displays queue times in seconds for all database types. | US528386 |
| You can now review warnings and errors that occur during the post-upgrade processing of policy records in Policy Designer. 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 policy that is upgraded from an earlier version. | US519063 |
| You can now use a new Collection output from the Sub Policy node. To facilitate this enhancement, now, when you execute a 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 output of the following nodes:
| 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 |
| You can now set the time or number of occurrences by when a scheduled execution should end in a policy. To facilitate this enhancement, the End Repeat option is added to the Scheduled Execution section of the Details workspace in the Policy Designer page. | US402265 |
| 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 |
| Description | Tracking ID |
|---|---|
| Previously, when you attempted to delete a policy instance with large number of execution history records, an error occurred. This issue has been resolved. | US459366 |
| Previously, if you used the Create Alert node to create an alert containing Scan Group Data, an error occurred in the policy execution history, even though the alert was created successfully. This issue has been resolved. | DE182923 |
| Previously, if you executed a policy with a Predix Time Series or 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 |
| Previously, when you executed a policy with two or more levels of sub-policies, and the second or lower level of sub-policies had an error, the execution status of the policy did not indicate that an error had occurred. This issue has been resolved. | DE143955 |
| Description | Tracking 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 |
| If the policy execution service experiences a session time out, the policy execution is not retried. This may result in skipped policy executions. | DE194998 |
| 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 |
| Description | Tracking ID |
|---|---|
The following catalog queries, which were used to determine the status of the scheduled policy trigger jobs, are no longer used and have been removed from the catalog:
The Public\Meridium\Modules\Policy Manager\Recent Policy Execution Results dashboard has been updated to remove widgets that reference the queries listed above. The Public\Meridium\Modules\Policy Manager\Recent Policy Execution Results (Oracle) dashboard has been removed. Note: If you have previously modified these queries or the dashboards, an error will occur when you access the content. You must copy the updated query,Baseline\Meridium\Modules\Policy Manager\Recent Policy Execution Results dashboard to the public folder and then reapply your modification. | US557590 |
| The Content GUID output has been removed from all nodes in Policy Designer. Note: When your Essentials system is upgraded, any existing policies that use the Content GUID output from any nodes will be upgraded to use the Entity Key output, and the behavior of the policy may change. For more information, refer to Upgrade or Update Policy Designer. |
|
Release Date: November 18, 2022
This topic provides a list of product changes released for this module on this date.
| Description | Tracking ID |
|---|---|
| Previously, when you scheduled multiple policies to execute at the same time, some policies were not executed, even though the scheduled jobs were completed successfully. This issue has been resolved. | DE190019 |