Skip to main content

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

Updating from a previous version to 8.7 version

Updated on January 13, 2022

For any implementation updating from 8.6 or earlier version, the application default to using the Standard due diligence case orchestration mode with the Standard Filtering applicability mechanism for KYC types. All the case orchestration and the KYC type applicability continue to work without any additional efforts.

Pega Client Lifecycle Management for Financial Services Implementation Guide

The application provides a new case type, Tax (PegaCLMFS-Work-Tax), to support the new intermediate case orchestration mode. This new case type is configured as a child case to the Client lifecycle management case-type. To ensure seamless support for the intermediate mode you must perform the following two steps:

  1. Create a Tax case at implementation layer and register the new case class in DCR. For more information on registering a new case class, see Override the application extension data transform.
  2. Modify the Client lifecycle management case-type at your implementation to have this newly added class as subtype and add the PropagateDataToTax data propagation rule.

The case orchestration modes are backward compatible, and you can choose to use any of the new case orchestration modes at any time. The system ensures that change in the case orchestration mode takes effect only for the newly created cases and that all the inflight cases from your previous version retain the case structure created with the cases. However, ensure that the applicability of the KYC types is adjusted based on the mode that you select.

Though the Standard Filtering applicability mechanism continues to work after the upgrade, rewriting the applicability logic using the new KYC Applicability Matrix leverages all the previously stated benefits of a comprehensive view, easier maintenance, and increased performance benefits.

Note: As you update and the Client lifecycle management case-type in your implementation layer, the system automatically copies the associated stage rules from the PegaCLMFS-Work-CLM class to the corresponding implementation class. However, the new copies of the stage rules in the implementation layer can mask their specialized versions from the child classes in the product. Hence, you must review the stage rules in the product in the classes that extend from PegaCLMFS-Work-CLM and manually copy all the stage rules to the corresponding implementation layer classes.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us