INC-173725 · Issue 656480
Logic updated for DX API retrieving View/Action ID using embedded property
Resolved in Pega Version 8.7
While calling the DX API using Assignment ID and action ID, a 500 error response was logged indicating that the server encountered an unexpected condition that prevented it from fulfilling the request. Investigation traced this to the logic used for resolving an embedded property referenced in a control/field to identify the correct page class. In a non-work object context for flow actions the new assign page doesn't exist, but the system was checking for it and clearing off errors from the named page. This has been corrected.
SR-A8915 · Issue 220454
Jump-back page reference fixed for Tree Navigation and TabbedScreenFlow
Resolved in Pega Version 7.2
When starting a ScreenFlow from a SplitForEach using using TreeNavigation7 and TabbedScreenFlow7, the navigation harnesses were not taking the correct interested page for a jump-back on a previous assignment. This has been resolved.
INC-149823 · Issue 608352
DX API returns properly referenced icon class for embedded page
Resolved in Pega Version 8.5.2
When using the DX API to build an Angular JS UI, the response returned from the GET /cases/{ID}/actions/{actionID} api did not return the iconStyle for an icon class that uses a property reference when the flow is on an embedded page. This has been resolved by adding code to set the correct context for pzAPICreateJsonForModes and pzAPICreateJsonForField Rule-Utility-Function.
SR-A11101 · Issue 223556
Enhancement added to hide Pega Pulse delete icon/link
Resolved in Pega Version 7.2
When using Pega Pulse for communication with a company's end users, it was possible for the end user to delete a message. This was not desired behavior in scenarios where the company wants full tracking of the interactions with the end users. To accommodate this, an enhancement has been added to allow the delete button to be hidden on the client user side based on 'when' conditions through use of the new rule 'pyCanDeleteReply'.
INC-170514 · Issue 653762
Lock conflict resolved for AssignmentCheck
Resolved in Pega Version 8.7
The error "Unable to unlock this work object" sporadically appeared in both the runtime log and Pega RULES log when the robot was trying to create a case in Pega using an API call. Investigation showed that as the case was created, it was pulled by another robot (another requestor) which was using the GetAssignments API. This caused the perform assignment check to fail. To resolve this, a 'when' rule has been added to the performAssignmentCheck Activity.
INC-177665 · Issue 662020
Security updated to allow Access group switching
Resolved in Pega Version 8.7
When a member of two different access groups attempted to switch from one group to another, an "access denied" message occurred. This was traced to the use of BAC, and has been resolved by updating the pzProcessApplicationSwitch activity to use the pzEncryptURLActionString function to register the request.
INC-186868 · Issue 675245
Security updated to allow Access group switching
Resolved in Pega Version 8.7
When a member of two different access groups attempted to switch from one group to another, an "access denied" message occurred. This was traced to the use of BAC, and has been resolved by updating the pzProcessApplicationSwitch activity to use the pzEncryptURLActionString function to register the request.
INC-186654 · Issue 669115
GetStatusChanges performance improvements
Resolved in Pega Version 8.7
Performance issues were seen when running the GetStatusChanges report. This was traced to the filtering methods used, and has been resolved by updating the report definition and enhancing the filtering conditions.
SR-A11935 · Issue 223901
Application creation allowed without case selection
Resolved in Pega Version 7.2
When attempting to create an application based on CS 7.1.4 using the New Application Wizard with no cases selected, the application was not created and an error was displayed. This was traced to the RulesetName and rulesetversion params not being passed to the "pyPrepareFrameworkAssetsForGenerationPost" activity: those params are set only when Case Types from FW are selected. The system has now been updated to pass the RulesetName and rulesetversion params to the activity even when Case Types from FW are not selected.
INC-148817 · Issue 604969
Added check for ABAC policy to getassignmentdetailsinternal
Resolved in Pega Version 8.5.2
When an attribute based access control (ABAC) policy was defined on a particular class, the policy was properly applied when browsing instances of the class and directly opening the work object. However when an associated assignment was processed via the DXAPI (using the assignments service) the security was not applied and users who should not have access were able to progress the case. This has been resolved by adding a check in the pzgetassignmentdetailsinternal activity to check for work object opening security.