Configuring a producer system for remote case types
To pass remote case types to another application, configure the system that stores your case types as a producer system. As a result, you provide a framework for case workers to process work from multiple applications without changing context, which promotes efficiency and saves time in your organization.
For example, your system might host Loan requests and Credit card operations applications. You want to publish case types from these applications to a VIP customers operations application so that users can perform work by logging in to this application only. You configure the system with the Loan requests and Credit card operations applications as the producer system first.- Preparing a token profile for remote case types
Token profiles secure data exchange between two parties, such as producer and consumer systems.
- Preparing identity mapping for remote case types
After you prepare the token profile for your producer system, prepare identity mapping to ensure that Pega server correctly identifies operators in your application. You also define how to map the user identity information for use in the Pega application.
- Preparing OAuth 2.0 client registration for remote case types
To ensure that remote application from a consumer system can properly communicate with your producer system, prepare the OAuth 2.0 client registration in your producer system. As a result, you create a secure and reliable connection between your producer and consumer systems.
Previous topic Configuring a consumer system for remote case types Next topic Preparing a token profile for remote case types