SR-A39964 · Issue 265562
Corrected unexpected rounding of decimal property
Resolved in Pega Version 7.2.2
Decimal value was incorrectly being rounded in the control for a decimal property which has Use Validate in place. This happened when the edit validate rule on the property failed and was then formatted using Double instead of BigDecimal. This has been fixed by updating the pxNumber control generation logic in the pzGenerateTextInput RUF to use BigDecimal instead of Double.
SR-A92731 · Issue 264546
Localization wizard correctly narrows to only rulesets
Resolved in Pega Version 7.2.2
Despite narrowing the localization wizard to select only rulesets, platform rules and messages ere also picked. This has been corrected by modifying the logic in the pzGetCLassLabels activity to only get populated rulesets when this filter is used.
SR-A21014 · Issue 246267
Busy indicator masking position adjusted for scrolling
Resolved in Pega Version 7.2.2
Due to an error in computing the XY position values, the busy indicator mask was not properly moving with a vertical scroll on a page with a popup error box. This has been fixed.
SR-A88333 · Issue 256129
Corrected Interaction Header unexpected refresh
Resolved in Pega Version 7.2.2
Every time a new intent task was launched or closed in Interaction Portal, the Interaction header refreshed without any explicit configuration to refresh the header. This was due to the process used when evaluating the cross thread change tracker and has been fixed.
SR-A77524 · Issue 255216
Removed undesired lock in Read-only Expand Pane
Resolved in Pega Version 7.2.2
Expand Pane was locking the work object in a Repeating Grid Layout even when the Display Details Read-Only check box was selected. This lock was acquired when the row was expanded and a thread was created. This was not the desired behavior, and has been resolved with modifications to the ui_modaldialog js function to handle the case of read-only Flowaction.
SR-A93522 · Issue 262384
Validation highlights correct field with duplicated sections
Resolved in Pega Version 7.2.2
For business purposes, the same section was included twice in the UI to allow the left part to be used as read-only to see the old data while the right part was editable to modify existing data. When validation triggered an error to be displayed (required attribute set to Always) the message correctly appeared under the impacted control, but the RO label was shown in RED because the same labels were used for the read-only and editable components. This has been corrected to ensure that the correct labels get highlighted after the validation.
SR-A93522 · Issue 262361
Validation highlights correct field with duplicated sections
Resolved in Pega Version 7.2.2
For business purposes, the same section was included twice in the UI to allow the left part to be used as read-only to see the old data while the right part was editable to modify existing data. When validation triggered an error to be displayed (required attribute set to Always) the message correctly appeared under the impacted control, but the RO label was shown in RED because the same labels were used for the read-only and editable components. This has been corrected to ensure that the correct labels get highlighted after the validation.
SR-A70873 · Issue 252499
Base Lock persists in modal action with expanded grid
Resolved in Pega Version 7.2.2
Given a work object Expand Grid in a modal, expanding a row and then submitting the modal caused the Base Lock to be released. This has been corrected.
SR-A90790 · Issue 262061
Layout group tab focus issue fixed
Resolved in Pega Version 7.2.2
he user is having a tabbed layout group, by imposing If visibility when conditions were imposed on a tabbed layout group such that only one tab was visible in Section pyCaseContent, the default Information tab did not receive focus upon completion of the assignment and all of the information was not rendered after a manual focus click. This was an error in the expand indication parameter value handling for the tab layout group, and has been fixed.
SR-A101626 · Issue 272644
Height properly set for opening report in Portal
Resolved in Pega Version 7.2.2
Height was not being properly set when opening a report in the harness due to the resize function incorrectly handling expanded items. This has been fixed.