By default, Pega Client Lifecycle Management for Financial Services provides the connection to the component. If your application needs to directly connect to any of them, you must use the automatic detection mechanism to avoid issues when the components are not in the application stack.
The system detects the presence of components in the stack using when rules. Pega
Foundation for Financial Services is required in order to use the components. Each
component has two associated when rules, one at Pega Foundation for Financial Services
level and an override of that rule at the component level. The rule in the component
layer is set to return a boolean value
true (the component is present),
whereas the rule present in the Pega Foundation for Financial Services layer returns a
false (the component is not present).
When a component is linked to the application, its associated rulesets are put directly
above the Pega Foundation for Financial Services rulesets for rule resolution. When the
system detects the component, it selects the when rule at the component, therefore
confirming its presence. If the component is not in the stack, the system selects the
when rule (with a value of
false) at the Pega Foundation for Financial
Services layer and the application will not use the component services.
Customers with applications that have logic strongly coupled to the rules of the components should make use of the rules below. They should invoke them before invoking to the component-related logic to avoid issues at run time due to the absence of the component in the stack.