SR-B77020 · Issue 326989
Help file update to clarify Precondition exceptions do not have error handling
Resolved in Pega Version 7.3.1
The rule-/rule-obj-/rule-obj-activity/stepstransition help file documentation has been corrected to indicate the Exception handling does not cover any conditions that might occur in the precondition.
SR-B37334 · Issue 314101
Cleaned up unexpected tooltip
Resolved in Pega Version 7.3.1
Attempting to set automatic input validation of HTML5 forms to be disabled within a Pega-based application by using "Change control settings -> Presentation -> Editable Format- > Type = text" resulted in a tooltip appearing for the field in the desktop. As it is only required for mobile, the system will avoid the same for desktop.
SR-B41092 · Issue 315609
Large Data Page works on repeating layout
Resolved in Pega Version 7.3.1
Using LDPs for Dynamic selects worked as expected in a mobile app, but not when used for a repeating layout in a mobile app or offline. This was traced to an issue when DP with node scope was used; regex to get the actual DP name from hashed version was not working. This has been fixed.
SR-B46212 · Issue 315461
fr_FR localization added for BrowseMultiDD labels
Resolved in Pega Version 7.3.1
French localization has been added to the labels Browse, Subject, Category and File for the pzAttachFileBrowseMultiDD section.
SR-B46588 · Issue 305524
Encoding of "&" fixed for New Document harness launch
Resolved in Pega Version 7.3.1
If the input property contained the "&" character anywhere in the parameter passed to data transform to launch a "New Document" harness, an error was seen on the screen and the logs. This issue was caused by improper partial encoding of the parameter, and has been corrected.
SR-B48649 · Issue 310650
doUIAction revised to work better with frameless Harness
Resolved in Pega Version 7.3.1
When the DynamicContainer used in Harness was frameless, calling workunlock in doUIAction resulted in "Obj-Save" failing and the activity pyWorkPage being deleted. To resolve this, changes were made in the doUIAction activity to skip deleting pyWorkPage if it is a primary page and to skip releasing the lock if the action is 'display harness replace current'.
SR-B51458 · Issue 308564
PegaMarketing localization tuned
Resolved in Pega Version 7.3.1
While localizing the Pega Marketing application, English strings were found in several places from Decisioning in particular, but also in the Platform in general. The localization for these has been fixed.
SR-B52673 · Issue 312131
Focus issue fixed for expanding DL header in Microsoft Internet Explorer 11
Resolved in Pega Version 7.3.1
When the dynamic layout collapsed header was expanded in Microsoft Internet Explorer 11, the focus did not stay on the current dynamic layout but instead went to the top of the section (i.e., the topmost dynamic layout in the section). This issue was caused by Microsoft Internet Explorer 11 firing the focus handler even on the elements which did not have tabIndex, and has been resolved by adding a check for Microsoft Internet Explorer to prevent firing focus on the wrong element.
SR-B53073 · Issue 313234
Handling fixed for properties with a leading dot
Resolved in Pega Version 7.3.1
Inconsistencies were seen in working with properties across different browsers: 1. If a field was set as requiring entering a property, pressing the arrow down to select the first value (i.e. topmost Page Name) caused the focus to point to the icon to the right of the control in Microsoft Internet Explorer and Google Chrome. 2. If it was not a required field, the focus was kept and the property could be set without using the mouse to reposition the focus to the field when in Microsoft Internet Explorer or Firefox, but only after HF was installed in Google Chrome and not for Autocomplete control. 3. When configuring Autocomplete control, the 'dot' disappeared when entering property names of embedded pages from the report based on exposed property when using Microsoft Internet Explorer, or if HF was installed in Google Chrome. This was found to be an issue where the non-required fields having a dot as prefix were having that starting dot trimmed off. To fix this, a check for extra dots has been added before trimming.
SR-B56228 · Issue 316573
Fixed conditions disappearing in Microsoft Internet Explorer delegated decision table
Resolved in Pega Version 7.3.1
If there were two or more conditions with OR in a delegated decision table in Microsoft Internet Explorer, conditions disappeared when the Show conflicts button was clicked. The same steps worked as expected in Designer Studio. This was traced to Microsoft Internet Explorer considering text nodes also as valid XML nodes and has been fixed by adding a nodeType check to pzRuleDeclareDecisionTableStandard.