SR-D55161 · Issue 527652
getStoreDataTable updated to resolve thread lock issues
Resolved in Pega Version 8.4
An IlegalMonitorStateException in TableInformationMapImpl.getDataStoreTableInfo caused a read lock to not be released, preventing other threads from acquiring a ReentrantReadWriteLock.WriteLock on the same ReentrantReadWriteLock. This eventually lead to a Deadlock scenario forcing other threads into an irrecoverable WAITING state. The issue could be cleared by restarting the nodes, but the implementation of the getDataStoreTableInfo method has been updated to resolve this issue.
SR-D64220 · Issue 535133
Reinitializing Full Text Search will shut down Elastic Search regardless of search initialization status
Resolved in Pega Version 8.4
Pega search was only sporadically working after converting from standard sandbox-marketing to largesandbox-marketing. This was traced to the Full-Text Search initialization having failed on the app-tier node during re-initialization. As part of re-initialization, the existing node is shut down and the Elastic Search node is started. The shutdown process relied on a boolean flag which indicated if the current status of full-text search initialization was successful. In this case, ES was trying to validate all the cluster level settings, for every save of one of the cluster level settings, but could not due to topology changes in the Util Tier node. The boolean flag indicated initialization had failed so the shutdown process was not invoked, yet the system was attempting to start the second instance of an ES node on the same machine. To resolve this, the shutdown FTS code has been modified to shutdown ES regardless of the search initialization status.
SR-D65944 · Issue 533395
Parent case lock properly released when child case is resolved
Resolved in Pega Version 8.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-C78603 · Issue 417128
Expression Builder will flag local variables
Resolved in Pega Version 8.4
An enhancement has been added to Expression builder which will display a warning in the test panel evaluation if there are any local variables in the given expression.
SR-D16433 · Issue 499297
Exception handling added for upgraded custom decision tables
Resolved in Pega Version 8.4
After upgrade, the status fail message "There has been an issue; please consult your system administrator" appeared with a blue screen in the Run window when attempting to run a Decision table from Actions-> Run option. This impacted the ability to create unit test cases. Analysis showed the issue occurred for any decision table where "Evaluate All rows" was enabled and list properties were used in Actions if there was no value for the list property after the execution of decision table. This was traced to a NullPointerException in a RunRuleFromPage activity in a customized in PUnit ruleset, and was caused by having list properties in the actions of a decision table that had not been populated during rule execution. Exception handling has been added to resolve this.
SR-D18726 · Issue 501390
Application quality page retains info on reopen
Resolved in Pega Version 8.4
When the application quality page was accessed for the first time the page displayed all the data properly, but if it was closed and then opened again all the counts were blank. This was traced to an issue with converting the date from the client to the database, and was seen when the Oracle database had date filed as key and type date. The issue did not occur if the type was varchar2. To resolve this, the system will use obj-open-by-handle instead of obj-open while fetching the details of AQD.
SR-D26334 · Issue 495322
Restore delegated rules short description header
Resolved in Pega Version 8.4
For delegated rules like SLA/Correspondence, the short description was not getting displayed in the header. This was an unintended side effect of work done on automation rule capabilities, and has been resolved by restoring the layout visibility condition pzDelegateHeader in pzRuleFormKeysAndDescription.
SR-D27041 · Issue 499048
Manual value group addition support available
Resolved in Pega Version 8.4
In a test case created for a data transform containing a value group property, that value group property could be added by clicking the + sign in the left pane of the test case, but a value group property could not be added manually by clicking the add row button. This has been resolved by adding support for manually adding value list/value groups. The activity steps which were using @java function have also now been replaced with a getproperty function.
SR-D32035 · Issue 504706
Save Button for Delegated rules is displayed correctly
Resolved in Pega Version 8.4
The save button for delegated rules was displayed in a truncated shape. This has been corrected by removing the split-left style from all of the buttons that are intended to be standalone and not have a drop-down actions menu.
SR-D38450 · Issue 505657
Added workaround to handle HiddenPropertiesToIgnore when a page is in Read Only mode
Resolved in Pega Version 8.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".