INC-183996 · Issue 669645
Step name given heading level for better accessibility
Resolved in Pega Version 8.8
When using the JAWS shortcut for navigating through headings, the Step name was not announced as expected. This was due to the Step name not containing the necessary code for a heading, and has been resolved.
SR-B38627 · Issue 298635
Calendar icon refresh updated for Internet Explorer browser
Resolved in Pega Version 7.3
Intermittent responsiveness issues were seen when trying to select/pick date from calendar icon. This issue was traced to the combination of having the "Contract ID" option enabled and using the Internet Explorer browser, leading to unexpected refresh of particular scripts used in the section. The script timing has been modified to resolve the issue.
SR-B38627 · Issue 298840
Calendar icon refresh updated for Internet Explorer browser
Resolved in Pega Version 7.3
Intermittent responsiveness issues were seen when trying to select/pick date from calendar icon. This issue was traced to the combination of having the "Contract ID" option enabled and using the Internet Explorer browser, leading to unexpected refresh of particular scripts used in the section. The script timing has been modified to resolve the issue.
INC-146610 · Issue 614422
MimeTypeHandler added for cloud downloads on mobile
Resolved in Pega Version 8.4.4
When using the Pega cloud storage repository (Application -> Integration -> Content Storage) with the Google Chrome browser on an android device, it was possible to upload attachments but re-downloading the attachments failed. Investigation showed that this was due to the content-type appearing as application/* so Google Chrome on mobile was not able to identify the file type. This was a missed use-case for returnFileForDownload(), and has been resolved by setting the system to use MimeTypeHandler for getting the content type.
INC-172124 · Issue 651293
Improved Operator ID selection in Mobile Logs Retrieval section
Resolved in Pega Version 8.7
Data-Admin-Operator-ID.pzOperatorsByApplication returns only the first 500 operators, which is insufficient for large-scale use. There was a workaround of turning off paging for this report definition and setting maximum records to a bigger value, but this caused potential performance issues when opening very large users list. To resolve this, an autocomplete control will now be used to select Operator ID in the Retrieve Device Logs section of Mobile Channel. When part of an operator ID is typed into this control, the first 100 best results are shown and may be selected.
INC-207218 · Issue 706367
Check added to prevent duplicate approval by single agent
Resolved in Pega Version 8.8
When using a cascading Approvals process supported both by a web access button or by responding via email, a single agent could use both methods and advance a case an additional step as if they were the next approval level. This was due to the system only checking the pzInsKey when processing the approval while the assignment key will be the same for the cascading approvals assignments. This has been resolved by introducing a datetime check to validate if the email approval assignment creation datetime and the one in the database have same value; if yes the approval process will proceed and if not it will exit.
INC-217821 · Issue 719168
Ensured data refresh for cascading dropdown controls
Resolved in Pega Version 8.8
When using two cascading dropdowns where the options within the second dropdown depended on the selection in the first dropdown, making both selections and then going back to change the selection in the first dropdown appeared to allow changing the selection in the second dependent dropdown, but autocomplete was still holding the previously selected value in memory even though the source property changed. This caused an unexpected behavior when the selections were submitted. Investigation showed that changing the value of the first dropdown triggered an API call to the Refresh assignment action that updated the value, but changing the first dropdown did not cause a refresh call to set the value back to blank in the second dropdown. This issue was seen when the dropdown values were hard-coded but did not occur if each dropdown used a data page. This has been resolved by ensuring the dependent property in a cascade is reset when the source property changes.
SR-B15463 · Issue 287079
New Application operator mapping refinements
Resolved in Pega Version 7.3
When using the New Application Creation wizard, the newly created operators were unexpectedly mapped to the same access group even though the access groups contained different roles. This has been corrected with changes in the pxPrepareApplicationDemoUsers and pxPrepareClonedAccessGroup activities to set transient properties for the original access group name as well as for use in lookup by demonstration users.
SR-B31876 · Issue 290136
Correspondence logic corrected for party ID
Resolved in Pega Version 7.3
When using the Send Email smart shape to send correspondence to work party, party Roles containing the string "Owner" (such as "AAOwner") caused the correspondence to be sent to the email address of the "Owner" party instead of the "AAOwner" party. This was caused by a logic error in the party list iteration that used 'contains' instead of 'equals', and has been fixed.
SR-B35965 · Issue 302489
Fixed copy from data page with optional data mapping
Resolved in Pega Version 7.3
When 'Optional data mapping' was used on a pageList property with the 'copy from data page' option enabled, data was not getting populated to the PageList if the filtered result was page type. This was traced to an issue with optional data mapping in a keyed data page, and has been resolved by changing the function to add the indexed page instead of directly using the FilteredClipboardProperty.