SR-B52664 · Issue 310856
Web mashup rendering fixed for iPhone/iPad
Resolved in Pega Version 7.3.1
The web mashup section was not rendering in iPhone and iPad due to a race condition between two network calls. Changes have been made to "PegaCompositeGadgetMgr.js" and "openCookieConsent" to delay gadget processing and resolve this issue.
SR-B52664 · Issue 312829
Web mashup rendering fixed for iPhone/iPad
Resolved in Pega Version 7.3.1
The web mashup section was not rendering in iPhone and iPad due to a race condition between two network calls. Changes have been made to "PegaCompositeGadgetMgr.js" and "openCookieConsent" to delay gadget processing and resolve this issue.
SR-B32323 · Issue 309342
Fixed SC toggling for Interaction Driver
Resolved in Pega Version 7.3.1
Two buttons on the interaction driver - 'Add Task' and 'Submit' - were freezing after more than one service case was created and the user toggled between two service cases. This has been fixed by modifying the code to handle scenarios where an onclick attribute is already present for a link.
SR-B66561 · Issue 316940
Empty grid check added to Add Item (Before) action
Resolved in Pega Version 7.3.1
Using "Add Item -> Before" to add the first row in an empty grid configured with page list as a source showed the following issues: 1. Focus was gone and not set on the first row. 2. The grid header disappeared, and the first row added appeared. 3. It was not possible to delete the first row. Even when manually clicking to set focus on the row, the system still asked for selection of the row to delete. This was traced to the "add before" function using updateHandlesAfterInsert even though the grid was empty. The postUpdate API in ui_grid.jshas been updated with a check to resolve this.
SR-B64984 · Issue 314348
Web mashup mime header set in Microsoft Internet Explorer
Resolved in Pega Version 7.3.1
When a response included the "X-Content-Type-Options: nosniff" header, the Microsoft Internet Explorer browser would not accept scripts and styles in case of mime-type mismatch. This was traced to the pzIncludeMashupScripts request not setting the mime type to text/JavaScript, and has been fixed.
SR-B49097 · Issue 308145
Validation check added for empty sections of non-template hierarchical dynamic layouts
Resolved in Pega Version 7.3.1
When a section which includes hierarchical dynamic layouts was created without a template, including an empty section for the inner dynamic layout header did not show any exception in the screen. The same use case did throw an error when using a single dynamic layout. This has been fixed by changing GridHeaderElements to not generate a call for a section include if the Section name is empty, ensuring the expected behavior of a section rule being validated and generating the error message when there are any empty sections.
SR-B44050 · Issue 319237
Accessibility improved for modal dialog errors
Resolved in Pega Version 7.3.1
When an error occurred in the modal dialog and was displayed at the top of the screen, the focus was not directed to the top of the screen to properly read the error messages for accessibility. Instead, focus shifted to the cancel button at the bottom of the screen for server side validation. To improve accessibility, code changes have been made to make the error section focusable and update the cyclic process (updating boundary elements of modal dialog) for the focus handling.
SR-B44050 · Issue 319888
Accessibility improved for modal dialog errors
Resolved in Pega Version 7.3.1
When an error occurred in the modal dialog and was displayed at the top of the screen, the focus was not directed to the top of the screen to properly read the error messages for accessibility. Instead, focus shifted to the cancel button at the bottom of the screen for server side validation. To improve accessibility, code changes have been made to make the error section focusable and update the cyclic process (updating boundary elements of modal dialog) for the focus handling.
SR-B55736 · Issue 311735
Invalid date field will remain after error message displayed
Resolved in Pega Version 7.3.1
When an invalid date was entered into a date field and the page was submitted, an alert with the message "Please correct flagged fields before submitting the form!" was displayed. Once the alert is dismissed, the value in the date field was reverted/reset to the old pre-populated date instead of the incorrect one. This created confusion as the date field now appeared valid and did not match the error message. To clarify the action needed, the error on the date field will remain and not be reset.
SR-B67239 · Issue 316374
pyCaseWorker offered during portal choice
Resolved in Pega Version 7.3.1
When choosing a portal on the access group, the pyCaseWorker one was not shown even though it was described in the documentation. To resolve this, an activity to update the property "pyDesktopType" to "User" has been added for the pyCaseWorker, pyCaseManager7, and pyPega7Express portals.