SR-C82549 · Issue 422848
Check added to getRuleNameFromInsKey to clip version name from rulseset name in the dataflow
Resolved in Pega Version 8.1.4
After changes were pushed to the datasets, dataflows were failing on a DT2 environment with an error related to rule resolution and a failure to find a specific property. The dataflows did not fail on a DT1 environment. Investigation showed that if the ruleset name was empty and the ins key was used to get the rulesetname, a mismatch occurred with the returned value due to the version information being included in the name. To resolve this, when a rule name is retrieved by getRuleNameFromInsKey, the system will check if aObjClass is Rule-RuleSet-Version. If so, the version part will be trimmed.
SR-C83050 · Issue 422978
IE width calculation fixed for imported built-on with dymanic layout
Resolved in Pega Version 8.1.4
After upgrade, the Built On input for the application screen in Designer Studio was not rendering in the Microsoft Internet Explorer 11 browser if dynamic layout was used. This was caused by a browser-specific issue with width calculation for pzDefinition, and code has been added to handle this issue.
SR-C83058 · Issue 424155
Assertion parse rule XML regenerated to resolve data mapping issue
Resolved in Pega Version 8.1.4
The parse-xml rule(NS-366601360 • Assertion) has been regenerated to resolve an assembler issue with mapping data to properties.
SR-C83468 · Issue 424951
Legacy multipart upload support added for very large hotfix catalogs
Resolved in Pega Version 8.1.4
After a package containing 100+ hotfixes was installed, the fixes were not visible in the Hotfix Manager page even though the database status showed them as "Installed". Investigation showed that performing a system scan on the catalog upload was resulting in thread dumps while decoding the request URL due to the control used for catalog upload posting the entire content in form data rather than sending a multi-part request. To unblock this use case for catalogs with huge data, the system has been updated to perform a legacy upload where a form submit is used with content-type as "multipart/form-data" rather than sending the entire data in the request header.
SR-C83615 · Issue 424947
Support added for hiding unwanted category reports
Resolved in Pega Version 8.1.4
After upgrade, a customization used to hide unwanted out-of-the-box category reports was not working. This was due to the pyServiceLevelPerformance and pxSimulations category rules not being included as part of the pyOOTBVisibleInBrowser 'when' rule that is specified for Display in the report browser 'when' setting. These two category rules - pxSimulations and pyServiceLevelPerformance - have now been modified to reference the 'when' rule pyOOTBVisibleInBrowser so categories may be hidden as desired.
SR-C83899 · Issue 421069
Alternate RD added for sub class union that will skip blob open
Resolved in Pega Version 8.1.4
The screen load was taking 4 seconds or more to load when a parent case had 500+ child cases, leading to timeouts and issues with case processing. This was caused by the system performing a database open of all the child work items for building the tree: because different child items are mapped to different work tables, a single RD would not suffice for fetching all child items. This meant a work record was opened and child inskeys grouped into different groups based on table mappings, then the RD was called multiple times to fetch the details. To resolve this and avoid blob open, a report definition that performs a union on all sub classes has now been put in place. Execution is based on a parameter to avoid any backward compatibility issues. This is used by overriding the 'pyPopulateCaseContentsWrapperExtension' data transform and setting param.useOptimizedQuery to 'true' to override the database open.
SR-C84116 · Issue 423757
Added container handling to make optimized grid table visible in action top
Resolved in Pega Version 8.1.4
After upgrade, if the Optimize code checkbox was checked on a table and visibility was applied over grid header, the table was not visible in the UI. This scenario only happened when a grid was upgraded from non-optimized to optimized with some visibility condition added, and was caused by the system not yet supporting the visibility features in action top for an optimized grid. To resolve this at this time, the system has been updated to not honor the visibility at container for an optimized grid so the table will be visible.
SR-C84135 · Issue 424532
Metadatatree updated to be function-scoped in UI to resolve custom tab control display issue
Resolved in Pega Version 8.1.4
When switching rapidly between two custom tabs, especially clicking in and then clicking away before the busy icon could be displayed, the section containing the tab controls was intermittently refusing to display. Refreshing the browser or clicking on the Pega button made the section visible again. This was traced to the template "metadatatree" getting overlapped with subsequent template processing due to a timing issue as "metadatatree" was being maintained in the global window object. To resolve this, "metadatatree" has been updated to be function-scoped in renderUI to avoid timing issues.
SR-C84167 · Issue 422478
Corrected issue with Field Level Auditing re-adding deleted page list items
Resolved in Pega Version 8.1.4
Pressing a Save button that invoked the pyTrackSecurityChanges data transform caused deleted items to be added back to a page list. This was caused by pyPropertyIndex being set on the removed page in RUF-pzAddHistoryMemosForPageList, and has been corrected by removing that unneeded action.
SR-C84384 · Issue 430964
Logoff control for Sales Automation case worker portal updated to clear states
Resolved in Pega Version 8.1.4
After logging in to the Sales Automation case worker portal and clicking a menu item other than dashboard, the link was properly highlighted in the navigation menu and the appropriate data was loaded in the harness. However, after logging out of the application and logging again as the same user, the portal opened to the dashboard page and the previously clicked link was highlighted instead of the dashboard link in the left navigation menu. While it was possible to reset the menu state by closing the browser and starting a new session, the issue has been resolved by updating the logoff control for this portal to use the general system control_logoff which clears states on exit.