SR-B64353 · Issue 313990
Resolved assignment error when competing with SLA
Resolved in Pega Version 7.3.1
An Assignment error was occurring when the SLA competed with the user for an assignment. This was an error with setting the success indicator in the EstablishContext Activity, and has been fixed.
INC-175630 · Issue 653863
Application selections only announced when visible
Resolved in Pega Version 8.7
The elements of the application switcher were being announced by the NVDA screen reader even when toggled off, i.e. not visible. The issue was occurring because the focus was remaining at the search bar even after closing the app switcher window, and has been resolved by adding the necessary logic to switch the focus.
SR-B67327 · Issue 317826
pxUrgencyWorkStageSLA properly resets when no SLA on next stage
Resolved in Pega Version 7.3.1
pxUrgencyWorkStageSLA was not being reset when the next stage did not have an SLA. This has been resolved.
SR-B57192 · Issue 315081
Performance enhancement added to optimize evaluation of 'when' calls in GetFlowData
Resolved in Pega Version 7.3.1
A lot of when conditions triggered as part of GetFlowData out-of-the-box activity were causing slowness when the Java Step (4) did its evaluation. Current screen flow navigation would evaluate all the when rules till the end of the flow to determine the flow navigation. To improve performance, an enhancement has been added to the GetFlowData activity to prepare pyFlowData page from the pyWorkPage. This will build the pyFlowData up to the current step and ignore the future steps. It will be necessary to override the PerformDefaults to pass the new parameter loadNavigationPathForBreadCrumbOnly to GetFlowData to call this new functionality.
SR-B66551 · Issue 317443
Fixed downstream question flow when upstream answer changed
Resolved in Pega Version 7.3.1
Downstream question responses were not getting reset on the form when a complex question (upstream question) response was changed. To fix this and to keep the behavior consistent, the property will be removed from both the survey embedded structure and the property mapping. BuildQuestionStream has been modified to clear the embedded answer value if the display when evaluates to false.
SR-B53918 · Issue 312285
Optimistic locking on resolved case fixed for Back button use
Resolved in Pega Version 7.3.1
It was possible to perform an action on a resolved case when in screen flow, i.e. when in the middle of a screenflow of a case and the case gets resolved due to some action in another case. If Refresh was clicked from the Actions, the case was updated as Resolved-, but clicking on the Back button of the screen flow ignored the Resolved status and allowed changes to be made. The logic to check for stale data (optimistic locking) was missing on the Back button in the screen flow, and has been fixed.
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.
INC-198765 · Issue 696686
Public URL will be appended with "/" if it is not present
Resolved in Pega Version 8.7.1
When using the Worklink Correspondence Fragment rule with authentication service type "prweb/PRAuth/sso", the returned URL did not contain the needed "/" at the end of public link. The "/" was present when using the legacy authentication service "prweb/sso". This has been resolved by updating the system to include a "/" at the end of a public URL if one is not present.
INC-184040 · Issue 688256
Improved accessibility for Disclosable Documents/attach files/auto selection dropdowns
Resolved in Pega Version 8.7.1
When using Dragon for accessibility, issues were seen when trying to select different options in the dropdowns related to attaching multiple files. This was caused by the legacy grids being used not supporting this type of accessibility functionality, and has been resolved by updating pzAttachFileDDFileList to use an optimized table instead.
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.