Skip to main content

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

Upgrading from 8.2 or earlier versions

Updated on May 25, 2021

Any KYC type created in KYC version 8.3 or prior will be automatically migrated to use the supporting evidence feature. During the migration, all the KYC questions that were configured to use the supporting documents are automatically updated to use the new Supporting evidence feature.

The system supports the following two approaches to migration:

Design Time
With this approach, the migration is performed for a KYC type when it is copied from an older version of the engine to Pega Know Your Customer for Financial Services 8.5 or higher. This ensures that a KYC Type uses supporting evidence in both the form of a rule and in the case.
Runtime Migration
With this approach, the KYC types rule instances do not need to be re-saved, but, instead, their run-time copies are migrated as they are applied to the case. This approach ensures that all the newly created cases use Supporting Evidence in a uniform way. However, this approach does not guarantee uniformity of the KYC rules at design time.

If your business demands uniformity of the KYC type rule instances, then you can migrate all the KYC types by re-saving them all in a higher ruleset version.

After a KYC type has been updated to use the Customer Documents handler, the data that could have been collected before 8.4 for that KYC Type will be automatically migrated at the time of initializing new KYC cases. The system will automatically change the supporting documents into supporting evidence, and ensure seamless reuse of the data.

Any open cases that use the older version of the KYC types will continue to use supporting documents, unless they are updated using the Surgical policy updates feature.

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