SR-D38450 · Issue 505656
Added workaround to handle HiddenPropertiesToIgnore when a page is in Read Only mode
Resolved in Pega Version 8.2.4
A 'WrongModeException' was generated while trying to use the Data Transform pxHiddenPropertiesToIgnore to remove system properties from page. When the Datapage was set to Editable/Savable mode, the Activity ran without an error and executed the Data transform. When the Datapage was in Read only mode, the error occurred. This was traced to a process that previously was allowed to set a page to an empty string, but which was removed during recent work. To resolve this, four instances of pxHiddenPropertiesToIgnore that included Single Page Value properties have been updated by moving them to the bottom of the Data Page and changing them to an "Update Page" from a "Set".
SR-B51204 · Issue 309685
Cassandra enhancement to retrieve multiple records and use runinparallel
Resolved in Pega Version 7.3.1
An enhancement has been added to allow the Cassandra Connector GET operation to return multiple rows by querying on clustering keys and/or secondary index. In addition, an issue with Connect-Cassandra not supporting run-in-parallel execution mode has been resolved to allow a result list from list operation to be called from pyoutputpage or primary page.
SR-B64066 · Issue 313310
Cassandra enhancement to retrieve multiple records and use runinparallel
Resolved in Pega Version 7.3.1
An enhancement has been added to allow the Cassandra Connector GET operation to return multiple rows by querying on clustering keys and/or secondary index. In addition, an issue with Connect-Cassandra not supporting run-in-parallel execution mode has been resolved to allow a result list from list operation to be called from pyoutputpage or primary page.
SR-B66961 · Issue 315458
Performance improvements for multiple operators using the same application
Resolved in Pega Version 7.3.1
Performance delays were seen due to static content being processed per each user. This was an issue where each census survey performed by a different operator ID using one of two applications produced two gen_.js files. One was generated at login, the other on submit. Because the variables in pzClientApplicationData were not static for an application, the dynamic static content was being regenerated and created for different users but for the same application. To correct this, the confirm_harness_loaded and pega.d.pyUID properties have been made dynamic so the file will not be regenerated for same application/different user.
SR-D34806 · Issue 506558
Horizontal scroll added to grids using Table Personalization
Resolved in Pega Version 8.2.4
After configuring “optimize code” and “personalization” options on a table which had more than 15 columns, the Optimization option on the table removed the horizontal scroll option from the screen and made some columns unviewable. If “optimize code” was not configured on the table, the horizontal scroll option appeared as expected. This was traced to the grid container not having scroll defined on it, and has been resolved by adding code to make the overflow columns visible.
SR-D35266 · Issue 509481
Check added to postOpenAssignment to support Ajax Container use
Resolved in Pega Version 8.2.4
After configuring an 'OpenAssignment' action on a begin button and giving the target as 'Dynamic Container', it worked as expected to open the assignment in a new tab on the Platform, but did not work from the Customer Service interaction portal. This was traced to the Customer Service portal using MicroDC to display the cases in the work area, which was not within the scope of the Ajax Container. Additional checks have now been added to the postOpenAssignment function to support this use.
SR-D33934 · Issue 503333
Parent case lock properly released when child case is resolved
Resolved in Pega Version 8.2.4
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 506799
Server node cache refresh will use remote execution timeout
Resolved in Pega Version 8.2.4
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.
SR-D42670 · Issue 510183
Force order added to inner join when running a Rules Resolution filter
Resolved in Pega Version 8.2.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 Report Definition, 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.