INC-142589 · Issue 595489
Corrected tooltip evaluation for multiselect
Resolved in Pega Version 8.4.3
After adding help text for a multiselect help icon with overlay on hover field, the value was not being sourced. Changing to a different type of help text or control type worked as expected. This was due to an error in case sensitivity, using pyToolTip when it should have been pyTooltip, and has been corrected.
INC-142714 · Issue 596554
Recent Cases from different applications available to open
Resolved in Pega Version 8.4.3
An enhancement has been added which will allow opening other application assignments in the Recent Cases section of the current application when the user has access to multiple applications.
INC-143005 · Issue 596954
Fluid Overlay displays as expected in Firefox
Resolved in Pega Version 8.4.3
After upgrade, using the Overlay format "Fluid" to perform the screening matches task in CLM using Firefox had an overlay that covered the entire screen but was missing the scrollbar to manage the content. This has been resolved by adding changes to support dynamic content (with scrollbar) for center overlay.
SR-D16427 · Issue 497220
Multi-nodes rebuild LibraryMetadata to ensure all Rule-Utility-Functions are present on change
Resolved in Pega Version 8.3.1
When performing a complete Application import into a clean installation, references to certain Rule-Utility-Functions went unresolved during the initial assembly. Investigation showed that after introducing a new Rule-Utility-Library or Rule-Utility-Function on one node in a cluster and then generating that, the other nodes in the cluster did not have the correct LibraryMetaDataCache for that Rule-Utility-Library. Therefore assemblies on those other nodes could be bad and throw a runtime UnresolvedAssemblyError. This has been resolved by modifying the way the Library subsystem processes the node changes events for Library Generation to ensure that each node completely rebuilds the LibraryMetadata for that Rule-Utility-Library so it contains all the Rule-Utility-Functions.
SR-D32441 · Issue 502572
Multi-nodes rebuild LibraryMetadata to ensure all Rule-Utility-Functions are present on change
Resolved in Pega Version 8.3.1
When performing a complete Application import into a clean installation, references to certain Rule-Utility-Functions went unresolved during the initial assembly. Investigation showed that after introducing a new Rule-Utility-Library or Rule-Utility-Function on one node in a cluster and then generating that, the other nodes in the cluster did not have the correct LibraryMetaDataCache for that Rule-Utility-Library. Therefore assemblies on those other nodes could be bad and throw a runtime UnresolvedAssemblyError. This has been resolved by modifying the way the Library subsystem processes the node changes events for Library Generation to ensure that each node completely rebuilds the LibraryMetadata for that Rule-Utility-Library so it contains all the Rule-Utility-Functions.
SR-D22113 · Issue 498312
Multi-nodes rebuild LibraryMetadata to ensure all Rule-Utility-Functions are present on change
Resolved in Pega Version 8.3.1
When performing a complete Application import into a clean installation, references to certain Rule-Utility-Functions went unresolved during the initial assembly. Investigation showed that after introducing a new Rule-Utility-Library or Rule-Utility-Function on one node in a cluster and then generating that, the other nodes in the cluster did not have the correct LibraryMetaDataCache for that Rule-Utility-Library. Therefore assemblies on those other nodes could be bad and throw a runtime UnresolvedAssemblyError. This has been resolved by modifying the way the Library subsystem processes the node changes events for Library Generation to ensure that each node completely rebuilds the LibraryMetadata for that Rule-Utility-Library so it contains all the Rule-Utility-Functions.
SR-D20439 · Issue 496405
Hotfix hashmap cleanup improved
Resolved in Pega Version 8.1.7
A DL installation failed with an out-of-memory error. It was observed that many CacheEntry(VersionedJdbcJarRwader.java) hashmaps were being created to store the details for each hotfix but that were then never cleared. This has been resolved by adding the finally block in CodeImportProcessImpl.java class to call the shutdown method for proper cleanup. In addition, the default command line utility (prpcUtils) has been updated to use JVM settings of Xmx 4GB and capture a heap dump if an out-of-memory error is encountered. The auto-generated prconfig.xml has also been updated to leverage its minimal startup setting which will avoid loading the conclusion cache into memory.
SR-C49664 · Issue 435310
Updates made for usage validation utility Run report checkbox and buttons
Resolved in Pega Version 8.1.5
The 'Review mode only' checkbox wasn't working for any browser, and the 'Run Report' button wasn't working in IE. This has been resolved by updating the javascript used to invoke the Run Report button to be better integrated with IE, and by adding additional handling to set the ID for the checkbox.
SR-C74677 · Issue 418339
ADM pulse timing changed to inprove performance on very large clusters
Resolved in Pega Version 8.1.5
ADM uses a pulse that checks if any models need to be updated. This uses a Cassandra query which has no "where" clause, causing poor performance for very large clusters. For immediate relief of this issue, the pulse configuration has been updated to increase the timing from 30 to 300 seconds so it fires less often. Model updates typically happen every x hours and often the pulse will not detect any models that would need to be updated. Further improvements in this process will be available in a future release.
SR-C77730 · Issue 437101
Resolved case lock release improved
Resolved in Pega Version 8.1.5
Cases created through the create work object were unnecessarily holding onto locks for up to two hours. This was traced to a defer-write scenario for mobile devices which did not return the correct status needed for "no further assignments". In order to resolve this issue, a new parameter "returnNextActionInfo" of type boolean has been added to svcPerformFlowAction. This parameter will be always set as false when calling this activity from sync up so all locks will be closed and released.