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.5

Updated on January 13, 2022

The data model and the case structure constructs with the managed related parties are significantly altered and updated to support the advanced use cases. To ensure a smooth transition for the inflight cases, Pega Client Lifecycle Management and KYC provides a solution with an advanced update mechanism that is strategically placed at various points in the lifecycle of the onboarding and due diligence cases. The mechanism ensures that due diligence case structure is retained while the old data model is seamlessly converted to the new one, so that the inflight cases can make use of all the new features that Pega Client Lifecycle Management and KYC provides with the product.

Pega Client Lifecycle Management for Financial Services Implementation Guide

The system encapsulates the logic in the PegaCLMFS-Work.UpgradeData rule and invokes from platform APIs PegaCLMFS-Work.pyUpgradeOnOpen and PegaCLMFS-Work.pyUpgradeOnPerform. The APIs ensure that the system performs an update when any assignment is opened or submitted. In addition, the update module is executed at the following points:

  • Related party cases are resolved and the data such as risk id propagated back up to the contracting party global due diligence cases.
  • Surgical policy update is applied to the inflight cases.
  • Cases are queued for asynchronous processing.

If required, this module can be invoked from any additional invocation points that your implementation may need. The module is also designed with a few extension points that can be specialized to cater to the module's behavior to meet your business needs. If you need to make changes to these extension points, review the following rules.

Rule nameRule typeUsage
PegaCLMFS-Work. UpgradeDataRelatedPartiesTo85_ExtData transformAllows you to execute any additional logic as the related parties are updated to follow the new related party data model.
PegaCLMFS-Work. UpgradeDataFundUnderlyingPrincipalTo85_ExtData transformAllows you to execute any additional logic as the underlying principle of the fund is updated to follow the new related party data model.
PegaCLMFS-Work. UpgradeDataFundWorkPartyTo85_ExtData transformAllows you to execute any additional logic as the fund work party is updated to follow the new related party data model.
PegaCLMFS-Work. UpgradeDataFundsTo85_ExtData transformAllows you to execute any additional logic as the funds are updated to follow the new related party data model.
PegaCLMFS-Work. UpgradeDataTo85_ExtData transformThis is a generic data transform that allows you to configure any additional update logic that you may want to execute at the listed invocation points.

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