SR-B64734 · Issue 315506
Column click focus fixed for >10 column report
Resolved in Pega Version 7.3.1
When there were more than 10 columns in a report, scrolling up to last column and right clicking on it caused the focus to move back to the first column and the window auto-scrolled back to the left. This was caused by right click shifting the focus to left-most, and has been corrected with a code change to handle the proper user agent and pass the event from showMenu.
SR-B64849 · Issue 317182
Sort/Filter alias format accepted for new configurations
Resolved in Pega Version 7.3.1
The Sort/Filter property has to be specified in .property format to sorting and filtering to work; even though it was working during runtime for already implemented properties, validation was not allowing new configuration in this format. This has been fixed.
SR-B65851 · Issue 317197
GenerateMenuAction RUF modified to trim newline strings in windowname
Resolved in Pega Version 7.3.1
While doing development and modification in Designer Studio, some sections were not opening due to the windowname containing newline characters that corrupted the JSON. This has been fixed by updating the pzGenerateMenuAction RUF to trim the strings.
SR-B66153 · Issue 315558
Fixed fr_FR localization for error field value
Resolved in Pega Version 7.3.1
An apostrophe in the translated value in the "This feature is not available in your browser" FieldValue in French was causing JS syntax issues in the pzClientLocaleData HTML rule for gStrFeatureNotSupportedInBrowser variable. This has been fixed by using double quotes instead of single quotes for wrapping variable value.
SR-B66269 · Issue 319098
Stopped Render As Single Page from replacing entire browser
Resolved in Pega Version 7.3.1
When the Render As Single Page option was enabled for Dynamic container, at runtime selecting any option from leftnav caused that harness to replace the entire screen instead of displaying as inner harness. A trace showed that the base version of the harness was getting picked up due to the way getMainPanelSection() was called from the base version and circumstanced versions. To correct this, changes have been made in the GenerateLayout RUF.
SR-B66581 · Issue 317478
Fixed browser tab fail after multiple expand/collapse
Resolved in Pega Version 7.3.1
Adding multiple class names was making the browser slow, and expanding/collapsing a section many times in a row caused the browser's tab to break down. This has been fixed by modifying the logic in expandallstyles() to add only the expanded class.
SR-B67688 · Issue 320076
Fixed use of FieldValue for templatization
Resolved in Pega Version 7.3.1
When templatization was turned on, a FieldValue containing property references that was set as a Label control value was not getting evaluated properly. This is due to the evaluated FieldValue is being set for pyLabelValue in the metadata of the label when the FieldValue actually needs to be evaluated at client side in templating. To resolve this, the property reference will be used directly instead of FieldValue.
SR-B67935 · Issue 319257
Updated decision shape iteration for StarCaseFlow
Resolved in Pega Version 7.3.1
When a decision shape in the pyStartCase flow contained only a boolean expression and the connector (true and false) of decision shape was attached to two assignment shapes, the flow worked on the desktop but did not work on mobile. This was due to 'ForDecisionShape' case being offline enabled while Library functions were not, and has been fixed by modifying the system to iterate and evaluate all the decision shapes in Create New Work .
SR-B67940 · Issue 316306
IAC authentication fixed for Mashup gadget headers
Resolved in Pega Version 7.3.1
The feature to pass headers to the Pega Web Mashup gadget Via JavaScript (i.e. browser) was not working because the Ajax request was sending a request for blank HTML and not establishing the appropriate cookie. To correct this, the Java script has been updated to better handle exceptions, and pzMashupProxyPage has been modified to replace the "blank.html" call with a new "pzMashupProcessHeaders" activity.
SR-B68379 · Issue 323426
Setting updated to determine whether Microsoft Internet Explorer 11 portal can steal desktop focus
Resolved in Pega Version 7.3.1
When Microsoft Internet Explorer 11 users multitasked and submitted something in a Customer Service portal then changed desktop windows to another non-Pega application, when the Customer Service task was completed the portal would steal desktop focus from the other application. This focus logic is by design, but Microsoft Internet Explorer 11 is more aggressive with overtaking application focus than other browsers. To counter this, focusNextElement in pzpega_ui_doc_focus .js has been updated to honor the pyIsWindowStealFocusInIEAllowed 'when' rule value.