INC-214160 · Issue 709283
Access group context handling updated for Mobile
Resolved in Pega Version 8.8
After update, a new mobile application for a specific access group was not applying the correct access group for an operator with multiple access groups but instead used the default access group. This has been resolved by moving the logic responsible for switching access groups for Pega Mobile Client from the Authorization.getInitialAccessGroup class to the SessionAccessgroupInfo class to ensure Authorization/SessionAuthorization gets the information about the default access group for the current context.
INC-144601 · Issue 602425
Empty addresses removed from email
Resolved in Pega Version 8.4.4
After upgrade, an issue was seen when sending email to multiple 'To' addresses generated an exception if any 'To' address had an empty value. To resolve this, a check has been added that will remove any empty address from the recipientTo address list.
INC-180594 · Issue 670957
Filtering added for DisableDormantOperators
Resolved in Pega Version 8.7
When running the Disable Dormant Operators agent, many operators were seen which were dormant but not disabled. Investigation showed the activity was fetching all of the operators without filtering the deactivation state. This has been resolved by adding a filter condition in pzDisableDormantOperators to fetch only deactivate state users.
INC-175205 · Issue 652531
Agent restart made more resilient
Resolved in Pega Version 8.7
During a timeout outage, agents intermittently encountered a NoClassDefFound error and were disabled. After the database connection was restored, the agents were not automatically restarting. This has been resolved by making the code more resilient to errors; agent will be restarted when a temporary issue is detected, and the restart will be immune to most exceptions.
INC-230826 · Issue 733552
Legacy hardcoded WorkPage removed from ReassignAssignment
Resolved in Pega Version 8.8
When there was a child case Task available, attempting to transfer the case caused the system to update the Parent case .pxFlow(CreateTask) instead of the Task case .pxFlow(CreateTask). This was traced to the pyReassignAssignment activity having a legacy hardcoded page pyWorkPage defined, and this hardcoded page has been removed to resolve this issue.
INC-152442 · Issue 616668
Check added for Create Access to attachment
Resolved in Pega Version 8.4.4
After restricting access for the attachments category in a CS application, the attachment was added without category and could not be opened. This was due to the Create Attachment access not being automatically created for all categories when privileges were added, and has been resolved by adding a step to check Create Access for attachments of the respective category.
INC-154564 · Issue 617350
JAWS reads the table header and filter options separately
Resolved in Pega Version 8.4.4
When table headers for a non-optimized table with filter options received focus in Google Chrome, JAWS read the header, sort and filter options all run together. This was due to a difference in the way JAWS reads headers in Google Chrome from the way it reads them in IE, and has been resolved.
SR-C78362 · Issue 415982
Preprocessing added to GET assignments and cases
Resolved in Pega Version 8.1.3
When the /assignments/{ID}/actions/{actionID} API was called, the result of the flow action did not include either the data transform nor the activity from the preprocessing section. The system has now been updated to run preprocessing for GET /assignments/{ID}/actions/{ID} and GET /cases/{ID}/actions/{ID}.
INC-189781 · Issue 677816
Database Transaction Log update overflow resolved
Resolved in Pega Version 8.7
When automatic.resume=false was encountered during an update, cleaning up the existing codeset from previous updates ended up filling up the database transaction logs and caused the update to fail. This has been resolved by updating the process of clearing the codeset so it doesn't overflow the transaction log.
INC-208976 · Issue 719164
Enhanced SSA metrics made available
Resolved in Pega Version 8.8
In order to better diagnose delays related to the time when a Campaign is scheduled to start and the time when the Dataflow actually starts to run, an update has been made to introduce detailed metrics to cover some of the strategy execution key performance intensive areas including invocation of other non-strategy modules like adaptive model scoring and interaction history summaries. These Level 1 diagnostics are enabled by default. Additional lower level internal metrics related to SSA engine execution have also been made available by way of a DSS to collect more runtime insight for diagnosis. To enable the collection of these Level 2 SSA internal metrics, set the dataflow/shape/strategy/detailed_metrics/level2 DSS in the Pega-DecisionEngine rule set to 'true'.