SR-120195 · Issue 180041
Smoothed adding rows to a repeat grid after canceling previous action
Resolved in Pega Version 7.1.8
When adding an item to the Repeat Grid, a small modal is opened to allow value entry to associate with that row. However, canceling the modal and then clicking on the button to add a row failed to open the modal a second time and it was not possible to add another row to the Repeat Grid. This was caused by the previous canceled modal call remaining active resulting in the new event being skipped. To correct this, the modal dialog incall property will be reset so it may be properly opened as expected following a previous cancelation.
SR-120218 · Issue 180532
Corrected dismissal of discard/cancel modal popup
Resolved in Pega Version 7.1.8
The out-of-the-box discard and cancel modal pop up was not closing up on single click. This was caused by a redundant action from the pyNewCaseHeaderInner section that has now been removed.
SR-120276 · Issue 179709
Corrected handling for DecimalPrecision Property Qualifiers in Advanced tab
Resolved in Pega Version 7.1.8
When DecimalPrecision Property Qualifiers were added to Advanced tabs, the Min/Max character limitation was not working for numeric input (Decimal) in pxTextInput or pxNumber. This was caused by an error in the initialization, and has been corrected.
SR-120468 · Issue 184320
Appearance order retained for multiple swimlanes
Resolved in Pega Version 7.1.8
After putting multiple swimlanes in a flow, the order of their appearance was returning to the original state after saving it. This was caused by the rendering being performed in the order the server store/sent the swimlane data. To ensure proper behavior, the swimlanes are now reordered based on the swimlane layout (horizontal, vertical) and their coordinates before being rendered.
SR-120468 · Issue 185827
Appearance order retained for multiple swimlanes
Resolved in Pega Version 7.1.8
After putting multiple swimlanes in a flow, the order of their appearance was returning to the original state after saving it. This was caused by the rendering being performed in the order the server store/sent the swimlane data. To ensure proper behavior, the swimlanes are now reordered based on the swimlane layout (horizontal, vertical) and their coordinates before being rendered.
SR-120477 · Issue 180530
Smoothed navigation for multiple screen trees
Resolved in Pega Version 7.1.8
In a tree navigation screen flow with multiple screens, the screens have client side validations which were not working when navigating from the tree navigation control link but did work when the "Next" or "Back" buttons were clicked. This was found to be a problem in the work flow UI doc submit method where validation was skipped if the Activity was "GoToPreviousTask". To resolve this, a check was added (previousEntryPoint) if submit is called from back button of screen flow.
SR-120556 · Issue 180535
Dirty prompts functioning with JAWS
Resolved in Pega Version 7.1.8
When a dirty work object is closed, you are warned with a dirty prompt. When this dirty prompt is sourced via the modal/section pyDirtyCheckConfirm, JAWS did not gain focus to read this prompt and a manual click on this was required to read any elements. This was an issue where JAWS wasn't reading the dialog because there was no role attribute attached. This has been corrected.
SR-120564 · Issue 179056
"Configurable Error Section" option now supported by JAWS
Resolved in Pega Version 7.1.8
It was reported that a custom error section on top of the harness created using the "Configurable Error Section" option was not being read by JAWS . This was due to the custom work flow section not being supported in the out-of-the-box PRPC Accessibility Mode, and the necessary support has been added.
SR-120603 · Issue 178264
RTE tooltips localization expanded
Resolved in Pega Version 7.1.8
The localization for RTE tooltips has been expanded to include the spin/roll button (to select font size).
SR-120615 · Issue 183300
SQL rules searches now display full details
Resolved in Pega Version 7.1.8
Expanding the connect SQL rules in a search result did not display "ruleset version," "updated by" or "availability" details. This was caused by a mismatch in the RuleName formatting for the Search Results and Transform activities, and has been corrected.