SR-B41806 · Issue 304276
Fixed Run Robotic Automation handling for input with quotes
Resolved in Pega Version 7.3.1
Run robotic automation was hanging when any property contained quotes. This has been fixed by adding the "escapeIntoJSONString" function encoding to pzGetRelevantRecordsAsJSON .
SR-B46334 · Issue 305715
PAL 'Add Reading with Clipboard Size' button repaired
Resolved in Pega Version 7.3.1
Selecting the 'Add Reading with Clipboard Size' button in PAL caused a new entry to be created which contained all zeros instead of the actual readings. During adoption of the ReadOnly ClipboardPage, a setValueOverride call passes an OverrideReadOnly parameter as 'true' to write reference property-related information. However the same flag was not being propagated to clearValue which is called from setValueOverride; this has been fixed.
SR-B49980 · Issue 309543
Rule-System-Generated-Access and Rule-Generated activities documented as deprecated
Resolved in Pega Version 7.3.1
The description of Rule-System-Generated-Access and Rule-Generated activities in the help files has been updated to indicate these classes are deprecated as of Pega7.
SR-B42100 · Issue 305166
CommitBatch failure message logic fixed
Resolved in Pega Version 7.3.1
The failure message of commitBatch was always showing the first entry as faulty even though the failure occurred because of entries added later into the batch. This was an issue with the error message being overridden for every entry, and has been corrected by updating the API getUpdateCounts() to return the list of failed indexes/ the starting index at which the batch failed, based on the database platform.
SR-B42100 · Issue 311280
CommitBatch failure message logic fixed
Resolved in Pega Version 7.3.1
The failure message of commitBatch was always showing the first entry as faulty even though the failure occurred because of entries added later into the batch. This was an issue with the error message being overridden for every entry, and has been corrected by updating the API getUpdateCounts() to return the list of failed indexes/ the starting index at which the batch failed, based on the database platform.
SR-B48201 · Issue 306294
pxObjClass Transform fixed
Resolved in Pega Version 7.3.1
The only way to modify pxObjClass via a Transform is through a Set command, but the command was failing with the error "Step Status Fail: The page or property testPage.pxObjClass is unmodifiable". This was caused by an exception that occurred when setting pxObjClass on a page inside an Autopopulate property via data transform but the data page flush did not correctly reset then property values on the AP. This missed use case has been resolved by ensuring that when the DP is flushed, the old property values should be cleared on next access of the AP.
SR-B52049 · Issue 312694
pxObjClass Transform fixed
Resolved in Pega Version 7.3.1
The only way to modify pxObjClass via a Transform is through a Set command, but the command was failing with the error "Step Status Fail: The page or property testPage.pxObjClass is unmodifiable". This was caused by an exception that occurred when setting pxObjClass on a page inside an Autopopulate property via data transform but the data page flush did not correctly reset then property values on the AP. This missed use case has been resolved by ensuring that when the DP is flushed, the old property values should be cleared on next access of the AP.
SR-B68812 · Issue 317695
Activities updated to use class name to access out-of-the-box templates
Resolved in Pega Version 7.3.1
The out-of-the-box templates were not visible in the implementation layer due to the shipped templates having been created in a horizontal layer tied to a horizontal class. To correct this, the pzGetAllMappedFieldsFromTemplate and pzSetInitialSourceInfo activities have been updated to allow for loading mapping data by getting a selected template class name before calling the load template data page.
SR-B68812 · Issue 310862
Activities updated to use class name to access out-of-the-box templates
Resolved in Pega Version 7.3.1
The out-of-the-box templates were not visible in the implementation layer due to the shipped templates having been created in a horizontal layer tied to a horizontal class. To correct this, the pzGetAllMappedFieldsFromTemplate and pzSetInitialSourceInfo activities have been updated to allow for loading mapping data by getting a selected template class name before calling the load template data page.
SR-B69935 · Issue 317991
Pega fetch assignments API updated to call py functions for Robot Manager use
Resolved in Pega Version 7.3.1
The Pega API assignment activity pzGetAssignmentDetailsInternal in ruleset Pega-API:07-10-31 makes a call on line 16 to pzNotifyRobotWorkBasketContainer. This is a platform defect that should have been replaced with pyNotifyRobotWorkBasketContainer. pyNotifyRobotWorkBasketContainer is an extension point activity that is blank in the core platform, but overridden when the Robot Manager app layer is added to the stack. The correct py calls are now present.