SR-D46681 · Issue 514433
SnapStart supports SAML2 Authentication
Resolved in Pega Version 8.2.5
When using an HTTP Post to SnapStart into Pega using PRCustom style or PRAuth style SAML authentication, the login was looping back to the login request. Investigation showed that the Pega ACS was posting data properly back to the RelayState URL, however the login activity was not getting the SAMLResponse and simply sent a SAML Login Request again. This has been fixed by updating reqContextURI in case of SAML2 Authentication service so pyActivity=value will be passed.
SR-D43141 · Issue 512434
Support added for iFrame Mashup resize when using SPA
Resolved in Pega Version 8.2.5
After upgrade, issues were seen with an iFrame holding a Mashup not resizing as expected. This was traced to the use of an SPA portal inside mashup, and has been resolved by explicitly invoking the doharnessResize API to set proper height on iframe when using SPA.
SR-D33227 · Issue 510825
Check added for lock expiration when using Save for Default locking
Resolved in Pega Version 8.2.5
With the default case locking policy, during the process from creating a Case Object to Submit it was possible for multiple users to edit and save the same work object if the lock expired for the original user. No warnings appeared. To resolve this, handling has been added for a lock expiration scenario: previously, Save for Default locking was not considered. This has now been updated with a check that will evaluate whether or not the lock is gone before attempting to save.
SR-D38492 · Issue 505491
Batching now enabled when using IH Summary shape in substrategies
Resolved in Pega Version 8.1.7
Batching was not being enabled when using IH Summary shape in substrategies. This was traced to the IH_SUMMARY_CACHE field not automatically being passed to sub-strategies, and has been corrected.
SR-D48881 · Issue 514602
Corrected alignment of column header and content when fixed header is used
Resolved in Pega Version 8.1.7
The tables header column was misaligned with the context columns when a fixed header was used. This has been resolved by correcting the code calculating the width of the header cells.
SR-D26133 · Issue 500723
Corrected alignment of column header and content when fixed header is used
Resolved in Pega Version 8.1.7
The tables header column was misaligned with the context columns when a fixed header was used. This has been resolved by correcting the code calculating the width of the header cells.
SR-D28898 · Issue 501653
Corrected alignment of column header and content when fixed header is used
Resolved in Pega Version 8.1.7
The tables header column was misaligned with the context columns when a fixed header was used. This has been resolved by correcting the code calculating the width of the header cells.
SR-D42583 · Issue 514486
Label of a field is correctly rendered when a section is re-used with a visiblity condition
Resolved in Pega Version 8.2.5
The label of a field was not being rendered/visible when a section with a 'visible when' condition was re-used in different Page Contexts. The label was displayed correctly if 'Run visibility condition on client' was checked. As part of performance improvements made in a previous version, label generation was moved under the dlcellvisibility flag. Because of this, if a section was re-used at multiple places with different contexts and one place had visibility false and another had visibility true, the labels were not getting generated for the visible section. To resolve this, Label Generation has been moved out of dlcellVisibility to ensure label metadata will always be generated. Updated performance improvements have been made instead by way of a DSS setting (generateCellMetadata) so that when generateCellMetadata is true, the label generation will honor dlcellvisibility to generate the label metadata.
SR-D42583 · Issue 514488
Label of a field is correctly rendered when a section is re-used with a visiblity condition
Resolved in Pega Version 8.1.7
The label of a field was not being rendered/visible when a section with a 'visible when' condition was re-used in different Page Contexts. The label was displayed correctly if 'Run visibility condition on client' was checked. As part of performance improvements made in a previous version, label generation was moved under the dlcellvisibility flag. Because of this, if a section was re-used at multiple places with different contexts and one place had visibility false and another had visibility true, the labels were not getting generated for the visible section. To resolve this, Label Generation has been moved out of dlcellVisibility to ensure label metadata will always be generated. Updated performance improvements have been made instead by way of a DSS setting (generateCellMetadata) so that when generateCellMetadata is true, the label generation will honor dlcellvisibility to generate the label metadata.
SR-D39577 · Issue 507203
Dynamic Layout Group renders properly when nested sections use PageGroup as source
Resolved in Pega Version 8.2.5
After upgrade, an included Section rule was not rendered in Dynamic Layout Group (repeat) layout at run time. This issue was only seen when PageGroup was used as the source for the dynamic layout group, and investigation showed that under these conditions the pagegroup state for nested sections was not propagating a needed editable property. This has been corrected.