SR-B36254 · Issue 293924
Removed error appearing on multiple tabs
Resolved in Pega Version 7.3
On a multiple tab scenario when client side validation was triggered on a specific tab ad that layout was under a tabbed repeat in a section, a warning icon appeared on other tabs as well. This is due to marking for tab repeat not being supported at this time: in these conditions, the system will skip the marking error.
SR-B36260 · Issue 296921
Fixed mobile native control submit clearing property/date
Resolved in Pega Version 7.3
When the "native control on mobile" option is checked for a date-time property, a runtime error on submit cleared the property value/date value. To correct this, if the datetime property gets any error messages on submitting the screen, the response of the datetime control will not generate the Value or overwrite it.
SR-B36307 · Issue 292510
prconfig added to disable tracer checks in census
Resolved in Pega Version 7.3
There was some contention when checking for tracer to log trace events for access denials in a census application. Since tracer is not used in census, a prconfig switch has been added to disable these tracer checks.
SR-B3633 · Issue 274006
Tab layout focus corrected for "show next error"
Resolved in Pega Version 7.3
The "Show Error" and "Show Next Error" functionality in the layout group of type tab were not giving focus to the correct element when clicking the 'show next error' if an autocomplete was present. Instead, focus was given to the element whose CSS property display was set to none. To correct this, an additional filter condition has been added to ensure the expected focus.
SR-B36418 · Issue 293162
More descriptive error message for RAP import
Resolved in Pega Version 7.3
In order to clarify that Schema migration does not support importing a table with the same name as an existing view or a view with the same name as an existing table, the code has been updated to throw a more descriptive exception.
SR-B36431 · Issue 293350
SOAP simulations restored
Resolved in Pega Version 7.3
SOAP simulations were not executed as expected due to the hard coded value SOAP being removed and made generic. This has been fixed by updating the service type to SOAP in the parameters passed to the simulations section.
SR-B36556 · Issue 301271
Internet Explorer text input focus fixed
Resolved in Pega Version 7.3
In IE, the mouse could not be used to return focus to a text field once there was text input followed by other clicks around the screen. This was traced to a grid inside the modal dialog launched by a button with an incorrect div that led to the text box losing editability. To resolve this, a check has been added.
SR-B36567 · Issue 296311
Full year date data made available to Excel for consistency
Resolved in Pega Version 7.3
Inconsistencies were seen in the handling of the year field on dates using Date or pxDateTime as a control, at times displaying the same input as 01/01/1917, 01/01/17, and 01/01/2017. To fix this, the date format in pzExport_Date_RD control has been modified from DEFAULT_DATE_SHORT to DEFAULT_DATE_SHORT_YYYY so the full year component is available for Excel.
SR-B3657 · Issue 274527
SAML authentication enhanced to detect encoded/decoded response
Resolved in Pega Version 7.3
Even though SAML authentication was working as expected, an error message was being logged when the system attempted to process the authentication response as encoded before falling back to process it as decoded. To remove confusion, Fallback has been removed and instead the system will intelligently identify the response as encoded/decoded and handle it appropriately without generating an unnecessary error.
SR-B3657 · Issue 280763
SAML authentication enhanced to detect encoded/decoded response
Resolved in Pega Version 7.3
Even though SAML authentication was working as expected, an error message was being logged when the system attempted to process the authentication response as encoded before falling back to process it as decoded. To remove confusion, Fallback has been removed and instead the system will intelligently identify the response as encoded/decoded and handle it appropriately without generating an unnecessary error.