SR-C19285 · Issue 358754
Blacklist when performance improvement
Resolved in Pega Version 8.1
When running a performance test, the when delta sync blacklist when rule generated 1.6BG of garbage. In order to improve performance, a data page will be created to hold blacklisted delta sync data pages.
INC-119754 · Issue 561523
Corrected 'when' rule context for GetCaseDetails
Resolved in Pega Version 8.4.2
The Pega REST API Get Method /cases{CaseID} failed if the Child Case was set with Manual instantiation using a 'when' rule. This was traced to the 'when' rule being resolved using @baseclass instead of the class of the case type, and has been resolved by updating the pzGetCaseDetails activity to evaluate the 'when' rule on the case page.
INC-192464 · Issue 681751
PackageComponent updated for use with repositories
Resolved in Pega Version 8.7
Exporting a zip file created by the Component wizard to a repository resulted in an error, however the same process worked as expected when the zip file was created by the Product wizard. Investigation showed that pxPackageComponent was not kept up to date with new metadata requirements for Artifactory export. This has been resolved by modifying pxPackageComponent step 7 to set Param.ArtifactType to "component" and Param.ArtifactName to [component name]_[component version]. A privilege check has also been added to zipMoveExport.
SR-C17147 · Issue 364317
Check in comments displayed when CSRF enabled
Resolved in Pega Version 8.1
After upgrade, using the Check-In modal window did not display the comments field. This was traced to a condition where an enabled CSRF token caused the data to not be rendered in the UI when a modal dialog flow is configured on the button, and has been fixed.
INC-128164 · Issue 567430
Resolved CommitError when trying to send email
Resolved in Pega Version 8.4.2
An error related to email was intermittently encountered while working on a case. This was traced to a local setting for Rule-ObJ class that set a read-only privilege, which appeared to have conflicted with the expected permissions around email template saving. This was an unexpected use case, and has been resolved.
INC-196414 · Issue 684238
OAuth token refreshed when revoked on source
Resolved in Pega Version 8.7
When an OAuth token was used to authorize the APIs in the system, revoking the token at the source, i.e. from the Service side, did not automatically refresh the token and a logoff/logon was required before a fresh token was generated. This has been resolved by adding an update to explicitly purge revoked tokens.
INC-178417 · Issue 670114
Flag reset added for grid with 'Expand When'
Resolved in Pega Version 8.7
A grid using an 'Expand When' condition worked as expected when the condition was true, but once expanded the grid did not collapse if the expand condition was changed to false even if a section/harness refresh was performed. This has been resolved by adding an update which will reset the flag when the result of 'Expand When' is false.
SR-C23138 · Issue 367878
PRPushServlet response corrected to 400 when disabled
Resolved in Pega Version 8.1
PRPushServlet is used to establish a WebSocket connection with the Pega server. When server-push is disabled, the Push engine won't get initialized and will return an empty response by logging a warning message ("Request arrived for requestor:[%s]. But PushEngine has not started." ). Unexpectedly, this process was returning HTTP status 200 instead of 400. This has been corrected.
SR-D90279 · Issue 554392
Data sync updated for use with DeferWrite
Resolved in Pega Version 8.4.2
After upgrade, attempting a data sync from the client mobile application worked for the first object submission, but the second object failed and stayed in the list. This was traced to finish assignments running back to back when deferWrite was enabled and svcPerformFlow failed to find the assignment. To resolve this, the assignmentHandle will be passed to the activity when calling the pzSetDeferWrite activity from FinishAssignmentActionProcessor.
SR-D96836 · Issue 555750
Refinements made to MarkerNode memory use
Resolved in Pega Version 8.4.2
Significant memory usage can be observed when data join in strategies are missing the join conditions. E.g., when the primary source in the strategy can have up to 300 or even more propositions, the join without the join condition would perform a cartesian product with possibly up to 400 or even more records returned. This may cause performance degradation. To guard against this, an update has been made that seeks to prevent repetitive markers being accumulated under a MarkerNode while trying not to rely on any implementation of equality and hashCode for individual marker implementations.