SR-D33227 · Issue 510826
Check added for lock expiration when using Save for Default locking
Resolved in Pega Version 8.4
With the default case locking policy, during the process from creating a Case Object to Submit it was possible for multiple users to edit and save the same work object if the lock expired for the original user. No warnings appeared. To resolve this, handling has been added for a lock expiration scenario: previously, Save for Default locking was not considered. This has now been updated with a check that will evaluate whether or not the lock is gone before attempting to save.
SR-D33359 · Issue 505774
SelectAll properly applied to only the page selected
Resolved in Pega Version 8.4
In repeating grid, applying SelectAll on one page resulted in it being applied to the next page as well even though all records in the other page were not selected. Investigation showed that on change, the 'when' condition added to refresh the list was always false. To resolve this, the condition in section pzBulkProcessingCheckbox which refreshes the list once the checkbox is changed has been removed.
SR-D36636 · Issue 503462
Check added to resolve WrongModeException in Work-.Reassign
Resolved in Pega Version 8.4
An agent was failing due to a WrongModeException specific to the out-of-the-box activity "Work-.Reassign". Investigation showed that in the activity "Work-.Reassign" step no 15, there was an assumption that if the property pxFlow existed then newAssignPage.pxFlowName must also exist: if it didn't, invalid pages were created in pyWorkpage.pxflow. To resolve this, a check for the existence of newAssignPage.pxFlowName has been added.
SR-D38306 · Issue 507992
Deleted operator details stored in history table
Resolved in Pega Version 8.4
Pegaunit automation has been added for the pxAddHistoryToTempObject activity to allow the retrieval of detailed operator records in the pr_history_data table.
SR-D40053 · Issue 517528
GetNextWork will use pyID to create unique thread name
Resolved in Pega Version 8.4
After creating three cases, for example D-1, D-2 and D-3 in application 'App1', and then moving to application 'App2' using Switch Application, the GetNextWork function was displaying unexpected behavior. Clicking on 'get next work' three times picked up the three cases (D-1, D-2, D-3) as expected, but when a case was closed manually the last case's lock was removed from the table. For example, closing D-2 manually resulted in the lock instance for the last case ID (D-3) being removed instead of D-2. This was traced to the Get Next Work API creating the thread with the access group name, which meant that if multiple assignments were accessed through 'get next work' it was always cleaning the already opened assignment threads and only the last assignment thread was available. To resolve this, Instead of creating the thread name with accessgroupname, the system will use the work object's pyID to create the thread using a unique key.
SR-D43173 · Issue 508612
Filter logic updated for Warning Summary guardrail report
Resolved in Pega Version 8.4
After scheduling a Guardrail report for Warning Summary, the warning summary reports received in email were blank irrespective of the filter criteria. The logic filters have been modified to resolve this issue.
SR-D43397 · Issue 510331
Force order added to inner join when running a Rules Resolution filter
Resolved in Pega Version 8.4
After upgrade, D_getResolvedWorkStatuses was not loading properly due to a Report Definition that used a Filter by Rule Resolution option timing out on the SQL Server. When the Filter by Rule Resolution option is selected in RD, it will generate a rule resolution query with an inner join which can cause a time out on the SQL Server while it tries to find out the join order for tables with multiple joins. To resolve this, the SQL server will provide a Force order, merge inner join hint option by way of an added DSS reporting/useForceOrderHint. Additionally, reporting/useMergeHintForRRquery should be set on Pega-Reporting to set things up for using the Merge Inner join hint in the query.
SR-D43627 · Issue 509801
Keyboard tab support added added for Focus on Date control
Resolved in Pega Version 8.4
It was not possible to use the Tab key to move to a section with date control to launch it, and hitting enter when on a calendar did not open it. To resolve these, tabindex has been added for date/time focus and the calendar will open on enter.
SR-D44215 · Issue 512192
Navigation Breadcrumb honors pyDisplay in navigation link subflows
Resolved in Pega Version 8.4
After configuring a sub process (screen flow) inside a screen flow connected by a decision shape having a fork condition, the Navigation breadcrumb for this subprocess was always visible irrespective of the connector when condition. This was traced to pyDisplay not being considered for subflows while building navigation links, and has been resolved.
SR-D50350 · Issue 519077
Added keydown event handler for JAWS use
Resolved in Pega Version 8.4
Clicking the "Select file(s)" button worked for mouse and keyboard users but did not work when a screen reader was used. Investigation showed that Keydown events were not firing while the JAWS screen reader was running. Since the screen reader was prompting a space key press to activate, an event keycode for space has been added in the pzMultiFilePath control for Select file button to resolve this issue. In addition, a role application has been added for a button to fire keydown events while running the JAWS screen reader.