Second Quarter of 2023
Release Date: June 30, 2023
This topic provides a list of product changes released for this module on this date.
| Description | Tracking ID |
|---|---|
| To ensure that content protection and revert to baseline features operate as expected, you can no longer modify the Name field in a baseline Policy record. Note: If you have already modified the name of a baseline Policy, you can no longer edit the name. However, if you revert the policy to baseline, the name will be reverted to the original name. | US580861 |
| To improve usability, the Rounds Pro module users can now access records from Measurement Step family and view information about related readings. The new Input Node is added that replicates the Measurement step node functionality. | US579505 |
| Description | Tracking ID |
|---|---|
| Previously, in the Design workspace of a policy, when you selected Execute Now, sometimes, the policy was not executed. This issue has been resolved. | US588802 |
| Previously, if the ActiveMQ server failed over or was restarted, scheduled policy executions were not executed as expected. This issue has been resolved. | DE201020 |
| Previously, when you executed a policy, the message "An unexpected error occurred when upgrading policy with key <...>" appeared in the execution log. This issue has been resolved. | DE200396 |
| Previously, if you selected the Summary Only option for the Execution History Log Setting for a policy, and then selected an Execution History to display the details in the design canvas, an incorrect error message appeared. This issue has been resolved. Now, in this scenario, the following warning message appears: Summary only is available for this execution history entry. | DE199650 |
| Description | Tracking ID |
|---|---|
| If you schedule a policy with a large number of instances, some of the policy instances are executed more than once at the same scheduled execution time. | US595325 |