Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Known issues in version 8.7

Updated on May 14, 2021

This section describes the known issues in this version.

Pega Customer Service Release Notes Pega Customer Service Release Notes Pega Customer Service Release Notes Pega Customer Service Release Notes Pega Customer Service Release Notes Pega Customer Service Release Notes

The following ID reference is used:

  • Reference numbers beginning with “ISSUE ” or “BUG” refer to bugs logged in the Pega issue-tracking system.
  • Reference numbers beginning with “INC-” or “SR-” refer to corresponding Support Requests logged in My Support Portal.
Note: To submit new issues or find out more about known issues, or to request a hotfix, go to the Pega Product Support Community. Look up or subscribe to your Support Requests (INCs) in My Support Portal. Ensure that you refer to the issue ID in all communications.

Pega Customer Service known issues

Pega Customer Service 8.7 has the following known issues:

Issue IDTitle and DescriptionSuggested Resolution
ISSUE 646680The New Application Wizard creates classes for interaction channels that were not selected by the operator.None.
ISSUE 677414Customer timeline does not show any events when an operator enables the Customer Inquiry feature in the Customer composite. Disable the Customer Inquiry feature to view the Customer timeline events.
ISSUE 678217Operators receive a guardrail warning for case types that were created from a case type template in version 8.6 or earlier due to a deprecated When rule.No action is needed. The affected case types will continue to work, and the warning has no impact on the functionality of the case types.
ISSUE 688017In the chat and messaging feature of Pega Customer Service version 8.7, czConversationID property is optimized in the PegaCA-Work-Interaction class, and the corresponding table name is pegadata.pca_work. So, the same property must be optimized in customer implementation classes and corresponding vertical classes.None.
ISSUE 689471If using the Google Chrome browser, the Interaction Portal has a memory leak of approximately 1MB per interaction. To ensure that the memory leak does not degrade application performance over time, CSRs should log out after their work shift. Alternatively, CSRs can use a different browser until the issue is resolved in a future patch release.
ISSUE 690104The platform does not perform input validation or output encoding of user input on Search and Pulse components. Possible risks include modifications to the application appearance, injection attack, or a redirect.Use a content security policy (CSP) to block the unintended URLs.
ISSUE 692644The Collections widget does not update when there is a change in the Collections status.None.
ISSUE 719976Upgrades from Pega Customer Service patch 8.3 on MSSQL fail with column name mismatch.This failure applies only to systems with Pega Customer Service 8.5.x or later patch releases. The capitalization for the column name pa_account.Productid is incorrect; the correct capitalization is productid. To prevent upgrade failures, when upgrading from Pega Customer Service patch release 8.3.x to 8.5.x or later patch releases, run the following command from the Microsoft SQL Server Management Studio (SSMS) to rename the column.

EXEC sp_rename 
'data-schema-name.pa_account.Productid',
'productid', 'COLUMN'
ISSUE 761252Initially, the first message sent from the customer in the long-running status needed to be present on the CSR screen. There were two entries in the D_MCPInteraction data page for the first message, and the response structure changed. So, a condition was added in the Pega Customer Service (CS) layer to honor the changed response structure to resolve the missing message issue. However, the duplication of the first message on the CSR screen is persistent.

This issue was identified in the 8.7.4 patch.

None.

Communications known issues

Pega Customer Service for Communications 8.7 has the following known issues:

Issue IDTitle and DescriptionSuggested Resolution
ISSUE 696531In the new customer acquisition flow, if you provided optional information such as first name and last name when creating the prospect, the state and city of the prospect does not display in the search results table.None.
ISSUE 697635In the new Guided internet setup in the mobile self-service flow, the Back button in the troubleshooter and the Close button on the last page do not work. None.

Financial Services known issues

Pega Customer Service for Financial Services 8.7 has the following known issues:

Issue IDTitle and DescriptionSuggested Resolution
ISSUE 697277Case Management Edition only: In the Replace a card case type, if you select a different address for shipping the card, the associated fields do not refresh accordingly.Add a Refresh action set to the country dropdown field in AddDifferentAddress section of the PegaCPMFS-Work-Service-ManageLostOrStolenCard class.
ISSUE 695486Interaction summary and Chat Interaction reports do not work.None.

Healthcare known issues

Pega Customer Service for Healthcare 8.7 has the following known issue:

Issue IDTitle and DescriptionSuggested Resolution
ISSUE 595398

Provider 360: responsiveness issue in low resolution

A section on the Practitioner tab does not break appropriately at low browser resolutions.

Update the template that is used by the HCLicensesInfo section.

Insurance known issues

Pega Customer Service for Insurance 8.7 has the following known issues:

Issue IDTitle and DescriptionSuggested Resolution
ISSUE 628689Conversation Flow Name is distorted in the Conversation Flow Modal.None
ISSUE 633210Interaction Header is missing when we Open a Case from Work.None
ISSUE 637957Unable to modify Research Interaction Composites via App Studio.None
ISSUE 639412URL Tampering seen when the Interation Time is > 30 Minutes.None
ISSUE 645349Create New Contact isn't aligned with the New Search.None
ISSUE 647865Issues related to Conversation Flow creation.None
ISSUE 647876Unable to create Conversation Flow from Data- Class.None

Tags

Pega Customer Service 8.7 Pega Customer Service for Communications 8.7 Pega Customer Service for Financial Services 8.7 Pega Customer Service for Healthcare 8.7 Pega Customer Service for Insurance 8.7

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us