SR-B35593 · Issue 297558
Fixed multi-click to dismiss Safari cookie message
Resolved in Pega Version 7.3.1
In some cases, Pega Mashup displayed a message to allow cookies for Safari users that required several clicks before the confirmation was accepted and the message was dismissed. This was caused by the system assuming the message was always the first child of a gadget, and has been fixed by using the openCookieConsent method to obtain the child div of the gadget using the "pega-mashup-cookieconsent" class and then remove it.
SR-B67293 · Issue 316457
Autocomplete fixed for complex repeating dynamic layout
Resolved in Pega Version 7.3.1
When using a repeating dynamic layout where each of the records in it had an autocomplete field, selecting a value for any autocomplete always entered the first record's autocomplete. This was an issue with templatization that caused autocomplete to replace the step page with the context's entry handle on the client for data-attributes in cases where it sat inside a repeating structure like RDL. This has been fixed. In addition, the API pega.ui.template.DataBinder.resolveIndex() has been deprecated and the call to it has been removed.
SR-B52083 · Issue 315414
Scrolling does not select checkboxes/buttons
Resolved in Pega Version 7.3.1
Radio buttons and checkboxes were becoming selected inadvertently while scrolling due to a touch events error. This has been fixed by setting the system to ignore a touch event when target is radio or checkbox while scrolling.
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.