Skip to main content


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

Financial Services issues resolved

Updated on May 20, 2021

The following issues are fixed in Pega Customer Service for Financial Services 8.6:

Pega Customer Service Release Notes
Issue IDTitle and Description
ISSUE 542760After completing a Repossession case, if the CSR clicked on the same case label on the driver panel, the Repossession case did not open for review. Instead, the parent Collection case opened for review.
ISSUE 561457In the Report Definition RetrieveCollectionCases, the results were filtered on the out-of-the-box PegaCPMFS-Work-Collection class. The report definition has been updated to filter on the implementation class.
ISSUE 586979Removed the CSLoadInteractionHistory rule override.
ISSUE 590783The launch time performance for service cases has been improved significantly.
ISSUE 595966Overridden case header pyActionLabelDisplaySection sections in different classes of Customer Service for Financial Services were not updated with changes from the Pega Customer Service application. While overridden case headers in PegaCPMFS-Work and PegaCPMFS-Work-Service classes were removed, overidden case headers in the PegaCPMFS-Work-Interaction class were updated with recent style changes from the Pega Customer Service application.
ISSUE 606218For some cases, clicking Submit hangs the screen.
ISSUE 619564The czSwitchDestination rule was not optimized to the work pool tables.
ISSUE 642176The czResponseType rule was not optimized in the CPMFS work class.
ISSUE 647630The Outbound Email interactions were not appearing in the Account tab interactions.

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