SR-B68434 · Issue 325774
Null parameter handling added to InitializeContextPage data transform
Resolved in Pega Version 7.3.1
When the end user portal was launched and a few tabs were opened, logging into a new session with same user ID caused content in tabs to generate an error and not load. This failure was traced to null parameters being passed to the InitializeContextPage data transform of the display harness activity, and the code has been updated to handle empty data transform parameters.
SR-B68837 · Issue 318361
Bad 'when' fixed for ruleset translation
Resolved in Pega Version 7.3.1
Due to an error in a 'when' condition that caused incorrect overwriting, Spanish rulesets were being displayed for saving correspondence/paragraph rules irrespective of the language translations that had been imported. This has been fixed.
SR-B69149 · Issue 320820
Header level reading fixed for JAWS
Resolved in Pega Version 7.3.1
JAWS was not reading the header levels properly due to them being treated as heading level 2 even though there were headings at level 1. This has been fixed by adding the aria-level for the header div to the element with role=heading.
SR-B69403 · Issue 317542
Refined Modal Dialog RUF for standard format override
Resolved in Pega Version 7.3.1
The modal dialog format was applying multiple style formats if the "Standard" format was overridden. The pzSkinGenWFModalDialog RUF has been refined to prevent this.
SR-B69420 · Issue 320400
Repeating Dynamic Layout can use source for base in Microsoft Internet Explorer
Resolved in Pega Version 7.3.1
When using Microsoft Internet Explorer, repeating dynamic layouts were only taking Data- as the base and could not be configured to add a source. Dragging and dropping a section did not provide the source either. oSectionBody, which is a DOM element, is sent to redrawSectionFieldSetCaptionInfo as a parameter. In Microsoft Internet Explorer this element is removed from the DOM and hence has no parentElement. This is the reason that the call to redrawSectionFieldSetCaptionInfo was failing. To resolve this, a check has been added to see if the oSectionBody is in the DOM by using the check oSectionBody.parentElement at the start of redrawSectionFieldSetCaptionInfo.
SR-B70222 · Issue 322936
Property value submit event for screen flow works in Microsoft Internet Explorer
Resolved in Pega Version 7.3.1
FinishAssignment Action was configured as an Enter Key event for Dynamic layout in order to submit the flow in screenflow, but at runtime when using Microsoft Internet Explorer some of the property values were not submitting to the clipboard as expected. The issue was a defect in the UI framework related to submitting a form through any event when the input had focus in Microsoft Internet Explorer, and a check has been added to resolve the error.
SR-B71754 · Issue 325868
OpenAssignment in WSS always opens in same window
Resolved in Pega Version 7.3.1
A difference was seen in the behavior of a button configured with OpenAssignment in the WSS portal; if the site was using prgateway the button would open the assignment in the same window, but if the site was using mashup code clicking the button opened the assignment in a new window. This was caused by a logic difference in the two cases, and has been fixed with changes in pega.desktop.support.openSpace to call openSpaceInGadget if the composite gadget is not available in the portal. This will cause the assignment to always open in the same window as expected.
SR-B72892 · Issue 323517
Error message display fixed for RG read-only field
Resolved in Pega Version 7.3.1
Incorrect behaviors were seen with displaying errors when a field in a repeat grid table was configured as "Read-only (always)" and "Show validation messages in read-only mode" was on. In Google Chrome, the UI form did not contain the corresponding error image in the field due to the only error icon div getting hidden. In Microsoft Internet Explorer 11, the UI form contained the corresponding error image in the field, but only part of this image was visible due to changes of column/field width not being honored. These issues have been fixed by updating the CSS in the pzbase-grids.css file.
SR-B73126 · Issue 323350
Fixed autocomplete cell value disappearing on blur
Resolved in Pega Version 7.3.1
After upgrade, an autocomplete configured with data page "onChange - Post Value" had cells whose entered value disappeared onBlur of the autocomplete cell. The reported issue is a UI framework defect with templating enabled, and was traced to an issue with the change tracker data not getting merged properly to context data after the postvalue response is received. This has been fixed.
SR-B73514 · Issue 324049
Added new function to bypass URLScan MaxURLLength
Resolved in Pega Version 7.3.1
When Pega is fronted by Microsoft IIS WebServer with either a proxy or Web Application Server plugin, the IIS advanced security options, URLScan, are used to limit the size of URLs. When the URLScan MaxURLLength is set below about 600 characters a major static content request for core PRPC UI JavaScript files is blocked. This is a known issue when using IIS Web Server, but to enable expanded use, a 'when' function named pyIsForcedSplitJS has been added that allows overwrite as required by dividing pzHarnessStaticScripts into 4 chunks to decrease length. The format is