For any implementation upgrading from 8.5 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.

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.

• Configuring KYC Type applicability