SR-C80076 · Issue 419094
Added check before deleting pxObjClass to avoid agent runtime exceptions
Resolved in Pega Version 8.1.3
When the rule was not assembled, agents were failing with exceptions. During label control assembly execution, standard attributes for label assembly including pxObjClass are removed from the cell page. There is a catch for the exception during cell trimming for browser requests, but the customer agent was failing because UnmodifiablePropertyException is a runtime exception that sets the step status to fail. This has been fixed by adding a check when attempting to delete a property from Clipboard page: if the property is pxObjClass, it will not be deleted.
SR-C80084 · Issue 417239
Target connectivity preference updated in Revision Manager to address deployment error
Resolved in Pega Version 8.1.3
Using the deployment page to deploy a revision or migrate it to a target environment was failing. This has been resolved by correcting the target connectivity preference in the connector rules.
SR-C80215 · Issue 421850
Migrated Data Flows open correctly from the data flow landing page
Resolved in Pega Version 8.1.3
After upgrade, Data Flows made in an earlier version could not be opened from the data flow landing page. Instead, a generic error screen was displayed and an NPE on activity pxMigrate was logged. This was caused by a missing null pointer check, and has been corrected.
SR-C80958 · Issue 419200
Added check for appname to avoid HarnessFail execution error on Mashup reload
Resolved in Pega Version 8.1.3
A HarnessFail execution error was occurring on Mashup reload. This was caused by the appname being appended twice during the reload, and has been resolved by adding a check to the _finalizeNavURL method in the PegaCompositeGadgetMgr.js file to remove appName if it is present in the URL to prevent duplication.
SR-C81111 · Issue 417909
Performance improvements made for IH summary use
Resolved in Pega Version 8.1.3
Enabling IH summaries in an adaptive model or using them in a strategy was impacting performance by as much as 300 milliseconds. Improvements have now been made to streamline Cassandra node health checks, to eliminate unnecessary duplicate calls to the DB, and to stop the DSS from being read on each single case dataflow execution.
SR-C81262 · Issue 418057
Failed delete instances now correctly logged
Resolved in Pega Version 8.1.3
After configuring rule-access-when on delete instances for a data class, the failed instances were not shown in the error log file. This has been resolved by correcting the path of the error CSV file in the pzDeleteRecords activity.
SR-C81829 · Issue 419228
pxCoveredCountOpen value decrease corrected
Resolved in Pega Version 8.1.3
When a flow reached the resolved stage (Resolved-Withdrawn), pxCoveredCountOpen was reducing the count by 2 instead of 1, eventually causing the value to go negative and prevent any further work objects from being marked as Withdrawn. Investigation showed the "Update status" activity was being called twice due to the Temporary WorkPage used to delete assignments persisting and appearing as a duplicate pyWorkPage. This caused an issue when using findPage by pzInsKey. To correct this, the "pxDeleteAssignmentsForWork" activity for Step-15 has been modified to explicitly remove the temporary WorkPage after the assignment is deleted.
SR-C81857 · Issue 420240
Enhancement added to support dropdown with page list property
Resolved in Pega Version 8.1.3
To enable the use of a dropdown control with a property of type page list, an enhancement has been added to support a clipboard page for drop down and autocomplete.
SR-C81946 · Issue 418711
Maintenance function operator ID will not persist in the system
Resolved in Pega Version 8.1.3
After a hotfix maintenance activity, an audit revealed that an extra operator created for the purpose called CloudMaintenanceUser persisted in the system. The code has now been updated to bypass saving operator records marked with pzPersistOperator="false" on user initialization; the CloudMaintenanceUser will be created with this property set to false, and updating this operator will be skipped during unauthentication.
SR-C82244 · Issue 421174
Enhancement made to allow passing of URL in actionset via the DX API
Resolved in Pega Version 8.1.3
When using the action "Open URL in Window" and the option "Use Alternate Domain" to pass a URL that is in saved in a property, the name of the property was passed when using the DX API instead of the URL. To allow this use, an enhancement has been added to support storing a last submitted value and a reference so that an action set with a property reference can return a reference object with lastSavedValue and the reference name attached.