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.
SR-B4034 · Issue 306173
Fixed data mismatch from parallel schema migration
Resolved in Pega Version 7.3.1
When a queue method in a loop inside an activity was used to create separate work objects and in parallel migrate work object data from one DB schema to another, running that queue method more than once caused the Source table columns and destination columns to have mis-matched datetime property values after migration. This was an issue where the same DateFormat object was being used by two batch requestors. To resolve this, whenever the requestor object is destroyed, the date format object used for database operations will be made null.
SR-B15685 · Issue 317888
Mobile autocomplete dropdown selections fixed
Resolved in Pega Version 7.3.1
When the 'Enable lightweight autocomplete on phone' and 'Allow scrolling for more results' were enabled, the incorrect data was selected (e.g., using the autocomplete to select "John" from the list instead displayed "Mark"). This was due to a logic issue around the scroll feature for mobile list based autocomplete, and has been fixed.
SR-B71308 · Issue 319409
Paragraphs load as expected in offline app
Resolved in Pega Version 7.3.1
After upgrade, paragraph rules were not displaying as expected in the offline mobile app. Instead, the message 'Loading...' appeared in their place. This was traced to the records being returned correctly but not being properly packaged for display due to an error in the report definition. To correct this, a step has been added to the pzPackageLocalization activity to clear parameters which may mislead report execution.
SR-B71308 · Issue 320806
Paragraphs load as expected in offline app
Resolved in Pega Version 7.3.1
After upgrade, paragraph rules were not displaying as expected in the offline mobile app. Instead, the message 'Loading...' appeared in their place. This was traced to the records being returned correctly but not being properly packaged for display due to an error in the report definition. To correct this, a step has been added to the pzPackageLocalization activity to clear parameters which may mislead report execution.