SR-B238 · Issue 271610
Fork shape works with both when and percentage connectors
Resolved in Pega Version 7.2.2
An error was generated when trying to save a flow rule that contained both percentage connectors and When rules fork shapes. This was due to the 'ValidateModelProcess' activity getting all connectors in the flow and checking if there is at least one connector with Percentage, then iterating each decision shape by iterating the connectors and checking for percentage error scenarios. To fix this issue, the system will get the connectors from the decision shape in context and check if at least there is one percentage connector, then check for validation after that.
SR-A93295 · Issue 260100
Page-Copy given 'when' rule for assembler switch
Resolved in Pega Version 7.2.2
Performance issues relating to XML stream assembly were identified as an assembler switch problem in the Page-Copy Activity Method step. To improve response, a 'when' rule has been instituted to control switching between the old assembly Action aspect or the Model aspect in a scoped way, but can be overridden in the parse XML rule applies-to class.
SR-A24793 · Issue 252731
Expandable When parameter handling updated for repeating layouts
Resolved in Pega Version 7.2.2
In a dynamic layout, the "Expandable When" parameter was checking the first of the several "pxResults" pages but was not checking that condition for all the pxresults (pages). This was due to a situation where once the when condition evaluated to true, all the results below the when condition were not checked. The expanded parameter handling has been updated to correct this.
SR-A76831 · Issue 255486
Grid headers show "Required" when PegaWAI enabled
Resolved in Pega Version 7.2.2
With PegaWAI enabled, grid headers marked as required were displaying the noncompliant '*' label instead of the accessibility-enabled 'required' label. This was due to missing styles for table headers and has been corrected.
INC-185847 · Issue 669526
Handling added for disabling weekends when no weekends are available
Resolved in Pega Version 8.7
A browser exception was generated while selecting the option “Disable weekends”. This was traced to a malformed array of weekends in a scenario where the Data-Admin-Calendar instance had all business days checked (i.e., no weekends). To resolve this, DatePickerAssembly and pzGenerateDatePicker have been updated to handle the case when there are no weekends available in the Data-Admin-Calendar instance.
SR-D29809 · Issue 505255
Extra <p> tag removed when not needed in RTE generation
Resolved in Pega Version 8.3.1
The RTE was generating an extra <p> tag in the Review harness or when the RTE was non-editable, causing alignment issues in the UI when RTE was displayed using inline dynamic layout with a textarea. This has been corrected.
SR-A77023 · Issue 257680
Fixed Firefox Checkbox onclick events triggering when not clicked
Resolved in Pega Version 7.2.2
When using Firefox, clicking in between the label and checkbox captured the target as span. Data-click actions were configured to trigger with this click, but the logic to toggle the checkbox value on click was missing. This has been corrected in ui_events on clickHandler.
SR-A77023 · Issue 255255
Fixed Firefox Checkbox onclick events triggering when not clicked
Resolved in Pega Version 7.2.2
When using Firefox, clicking in between the label and checkbox captured the target as span. Data-click actions were configured to trigger with this click, but the logic to toggle the checkbox value on click was missing. This has been corrected in ui_events on clickHandler.
SR-A94142 · Issue 263214
Check added to handle submitModal button use
Resolved in Pega Version 7.2.2
After upgrade, running a script under the actions tab of a button was not working as expected though the standalone run did work. This has been fixed with the addition of a check to differentiate between a pzModalButton and a normal button.
SR-A99523 · Issue 266451
LockInformation section uses field value label
Resolved in Pega Version 7.2.2
The label in pzLockInformation section was hard coded, causing the string "You have lost the lock! Please reopen the item to continue your work." to not have a field value. This has been changed to create a Field Value and use the same in the label.