SR-D29127 · Issue 506863
SAML data pages restored after passivation
Resolved in Pega Version 8.2.4
If login used SAML SSO, resuming the session after passivation resulted in missing or empty data pages when using an SAP integration with Pega Cloud. This was traced to a security change that modified the D_SAMLAssertionDataPage and D_SamlSsoLoginInfo data pages as readonly, causing them to not be passivated under these conditions. To resolve this, the data pages have been made editable so they will be restored as expected. This change also resolves any difficulty with SAML logoff activities in conjunction with SAP and Pega Cloud.
INC-182530 · Issue 695760
SAML datapages cleared before new authentication
Resolved in Pega Version 8.7.1
If a previous user had not logged out or timed out when using SAML authentication, a second person using the same device/browser would end up in the first user's session after performing their own authentication. Investigation showed the second login D_SAMLAssertionDataPage was not getting refreshed with the current user login details; this has been resolved by explicitly deleting the SAML Datapages before processing a new login if the session has not timed out.
INC-195519 · Issue 698497
Support added for using CFW when Pega server is unavailable
Resolved in Pega Version 8.7.1
Data synchronization changes have been added to allow Client for Windows to work in offline mode without an AppCache manifest.
INC-195511 · Issue 693219
Check added for child join class when using ABAC
Resolved in Pega Version 8.7.1
When a join was applied on a report definition and the same join class had a child class to which ABAC was applied (for some property eg., isABC), an "invalidreference" exception (isABC) was generated. This was traced to the system taking into account the child class of the join class while running the report, and has been resolved by adding a check to handle this scenario.
SR-D38492 · Issue 505489
Batching now enabled when using IH Summary shape in substrategies
Resolved in Pega Version 8.2.4
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-D39003 · Issue 505997
Threads will be updated to maintain assembly context when using Static Assembler
Resolved in Pega Version 8.2.4
When running the Static Assembler utility from UI, the assembler process completed successfully but the PegaRULES.log was flooded with the FATAL exception "Usage error - next Executable not based on current". This error was generated from com.pega.pegarules.session.internal.mgmt.Executable constructor, and indicated an issue with the thread context being different from the assembly context. To resolve this, the system has been modified to update the context of thread to what is expected as assembly context.
SR-D39302 · Issue 507981
Report name in tab uses localization
Resolved in Pega Version 8.2.4
After creating a field value with field name as pyCaption to localize the report definition name, the title in the report definition tab was not translated. This was traced to Step 1 of the activity displayReport using an old localization function, and has been resolved by changing the localization of document title to use pyCaption.
SR-D26785 · Issue 495892
Corrected error when persisting temporary work object
Resolved in Pega Version 8.2.4
When persisting a temporary work object using the Persist case shape, the internal assignment handle was not updated to include the work object's ID. Subsequent attempts to access the internal assignment (such as the "Edit" button on the Review Harness) resulted in errors. Investigation showed that when a temporary case was persisted, pyInternalAssignmentHandle was not getting recalculated after pzInsKey was updated. To resolve this, the configuration on the edit button has been modified to use .pxFlow(pzInternalCaseFlow).pxAssignmentKey which is what pyInternalAssignmentHandle declare expression was also returning.
SR-D29809 · Issue 505256
Extra <p> tag removed when not needed in RTE generation
Resolved in Pega Version 8.2.4
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.
INC-199558 · Issue 693302
Updated calling activities from refresh to use invokeActivity
Resolved in Pega Version 8.7.1
The Refresh DX API was inconsistently throwing an index out of bound exception when using a checkbox which invokeed an activity on check to save and commit the case. This has been addressed by updating calling activities from refresh to use invokeActivity, and a try/catch has been added to capture exceptions and add a page message if the activity is not found or has an error.