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

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 upgrade when any assignment is opened or submitted. In addition, the upgrade 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.

• Managing related parties