SR-A13882 · Issue 228926
Date Control in expandable repeating grid shows proper date value
Resolved in Pega Version 7.2.1
The Date control in the repeating grid was showing the case ID number instead of the date value when configured as master-details with expandable rows. This was due to a missed use case of the "display read-only formatting" feature where a read-only condition configured on the control returned the editable control in the response instead of read-only. This has been fixed.
SR-A13930 · Issue 227345
Calendar popup positioning fixed
Resolved in Pega Version 7.2.1
The calendar popover is positioned to the parent span instead of input, creating space between the input and calendar when there are errors. This has been fixed by positioning the calendar popover to the input field instead of parent span specifically for Text Input + Calendar mode.
SR-A13931 · Issue 227032
validation errors shown with datetime control
Resolved in Pega Version 7.2.1
If a server error occurred, client validation errors were not shown when the next focusable element was in datetime control. The issue here was that the Control change event was not properly bound to the calendar control in case of immediate focus, and this has been corrected.
SR-A14132 · Issue 232550
Improved handling for values starting with "." in Developer Portal Explorer
Resolved in Pega Version 7.2.1
A value starting with "." was being treated as a property and causing an exception error when using the Recent Explorer in the Developer portal. A catch has been added to resolve this issue.
SR-A14132 · Issue 233457
Improved handling for values starting with "." in Developer Portal Explorer
Resolved in Pega Version 7.2.1
A value starting with "." was being treated as a property and causing an exception error when using the Recent Explorer in the Developer portal. A catch has been added to resolve this issue.
SR-A14151 · Issue 244440
Autocomplete select updates as expected
Resolved in Pega Version 7.2.1
An intermittent problem was found with autocomplete that selected a previously set value if text was typed in the autocomplete box and the value was selected instead of the search text. This was traced to a press of the capslock key being interpreted as an unprintable character, causing an abort of the request and change tracker not having the correct update. The function processkey of autocompleteag.js has now been updated to not abort the request when a non-printable character is typed.
SR-A14230 · Issue 230423
IconRequired fixed for repeating layouts
Resolved in Pega Version 7.2.1
The iconRequired span was only being generated for the first row of any repeating layout structure. This has been fixed in the GenerateCellContent RUF.
SR-A14313 · Issue 227652
Autocomplete displays properly after screen rotation
Resolved in Pega Version 7.2.1
A black gap appeared on the screen of iPad and iPhone devices when tying to use the autocomplete window after the screen was rotated between Portrait and Landscape modes. This was due to the autocomplete popover not accepting a % width setting, and the display method of the popover has been modified to display properly.
SR-A14325 · Issue 228543
Repositioned BusyIndicator to cover Target element
Resolved in Pega Version 7.2.1
If the section with busy indicator was taller than the viewport height, the busy indicator mask did not cover the lower part of the section when scrolling and the section was editable. This has been fixed by repositioning the mask to cover the part of the section editable in the viewport and also show immediately on scroll.
SR-A14359 · Issue 232227
Context-aware paths for SMA jmxclient.css and global.js files
Resolved in Pega Version 7.2.1
In some cases the jmxclient.css and global.js files were not found when running SMA due to the use of relative path names. The path names have now been made context-aware.