SR-A14336 · Issue 230881
Resolved NPE when @checkForSubstitute used
Resolved in Pega Version 7.2.1
If an assignment used the "Check Availability" setting and the operator was not available at that time, a NPE was generated in cases where the timezone needed to be parsed to complete the check. To correct this, the system has been modified to support time zones with more than 3 characters, and support was added for the IST timezone.
SR-133715 · Issue 204978
RTE <br> handling resolved when using pega:when = false
Resolved in Pega Version 7.2
Inconsistent behavior was seen when using rich text editor in paragraph rule if the pega:when was false. This was an issue with the handling of the
tags under this condition, and has been resolved.
SR-133715 · Issue 209655
RTE <br> handling resolved when using pega:when = false
Resolved in Pega Version 7.2
Inconsistent behavior was seen when using rich text editor in paragraph rule if the pega:when was false. This was an issue with the handling of the
tags under this condition, and has been resolved.
SR-A3803 · Issue 212217
Better handling for menus when using JAWS
Resolved in Pega Version 7.2
When accessibility was invoked, the Navigation menu did not indicate arrow up/down options in links with showmenu role='link' generated on them, and JAWS was not reading out that it was a link with a menu. This was an unintended side-effect of updates to avoid reading out a URL in a label/text, and corrections have been made to support accessibility so that navigational menus are read out more intuitively with JAWS.
SR-A8595 · Issue 218942
Security updated for SAML Rule keystores
Resolved in Pega Version 7.2
Password encryption has been updated for the Keystores records used by SAML Rule forms for signing and decryption in the auth service rule data.
SR-C84361 · Issue 437601
Added handling for better recovery and reset when using 'When' conditional row deletion
Resolved in Pega Version 8.1.5
Given a 'When' condition configured so that a specific row could be deleted, trying to delete another row resulted in the expected error indicating it was not possible to delete that particular row. However, attempting to then delete the row with the 'When' condition caused the same failure error to appear which could not be cleared through clicking on the Refresh button for the section. In order to resolve this, handling has been added for a scenario where Obj-Delete fails and the record is marked for deferred commit. In this situation, the system will revert Obj-Delete by way of Obj-Save-Cancel in @baseclass.pzDeleteRecord so that a subsequent Obj-Delete does not pick up the previous record and fail again.
SR-A7590 · Issue 216110
Corrected parameter page used when Flowproblems restarts
Resolved in Pega Version 7.2
Restarting the problem flow was not taking the mandatory parameters defined in the flow, instead generating the error "Required parameter Parameter_name." To correct this, the flow method body has been modified to populate the parameter page from the pyFlowParameters page before checking for mandatory parameters.
SR-A12684 · Issue 224534
Extracts count corrected when using XML as output
Resolved in Pega Version 7.2
While running an extract using XML as output, a difference was observed in the number of records being extracted when compared with 'Database Schema' as output. The Pega-BIX logs contained failed records with 'Index out of bounds' exceptions. This was traced to missing handling for the value group property references in this scenario, and has been corrected.
SR-A9773 · Issue 221357
Fixed repeating row focus when using Accessibility
Resolved in Pega Version 7.2
When Accessibility was enabled and the add icon was clicked to add a section to a row repeat, it was not possible to access the first item in first row with the keyboard. Additional added rows had the correct focus. This was traced to an issue where getFocusOnNewRow was not being called correctly, and as been resolved.
SR-A11447 · Issue 243018
Importing an archive no longer fails when using DynaTrace
Resolved in Pega Version 7.2.1
Importing an archive was failing when using the third party program DynaTrace. This was due to passivation during the import process, and the system has been modified to prevent this.