SR-A77555 · Issue 260161
Improved handling for multiple access 'when' in business event processing
Resolved in Pega Version 7.2.2
It was possible to encounter a missing page in the business event processing if event processing performed a call to tools.getThread().getAuthorization().haveAccess in multiple activities and there were several access 'when' actions defined for the class. The access 'when' requires that a work page be present to evaluate against, and depending on how the call was being performed or if passivation has occurred the process could throw an IndeterminateConditionalException and pass a null as parameter value for "aPage" parameter. To prevent this error, the activities pxCreateSummary and pxGetPrimaryClasses have been changed to pass the ClipboardPage of class for which haveAccess() is being called.
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-A87322 · Issue 260290
Enhancement to display custom properties during editing based on when
Resolved in Pega Version 7.2.2
It was assumed that if pyShowCustomProperties returns false, only the custom properties are shown while editing a report in the data explorer. This was not always true based on checkout privileges, and was therefore inconsistent with the name of the when rule. In order to meet expectations for filtering, pzPrepareReportExplorerFieldNames and runReport have been updated to reference a new 'when' rule called pyReport_ShowCustomProperties. This function will filter the properties as expected based on the available when rule and will reference pyShowCustomProperties for backwards compatibility reasons.
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.
SR-C22471 · Issue 370124
Handling added for long names when exporting DataType columns
Resolved in Pega Version 8.1
Values were not being displayed in an exported file for a column with a name exceeding 30 characters. This was traced to the values being mapped to a hashed value that truncated the name and caused the alias to not be found when expanding the data, and has been fixed.
SR-C5169 · Issue 349818
Tabs maintain state when new RDL item added
Resolved in Pega Version 8.1
Adding a new item to a repeating Dynamic layout switched all the currently selected tabs in an embedded Tab Layout Group to be the same as the last item. This was an issue with complex configuration RDL having another repeating layout (DLG) with an active 'when' based on repeating context property, and code has been added to handle the previous selected tab state and active when so tabs will retain integrity.