Skip to main content


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

Configuring business services

Updated on June 11, 2021

The business service configuration consists of the following three elements that must be put together to enable a business service.

Business service activation
Business services can be turned on and off based on the needs of the Financial Institutions, see Business service activation.
Provider registration
Some business services require a default data provider registration that can be used during the invocation to business service, see Default provider registration and Dynamic provider registration chapters.
Demo simulator
The data providers natively supported by the application have simulators that can be activated for testing and demo purposes, see Provider demo simulators.

To complete the business service invocation, met every condition on the following list:

  • The business service is active.
  • The provider is configured for the business service.
  • The integration component for the provider is installed, or its simulator is activated.

Business service activation

The first step to activate given business services is to configure a general switch that enables or disables the invocation to the service from the process. To implement the switch, use a Dynamic system setting with a name built according to the following standard: PegaFS fs/services/<business-service>/enable=true|false

For example, if you need to activate the invocation to eScreening from your process, set the Dynamic system setting accordingly: PegaFS fs/services/eEnrichment/enable with the true value.

If multiple Pega FS applications reside in the same server, configure the activation of the service at the application level to avoid any impact on other applications that your change of configuration might bring. For example, to enable the eEnrichment functionality for Pega Client Lifecycle Management and KYC, create a Dynamic system setting with a name: PegaCLMFS clmfs/services/eEnrichment/enable=true|false.

For the names given to the Dynamic System Settings of each specific business services, see Configuring supported data providers.

Default provider registration

After the business service is active, a default external data provider in the business service must be configured. You can choose for explicitly passing of applications the name of the provider based on certain case data (for example, use one provider for customers of type individual and another one for organizations). If the provider is not explicitly mentioned during the invocation to the business service, the system uses the name of the provider set by default for that service.

The configuration of the default providers for given business service is implemented in a very similar manner to its activation by using a Dynamic system setting built according to the following standard: PegaFS fs/services/<business-service>/Provider=<provider-name>

For example, if you need to register Equifax as the default data provider for electronic ID verification, create a Dynamic System Setting with the following name: PegaFS fs/services/eIDVerify/Provider with the EQ value.

For the activation, the configuration of providers can also be set at the application level. The same configuration for Equifax can be done only for Pega Client Lifecycle Management and KYC by using the following Dynamic system setting name: PegaCLMFS clmfs/services/eIDVerify/Provider with the EQ value.

For the names given to the Dynamic System Settings of each specific business services, see Configuring supported data providers.

Dynamic provider registration

Applications may have more complex use cases where the name of the provider must be determined at run time based on a case or application data. For example, implement certain business service for customers of type individual by using a data provider, while a different data provider must take care of those of type organization.

To cater for these complex user cases, Pega Client Lifecycle Management and KYC provides a set of the following extension points that Financial Institutions can override to implement their logic and bypass the default provider configuration.

For more information about extension points, see Configuring supported data providers.

Provider demo simulators

For testing or demoing purposes, sometimes it is desired to run the business service even if the external data provider is not available. Pega Foundation for Financial Services provides a set of basic simulators for the natively supported Business services. The simulators can be switch on or off using the following Dynamic System Settings.

The simulators can be switched on or off using Dynamic system setting. For more information, see Configuring supported data providers.

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us