SR-D33934 · Issue 503334
Parent case lock properly released when child case is resolved
Resolved in Pega Version 8.3.1
After creating Parent-Child casetypes with default locking where the child case had the “Allow access to parent” check box checked, the temporary lock acquired on the parent during resolution of the child case was not released afterwards. If “Allow access to parent” was not checked, then the locks were released on both the parent and the child. This was traced to a combination of parameters used by the openIfStale() API where aUnlockOnCommit could be set to false despite the provided locking strategy expecting it to be true, as well as honoring UnlockOnCommit when maintainLockingStrategy is false. To resolve this, the system has been updated to always check whether the lock is available in the map already and if it is, then set unlockonCommit to true. Otherwise, under all cases, honor the passed-in unlockOnCommit value.
SR-D37945 · Issue 506798
Server node cache refresh will use remote execution timeout
Resolved in Pega Version 8.3.1
A campaign was failing due to VBD remote ping timeout with a stacktrace that indicated a StageException. Investigation showed that when the cluster is heavily loaded, calls to the remote execution API could time out. If this occurred when the VBD client was refreshing its cache of VBD server nodes, then the insert failed and the error was propagated up the calling data flow. To resolve this, the system will use the remote execution timeout when refreshing node cache, extend the timeout to 60 seconds, and ensure timeouts are retried during inserts.
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-190130 · Issue 678541
Help information updated for using Elastic Search with Report Definition
Resolved in Pega Version 8.7
The support article "Configuring a report definition to run against an Elasticsearch index" has been updated to clarify that the search can pass multiple values with a space in pySearchString as it does OR operation on all the fields, and that filters in the report definition will be used when executing the report directly or when calling the report in the pxRetrieveSearchData activity. https://community.pega.com/knowledgebase/articles/system-administration/85/configuring-report-definition-run-against-elasticsearch-index
SR-A20018 · Issue 250581
Drill down fixed for use with "Do not display group headings"
Resolved in Pega Version 7.2.2
When the "Do not display group headings" setting in report viewer tab was checked in a report, drilldown did not work correctly for summarized reports that do not display group headings. This was an issue with attributes not being set for the drilldown to work with aggregate columns, and has been resolved.
SR-A20018 · Issue 250155
Drill down fixed for use with "Do not display group headings"
Resolved in Pega Version 7.2.2
When the "Do not display group headings" setting in report viewer tab was checked in a report, drilldown did not work correctly for summarized reports that do not display group headings. This was an issue with attributes not being set for the drilldown to work with aggregate columns, and has been resolved.
SR-A76586 · Issue 256002
Guardrail updated for Report Definitions using Data Page for filter
Resolved in Pega Version 7.2.2
It is possible to configure a report definition to use a Data Page in the Filter/Criteria field (such as pxObjClass Contains D_ABC.PropValue) and not be prompted to list the Data Page on the Pages & Classes Tab, but when it is not listed on this Tab the query uses a literal value as opposed to a dynamic reference. In order to ensure expected results, a check has been added to fully identify invalid page prefixes and an Informational guardrail for Functionality will appear.
SR-D42159 · Issue 508939
Large report pagination should use "Previous and Next only"
Resolved in Pega Version 8.3.1
Some Report Definitions were getting timed out or facing gateway exceptions, primarily due to high time consumed by the DB Queries. Investigation showed the total result count process appeared to stop at the configured pyMaxRecords value as long as it was nonzero. This indicated the issue was related to changes made to fix the inaccurate behavior of the "Last" button in the responsive paginator which included removing logic that set pyMaxRecords to anything other than zero. To resolve this issue, those pagination changes have been reverted. The "Last" button should not be used when the paging mode is set to Numeric: in the case of large reports, the paging option should be set to "Previous and Next only".
SR-A91682 · Issue 261408
Repeat grid properly refreshed with add icon when no rows to display
Resolved in Pega Version 7.2.2
The repeat grid was not getting refreshed when the add icon was clicked. Analysis showed that when "Do not display grid header when there are no rows to display" was checked in the repeat grid property panel presentation tab, the grid 'no results' div was placed outside of the grid content div. This caused removeGridNoResultsMsg to fail and the toggleGridStylesForNoResultsCase function was never called after loading the new row. To fix this, the pega_ui_grid JS removeGridNoResultsMsg function has been modified to call the toggleGridStylesForNoResultsCase function when bHideGridHdrWhenNoRows is true.
SR-A91682 · Issue 260252
Repeat grid properly refreshed with add icon when no rows to display
Resolved in Pega Version 7.2.2
The repeat grid was not getting refreshed when the add icon was clicked. Analysis showed that when "Do not display grid header when there are no rows to display" was checked in the repeat grid property panel presentation tab, the grid 'no results' div was placed outside of the grid content div. This caused removeGridNoResultsMsg to fail and the toggleGridStylesForNoResultsCase function was never called after loading the new row. To fix this, the pega_ui_grid JS removeGridNoResultsMsg function has been modified to call the toggleGridStylesForNoResultsCase function when bHideGridHdrWhenNoRows is true.