SR-122820 · Issue 177433
Passivation thread logic improved
Resolved in Pega Version 7.1.8
It was noticed that the passivation daemon was triggering thread dumps several times a day, affecting performance and disk space. This was caused by threads in the process of being passivated inaccurately being reported as long-running. This has been corrected by changing the long-running thread detection to recognize threads in the process of passivation, and to bypass them unless there is a long-running passivation problem.
SR-122820 · Issue 182133
Passivation thread logic improved
Resolved in Pega Version 7.1.8
It was noticed that the passivation daemon was triggering thread dumps several times a day, affecting performance and disk space. This was caused by threads in the process of being passivated inaccurately being reported as long-running. This has been corrected by changing the long-running thread detection to recognize threads in the process of passivation, and to bypass them unless there is a long-running passivation problem.
SR-122839 · Issue 185954
Audit entries properly suppressed
Resolved in Pega Version 7.1.8
Audit entries were being added to the history even after suppressing the same in the DT "FilterHistory" of the respective interaction class. When the "RemoveAssignmentByTicket" function called the activity "AddWorkHistory", the parameter workPage was not being sent. Because the system skipped the call to the decision tree, it was returned as 'true' each time. To resolve this, the system now passes "WorkObjectPageName" to ensure proper evaluation.
SR-122881 · Issue 184898
Print preview for work objects in a fixed portal no longer truncated
Resolved in Pega Version 7.1.8
Printing a work object opened in a fixed portal was resulting in part of the work object being truncated in the print preview. This issue was traced to a change in the name space of "interceptPrint" method, and has been corrected.
SR-122902 · Issue 182835
Shutdown issue with Tomcat resolved
Resolved in Pega Version 7.1.8
During shutdown, errors were reported on the App Server window. Shutdown did not complete and the App Server Window remained open. This was due to the "Shutdown" button/feature not properly terminating Tomcat. There was a workaround to manually close the Tomcat window, but the DNodeServiceListener has been modified to release all of the threads properly.
SR-122917 · Issue 182299
Resolved error in security change tracking
Resolved in Pega Version 7.1.8
If security change tracking was enabled using a declare trigger with a TrackSecurityChanges activity on the Operator class, adding a Data Transform ChangeTrackModel to track a number of properties on the operator record would create a PropertyIndex property and no further changes could be saved. This occurred in environments using the dynamic system setting "validateonsave" (set to true) which validates the property existence in the class hierarchy, but a validation error occurred on save because "pyPropertyIndex" is in the Embed-ModalParams class which was not accessible to Data-Admin-Operator-ID. To resolve this, the "pyPropertyIndex" has been moved to baseclass.
SR-122923 · Issue 186055
Created DSS for switching to old assembler
Resolved in Pega Version 7.1.8
The error "** FAIL : Unable to apply Rule-Parse-XML instance. WrongMode" while mapping xml data to page list in a parse rule was caused by a gap in the assembler, and has been resolved by creating a Dynamic System Setting with the following: Setting Purpose: switchtooldassembler Value: true Owning Ruleset: Pega-IntegrationEngine.
SR-122982 · Issue 186898
Ensured Excel reports contain fresh data
Resolved in Pega Version 7.1.8
A sporadic issue was found when running multiple reports and exporting them to Excel where new reports sometimes contained data from previously exported results. This was found to be an issue with stale data being left on the TmpExportResultsPageOrig because this page was not listed in the Page-Remove at the end of the RDExportWrapper activity. This has been corrected.
SR-122982 · Issue 185153
Ensured Excel reports contain fresh data
Resolved in Pega Version 7.1.8
A sporadic issue was found when running multiple reports and exporting them to Excel where new reports sometimes contained data from previously exported results. This was found to be an issue with stale data being left on the TmpExportResultsPageOrig because this page was not listed in the Page-Remove at the end of the RDExportWrapper activity. This has been corrected.
SR-123008 · Issue 185497
Improved performance for heavily active ruleset grids
Resolved in Pega Version 7.1.8
Progressive performance issues were seen in environments with frequent rule updates. Memory leaks were found in the grid code, and performance has been enhanced by the following updates: An erroneous global object was removed and the process tuned for nullifying the grid objects. The Section RuleFormLayout rule had the DesignViewInclude section was erroneously included twice: the duplicate has been removed. Issues were resolved in the "openRuleAdvanced," tab support, and dynamic container controls. An event listener has improved handling of load and unload of the menus. Av condition was added in if block checking for styleClass which adds correct number of dots for the case where image source selected is icon class. The Actions split button was consolidated to a single button with a down arrow. The +Create submenu was removed from the actions menu for @baseclass and 3 overrides. The autoAdjustProgressiveGrid was optimized. Handling for Composite Gadget manager was updated.