SR-C66639 · Issue 406176
Localization added to "Text" in Themes page
Resolved in Pega Version 8.1.1
The header "Text" in the Themes page was not localized properly due to the field value created in the wrong applies-to class . There is a field value in @baseclass but is in Pega- DecisionArchitect ruleset might not have been considered while exporting rules for translation . Will create another one in @baseclass /Pega-EndUserUI
SR-C67164 · Issue 406358
Operator security bypass now available to multitenancy environments
Resolved in Pega Version 8.1.1
In Pega 8.1, whenever operator records are imported via a RAP file they are disabled by default for the purpose of increased security. When performing this operation there is an option to bypass this feature so that operators are not disabled upon import, but that bypass was not available in multitenancy environments. To allow or that use, this release includes an enhancement to expose a parameter on PegaRULESMove_Zip_To_DB to support bypassing operator security.
SR- · Issue 403102
Links updated for Security Checklist rule documentation
Resolved in Pega Version 8.1.1
The links for the following tasks in the documentation for the Security Checklist rule have been updated: "Secure web.xml"; "Appropriately encrypt data"; and "Define appropriate access control for client personal info subject to regulations like EU GDPR". In addition, the task "Configure Dynamic System Settings for production" has been renamed to"Define appropriate Cross-Site Request Forgery (CSRF) settings" and is linked to the CSRF landing page.
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- · Issue 406436
OIDC and authorization_code flow corrected
Resolved in Pega Version 8.1.1
The OIDC and authorization_code flow was not working work on the first attempt. This was traced to the server that was performing the OAuth 2.0 authorization_code redirecting straight to the Pega application after successful user authentication instead of returning an authorization code via redirect_uri. As a result, the Pega application was rendered in a external Safari window which is supposed to be used for user authentication only. Second and subsequent attempts to perform the OAuth 2.0 authorization_code flow were successful and the Mobile Client was logged in. This was caused by the unnecessary retainment of state parameters in the OIDC flow, and has been fixed by removing the code that appended the querystring parameters used for the Hybrid Client.
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.
INC-167606 · Issue 665869
Updated ConfirmHarness handling for case type creation
Resolved in Pega Version 8.6.2
If a new case type was created with the initialization stage and there were no assignments in the case type, the /cases API did not return a NextPageID in response. This has been resolved by setting the pyConfirmHarness parameter before calling addworkobject.
INC-168368 · Issue 651079
Correct flow actions loaded in multi-thread portal refresh
Resolved in Pega Version 8.6.2
The member authentication screen was displaying an incorrect flow action on doing browser refresh after creating a new interaction. Refresh is a special case where the parameter retention is different across single-threaded & multi-threaded portals alongside the execution order of activities. In this case, this inconsistency occurred in a multi-threaded portal when newAssignPage had the information to load the proper assignment but the parameter indicated an old index. This has been resolved by adding 'when' conditions to to populate and pass the correct references and labels and to honor the Param.TaskIndex set and sent by UI activities so it's retained in case of multi-thread portals.
INC-171842 · Issue 664387
Visible element populated for field value controls
Resolved in Pega Version 8.6.2
When implementing a section which had several labels with visible when conditions, this is not reflected in the DX API Get Assignment View. This has been resolved by adding a visible element.
INC-173068 · Issue 654067
HTML tags escaped in Audit History field values
Resolved in Pega Version 8.6.2
The case narrative section was showing case statuses with encoded special characters such as % or ( ), resulting in entries such as "Status changed to Complete &# 40;approved& #41; !@#$ %^& amp;*&# 40;&# 41;_&# 43;.". This has been resolved by updating the PyMemo field from type Text Input to DisplayAsLiteral for case narrative, which matches the setting for case history.