Skip to main content

Module

Perpetual KYC with event-driven architecture

Archived

3 Topics

35 mins

Visible to: All users Applies to: Pega Client Lifecycle Management for Financial Services 8.8
This content is now archived and is no longer updated. Progress is not calculated. Pega Cloud instances are disabled, and badges are no longer awarded. Click here to continue your progress in the latest version.

Customer data changes, ongoing e-screening alerts, and periodic review deadlines are just a few examples of types of events that the application might need to manage. Learn about Perpetual KYC and event-driven architecture (EDA), and how it facilitates the implementation of event-driven processes, consuming events coming from different systems and modules to ensure continuous regulatory compliance.

Beginner
Case Management
Dev/Designer Studio
Financial Services
English

After completing this module, you should be able to:

Describe event-driven architecture.
Articulate how event-driven architecture supports Perpetual KYC.
Design new event types and event-driven processes.

Available in the following missions:

Pega CLM and KYC Release Update v1 Pega CLM and KYC Foundation v3

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice