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.
SR-A85709 · Issue 255759
Cleared erroneous dirtycheck popup on DropDown using lazyload
Resolved in Pega Version 7.2.2
When a pxDropDown was configured with load mode "After screen renders", the "selected" attribute was not correctly set on the HTML and the dirtyCheck failed even when the values were saved. This was due to the "Selected" attribute on options tag not being set properly when the dropdown mode was set to lazyload (after screen render), and has been fixed.
SR-A22284 · Issue 249432
Data pages used as search fixed for mobile clients
Resolved in Pega Version 7.2.2
In an application accessed via mobile client, a data page used as source for a search was not rendering results when attempting a second search. This issue was happening because of a race condition, and has been resolved with an added settimeout for the asyncrendercallback of the RDL template.
SR-A22996 · Issue 250572
Logic updated for 'when' controlled edit modes in embedded sections
Resolved in Pega Version 7.2.2
Complex layers of 'when'-controlled edit modes were not being properly applied in embedded sections. For example, if the main section included another section and the read-only nature of the included section was controlled by a when rule and the included section went on to include another section that contained a Repeat Grid/ Row repeat, the edit mode of the parent was not considered when evaluating the edit mode of the child. This was an issue with the logic governing precedence considerations, and has been updated with additional checks.
SR-A22996 · Issue 252883
Logic updated for 'when' controlled edit modes in embedded sections
Resolved in Pega Version 7.2.2
Complex layers of 'when'-controlled edit modes were not being properly applied in embedded sections. For example, if the main section included another section and the read-only nature of the included section was controlled by a when rule and the included section went on to include another section that contained a Repeat Grid/ Row repeat, the edit mode of the parent was not considered when evaluating the edit mode of the child. This was an issue with the logic governing precedence considerations, and has been updated with additional checks.
SR-A22996 · Issue 248338
Logic updated for 'when' controlled edit modes in embedded sections
Resolved in Pega Version 7.2.2
Complex layers of 'when'-controlled edit modes were not being properly applied in embedded sections. For example, if the main section included another section and the read-only nature of the included section was controlled by a when rule and the included section went on to include another section that contained a Repeat Grid/ Row repeat, the edit mode of the parent was not considered when evaluating the edit mode of the child. This was an issue with the logic governing precedence considerations, and has been updated with additional checks.
SR-A76837 · Issue 257171
Resolved blank property screen lock when WAI enabled
Resolved in Pega Version 7.2.2
When PegaWAI was enabled and a property-set-message method, run by clicking a button, set an error message to a blank property on the user portal (not in a flow), the screen became disabled. After entering a value in the field, the screen was still disabled and the error was not cleared and appeared in a fixed position on the page. This has been fixed by adding a null check to the displayError method in the harness_accessibility.js to handle conditions when there are no forms present.
SR-A95614 · Issue 263958
Modified logic for displaying default accordion tab with visibility when
Resolved in Pega Version 7.2.2
When the default tab selected in an Accordion was hidden by a visibility condition, the whole default tab calculation was incorrect and did not display properly. This has been fixed by modifying the defaultTab calculation logic when visible when conditions are present.
SR-A95614 · Issue 263995
Modified logic for displaying default accordion tab with visibility when
Resolved in Pega Version 7.2.2
When the default tab selected in an Accordion was hidden by a visibility condition, the whole default tab calculation was incorrect and did not display properly. This has been fixed by modifying the defaultTab calculation logic when visible when conditions are present.