SR-123008 · Issue 185492
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.
SR-123011 · Issue 182646
Added null check for datetime in SOAP
Resolved in Pega Version 7.1.8
Some SOAP services using a Response Parameter with Data Type of DateTime and for services of type RPC/ literal were generating an NPE when the service was executed outside Pega7 using Google Chrome. Running the service directly from the service rule within Pega7 did not encounter this error. Other SOAP requests returned a date of 1970-01-01. This was traced to a check to get the thread which did not handle situations where PRDateFormat.formatXSDDateTime() could be null, and the handling for that case has been added for this browser.
SR-123018 · Issue 183818
Addressed ruleset integrations problems using Google Chrome
Resolved in Pega Version 7.1.8
When using Google Chrome and running the Integration > Tools > Rule-From-File wizard, the ruleset version was not displayed and it was not possible to proceed past the screen that requires values for rule name, ruleset, ruleset version and class name. This was due to there not being an input field for RuleSet Version, and the validation of that step in the wizard fails. This issue occurred due to Google Chrome not supporting the use of document.all in the HTML code, leading to an undefined value for the JavaScript. This has been resolved by changes to the HTML to make it browser code independent.
SR-123044 · Issue 182684
Improved failure handling for cache loading on startup
Resolved in Pega Version 7.1.8
During server startup after upgrade, a data page with a failed definition cache prevented all remaining data page definitions from loading into the cache. This was found to be caused by a Node scoped data page which had only shared rule sets and did not have at least one production ruleset. In order to smooth startup, the declarative data page definition cache load will skip one particular improper record if found and continue processing.
SR-123051 · Issue 182680
LogOut' function corrected in the out-of-the-box operator menu
Resolved in Pega Version 7.1.8
When using the out-of-the-box provided "pyCaseMgrOperatorMenu" navigation rule, the menu contains two items - 'Preference's and 'LogOut'. Clicking on 'Log Out' was not performing log out operation. This was an error in the logout item of the navigation rule PYCASEMGROPERATORMENU, which was using an old script. This has been replaced with the new out-of-the-box logoff action.
SR-123056 · Issue 186144
FCM IAC caching improvements
Resolved in Pega Version 7.1.8
Analysis on the web server access logs found that content such as JS, image, and CSS files are cached correctly when accessing PRPC directly but not cached at all on the client when the same case is opened via the FCM IAC Gateway. This caused network congestion for the browser. To resolve this, the system now removes the appending forward slash from the thread name in the finalizeNavURL method when the request is issued to a gateway, allowing the download of the static content based on the application instead of the thread name.
SR-123056 · Issue 185070
FCM IAC caching improvements
Resolved in Pega Version 7.1.8
Analysis on the web server access logs found that content such as JS, image, and CSS files are cached correctly when accessing PRPC directly but not cached at all on the client when the same case is opened via the FCM IAC Gateway. This caused network congestion for the browser. To resolve this, the system now removes the appending forward slash from the thread name in the finalizeNavURL method when the request is issued to a gateway, allowing the download of the static content based on the application instead of the thread name.
SR-123106 · Issue 188198
Scroll bar corrected in tabbed work areas with tree grids
Resolved in Pega Version 7.1.8
If a section with tree grid is configured in a tabbed Work Area and has a vertical scroll bar, expanding the node of the tree grid caused the scroll bar to disappear. Clicking on the same node brought the vertical scroll bar back. The issue was in the resizeCallback function of the PegaCompositeGadgetMgr JS file. The overflowY attribute of the workarea gadget div has been set to 'auto' to avoid this behavior.
SR-123127 · Issue 185219
Improve error handling for File Listener
Resolved in Pega Version 7.1.8
The File Listener not processing all files successfully when there was more than one file to be processed. This was caused by missing logic for the clearing of 'hasOnce' at the file level for the record type. Since 'hasonce' was not cleared at file level, once a file with an incorrect configuration is processed, others files were also getting processed as errors. This has been resolved by adding code to reset the 'hasonce' on a per file basis so File Listener is able to process multiple files.
SR-123130 · Issue 184202
Added apostrophe handling for navigation rule item names
Resolved in Pega Version 7.1.8
If an apostrophe (') was present in the label of Navigation rule item name, the onclick functionality of menu option was not working and threw a JavaScript error. In this JS file, the eval(strAction) function call failed because strAction text contains all the parameters enclosed in single quotes: if the label contains an apostrophe, that became an extra quote in this text. To avoid this, the functions pzMenuBarTranslator and pzActionShowHarness have been modified to handle extra apostrophes passed by the label.