SR-B15690 · Issue 313605
Access Group hash reworked to avoid linefeeds
Resolved in Pega Version 7.3.1
It was discovered that Access Group names with more than 56 characters result in a hash value whose length is more than 76 characters; this introduces line feeds in the final AG hash that were causing IIS 7.5 to reject the URLs and impede use of Pega in a mobile client. To resolve this, changes have been made to ContextMap/Base64 to not include line feed character while generating Access Group Hash.
SR-B43747 · Issue 305698
Localization rulesets visible to redirected thread
Resolved in Pega Version 7.3.1
Modal Dialogs content coupled to localized field values for a target language were not updated until the internal content was refreshed. This was traced to localization rulesets not being set for the thread when the flow was executed through the redirectAndRun activity. Localization rules were visible to the main thread but not to the redirected thread. This happened only when a section was displayed in a modal window and localization FV was defined for the properties in the section, and has been fixed.
SR-B56835 · Issue 312521
Checked in SLA values updated by delegated use
Resolved in Pega Version 7.3.1
Once checked in to the application, the SLA value was not being properly updated when edited by an delegated operator and instead retained the value given by the Case Manager. This was a clipboard handling issue, and has been fixed.
SR-B42971 · Issue 304249
Enhancement added for sorting configured nested grid embedded as expandable row
Resolved in Pega Version 7.3.1
Performing a sort on a configured nested grid embedded as a expandable row opened a new window with the error message indicating the VirtualClipboardPropertyImpl was incompatible with the ClipboardPropertyBase. To resolve this, an enhancement has been added in order to support the sorting of an embedded virtual pagelist inside another VirtualPagelist.
SR-B48709 · Issue 313194
Rule resolution fixed for for Rule-Parse-Transform
Resolved in Pega Version 7.3.1
Rule resolution was not working as expected for Rule-Parse-Transform due to the way classes were defined during the rule assembly. This has been fixed by changing the class DefaultVirtualTableConfig to ignore vtable assembly for Rule-Parse-Infer and use application based assembly (ABA).
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.