SR-C57557 · Issue 402906
Work Object lock released correctly when modal dialogue is canceled
Resolved in Pega Version 8.1.1
The Work Object lock was not being released when the modal dialogue cancel button was clicked. This was due to the primary page not being switched to the pyWorkPage during the cancel, and has been fixed.
SR-C50284 · Issue 402874
Top level activity steps are numbered correctly when child steps exist
Resolved in Pega Version 8.1.1
Top level activity steps were showing as being numbered incorrectly when child steps existed, but saving the rule or refreshing the rule corrected the numbering. This was caused by CSS that was added to the rule form harness to increment the step number; while expanding a top level node the reset happened and then the counter initialized the value. To address this, the code has been changed from CSS counter to CSS attr which will use the index attribute of the current row. Additional CSS cleanups were also done to remove IE9 and other browser-specific styling that is no longer needed.
SR-C53680 · Issue 402914
Filter value Autocomplete uses localized text for the 'Case Type' string
Resolved in Pega Version 8.1.1
The Filter value autocomplete field of the Case Manager portal bulk action landing page was not working as expected while using the Japanese locale setting. If the locale setting was English or empty, the filter value was displayed correctly in the autocomplete. This was an issue with comparisons being hard-coded to use the literal text string 'Case Type', which was failing in localization. To fix this, a 'when' rule has been added to compare localized text against pyFilterName and use it in the appropriate rules.
SR-C57025 · Issue 402913
Filter value Autocomplete uses localized text for the 'Case Type' string
Resolved in Pega Version 8.1.1
The Filter value autocomplete field of the Case Manager portal bulk action landing page was not working as expected while using the Japanese locale setting. If the locale setting was English or empty, the filter value was displayed correctly in the autocomplete. This was an issue with comparisons being hard-coded to use the literal text string 'Case Type', which was failing in localization. To fix this, a 'when' rule has been added to compare localized text against pyFilterName and use it in the appropriate rules.
SR- · Issue 404593
Thread name implementation fixed for FCM use with micro DC
Resolved in Pega Version 8.1.1
When attempting to invoke a remote case in the Interaction Manager portal via FCM with the Customer Service for Insurance application which uses micro DC, the case was not invoked and an empty screen was displayed. Invoking the case from the interaction portal resulted in a JavaScript error. Invoking the case from a WSS or directly from the Create button in Designer Studio worked correctly. This was traced to a recent change to the implementation for generating the thread name. Because of this, CRM apps could not load the Federated cases via micro DC. This has been fixed through changes in "pzFCMMashupGadget" to replace the slash with underscore for the FCM thread.
SR-C60612 · Issue 402878
Modified "What's New" widget to remove use of webGL and improve browser performance
Resolved in Pega Version 8.1.1
The "What's New" widget on the Designer Studio home page was using WebGL to render its background animation. If the browser was running on a virtual machine without hardware acceleration, this widget could cause the browser to become unresponsive. While there was a workaround of using the 'Click the Hide this until next release' button to remove the widget for subsequent logins, the "What's New" function has now been modified to not use webGL.
SR-C54754 · Issue 402915
Work by Work Queue modified to use RD in place of deprecated list view
Resolved in Pega Version 8.1.1
When the "Find" button was selected in Designer Studio >> Case Management >> Tools >> MyWork >> Work by Work Queue, a series of dotted lines that exceeded the section limitation appeared. This was traced to the use of the deprecated function List-view in workbasketlistPopup. In order to support the needed display, the Pega-Landing.pzProcessAndCaseRulesMainMenu Navigation rule has been modified to call a report definition Assign-WorkBasket.pyASSIGNMENTSFORWORKBASKET instead of the deprecated list view. While there is a small difference in user experience and behavior, all the columns being fetched and filters being added will be similar to that of the ones previously seen in the list view.
SR-C51952 · Issue 402949
Admin user flag correctly passed from Dual user when falling back to the legacy connection manager
Resolved in Pega Version 8.1.1
When using Dual user configuration with the Base user running Pega, creating a Data Type with a Local Source and then changing the database to CustomerData resulted in an exception citing "insufficient privileges" while trying to save. This was traced to the flag indicating whether the request was coming from an admin user not being passed through ConnectionBrokerAdapter if the system has to fall back to use the legacy connection manager. This was a missed use case which has now been fixed.
SR- · Issue 402877
Merge Wizard errors fixed, and created rules will use the highest ruleset version available
Resolved in Pega Version 8.1.1
Code errors in the Merge Wizard that were causing Null Pointer Exception errors have been fixed, In addition, branch rule sets created through this wizard did not have the 'Application validation' option and rule set pre-requisite filled automatically; the system has been updated so the version prerequisite will be the highest existing ruleset version in the ruleset.
SR-C46537 · Issue 402866
Code added to format location header for redirect response in IE
Resolved in Pega Version 8.1.1
When using Internet Explorer, authentication was working but the portal did not load. This was traced to IE mandating the presence of a location header in the response: an HTTP 303 "See Other Response" was being returned along with the initial portal HTML payload, but recent modifications to SAML 2.0 to use the PRAuth Servlet were missing this specific redirect case. To resolve this, generic code has been inserted that adds the location header in all redirect cases.