SR-B51792 · Issue 308109
System Pulse enhanced to support Data-Admin-Requestor instances
Resolved in Pega Version 7.3.1
Changes in the Data-Admin-Requestor instances were not consistently getting propagated to other nodes in a cluster due to System Pulse not being supported for the Data-Admin-Requestor instances. An enhancement has been added to support this use.
SR-B77464 · Issue 327643
Clean up corrected for MultiChannel indexes
Resolved in Pega Version 7.3.1
Due to a capitalization change from 'Pega-Multichannel' to 'Pega-MultiChannel', indexes were not being cleaned up properly. This has been corrected.
SR-B77464 · Issue 328021
Clean up corrected for MultiChannel indexes
Resolved in Pega Version 7.3.1
Due to a capitalization change from 'Pega-Multichannel' to 'Pega-MultiChannel', indexes were not being cleaned up properly. This has been corrected.
SR-B49994 · Issue 312887
Pulse agent updated to handle Linux mixed case names
Resolved in Pega Version 7.3.1
Files were not getting deleted by the pulse agent in Linux-based multi-node environments if the Image Content had a path and name defined with a mix of upper case/lower case and the image was updated on a different node. This occurred because Linux-based environment file handles are case sensitive and the pulse message was not sanitized to be in lower case. To resolve this, the system will honor the lowerCase matching for filePath processing on pulse messages for Data-Content-Image files.
SR-B49994 · Issue 314006
Pulse agent updated to handle Linux mixed case names
Resolved in Pega Version 7.3.1
Files were not getting deleted by the pulse agent in Linux-based multi-node environments if the Image Content had a path and name defined with a mix of upper case/lower case and the image was updated on a different node. This occurred because Linux-based environment file handles are case sensitive and the pulse message was not sanitized to be in lower case. To resolve this, the system will honor the lowerCase matching for filePath processing on pulse messages for Data-Content-Image files.
SR-B48517 · Issue 320295
Handling added for Multiple pega:reference tags in paragraph
Resolved in Pega Version 7.3.1
Given a paragraph rule that includes more than one tag, offline testing on a mobile app displayed only the last reference. This was caused by a lack of handling for multiple pega:ref tags in same line, and has been fixed by tweaking regex to do a non-greedy match.
SR-B43676 · Issue 306298
Enhanced ArchivePurge logging
Resolved in Pega Version 7.3.1
In order to help manage and report on ArchivePurge processing, an enhancement has been made to ArchivePurge logging to include values of two properties: pxCoveredCountOpen (integer) and pxCoverInsKeys (StringList). These will appear in logging triggered within the ArchivePurge.evaluateItem RUF.
SR-B43676 · Issue 306302
Enhanced ArchivePurge logging
Resolved in Pega Version 7.3.1
In order to help manage and report on ArchivePurge processing, an enhancement has been made to ArchivePurge logging to include values of two properties: pxCoveredCountOpen (integer) and pxCoverInsKeys (StringList). These will appear in logging triggered within the ArchivePurge.evaluateItem RUF.
SR-B43414 · Issue 306721
PegaSurvey radio buttons updated for better null handling
Resolved in Pega Version 7.3.1
In the Answer section for a (PegaSurvey) Question, a section in a repeating layout sourced by a pagelist that contained radio buttons and a formatted text field was not working as expected if items were skipped. If a user answered one of the questions other than the first (page), and submitted without answering the rest, it generated a JS error and an endless busy indicator on mobile devices. In addition, the pages which were not "answered" were null in the client cache. This was caused by the radio buttons which were not checked being submitted as null in the page list array, and their condition has been changed to populate as empty to better handle this scenario.
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.