PEGA Decisioning - Working with PEGA Decisioning Components

PEGA Strategy Decision Components are the building blocks of decision strategy, they are the language used by the business to express how business wants to go through the strategies.

The Import components bring external data into the decision strategy e.g. data from another strategy, or the propositions to the customer.

Business Rules components apply business rules, such as eligibility requirements.

Decision Analytics components make predictions about the customer, e.g. propensity, or, likelihood to accept an offer.

Enrichment components do calculations, such as a margin calculation based on the price and cost, and the pricing can be dynamic.

Arbitration components filter out propositions that are less relevant for the customer or that a customer is not eligible for.

Selection components allow propositions to be ranked, top offers for a customer can be selected.

Aggregation components allow the calculation of aggregate numbers e.g. telecomms company can calculate monthly usage, or a bank can calculate average monthly account balances to determine a credit card.

Business process kicks off a decision rule or a decision strategy. A Flow Shape is the link between BPM and Decision Mgmt, it can either call a Decision rule or a decision strategy via the Interaction Rule.

 

Run Interaction flow shape invokes a Decision Strategy via the Interaction rule type- it separates the decision strategies from the business processes, allows to swap out strategies without changing the process flow (business users do not rely on technical users to update business process).

From Strategy you can invoke other rule types: Decision Trees or Tables, Scorecards or Adaptive Model, which means that the strategy can invoke rule types that are a part of PRPC or PDM.

 

All of this is supported by PEGA Decisioning Core Services:

Interaction History- keeps a track of communication with a customer

Visual Business Director – preps the data rendered in 3D VBD landing page

Adaptive Decision Manager – live data is gathered and adaptive models are created and linked with a proposition.

NBA is determined by a collection of sub-strategies rather than a single strategy- this is called the “Separation of Concerns” design principle. It enables each sub-strategy to address a separate aspect of how NBA is determined. The result of each sub-strategy feeds into the corresponding component of the higher level strategy and is presented to the agent or a customer via appropriate channel.

In Pega 7 Designer Studio (App Explorer>Process Flow) we build the application, where in the Case Manager portal we can review it.

The results of the strategy can be written to a clipboard where the data can be accessed by BPM and PDM layer of the application.