Pega Customer Service for Communications Hotfixes

The following tables list required hotfixes the Pega® Customer Service for Communications application requires. To request a hotfix, go to your account on My Support Portal. Click +Create and select Request Type > Existing Hotfix Request. Enter and verify the hotfix details and click Submit.

Import each type of hotfix in the listed order during the Pega Customer Service for Communications installation or upgrade:

  • Apply Pega Platform hotfixes immediately after the Pega 7 Platform installation or upgrade.

  • Apply Pega Customer Service for Communications hotfixes just after you complete the application bundle import.

To see hotfix installation details, see the readme that is included in the hotfix.

Pega Customer Service for Communications 7.31

Required Pega Customer Service for Communications 7.31 hotfixes

Pega Platform Version Hotfix Number Observed Behavior
7.3.1 HFix-39843 Issues addressed include:
  • Bots: When the interaction is escalated to the agent, the chat transcript is showing HTML tags and IDs.
  • CRM: Pega Customer Service cases in Sales Automation application does not have a close button.
  • For Timeline, billing composite is not appearing for Opportunity.

Pega Customer Service for Communications 7.22

Required Pega Platform hotfixes required for Pega Customer Service for Communications 7.22

Pega Platform Version Hotfix Number Observed Behavior
7.2.2 HFix-31520 After a update, demonstration popups fail to launch initially and require a second launch.
7.2.2 HFix-32372 A concurrent modification exception is observed for parameterized data pages: "thread.pageExists(aPageName,paramPage)".

Required Pega Customer Service for Communications 7.22 hotfixes

Pega Platform Version Hotfix Number Observed Behavior
7.2.2 HFix-32315
Issues addressed include:
  • In IE11 browsers, scroll bars are observed after launching service cases in WSS.
  • Upgrade icon not working.
  • Changes in billing period are not reflected after billing composite refreshing.
  • Marketing offers are not refreshed after service case closure.
  • Access group authorization failed to access KM related data pages defined at node level.
  • Interaction header improperly displays for Co-Browse and Next Best Action adapter settings.
HFix-34522 The Inbound correspondence request is not created through an email listener.
HFix-40255 Changes are required to support the latest localization changes.

Suggest Edit

Have a question? Get answers now.

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