One common design question usually asked by many of our Decisioning Architects is, where should i define my Decision Table? Whether the Decision Table to be defined on the Strategy Result (SR class) or a Customer class? How to choose the Applies to Class while creating my Decision Table in my Decisioning application.
The Decision Table can be defined on the Strategy Result, SR class, or a Customer class. The choice often depends on where the properties used in the Decision Table are located. Let us discuss the following three design options:
If the Decision table is using the properties from the Customer Class and Decision Table returns result from Decision Table OR result of the Decision Table directly sets the property available in the same customer class, you should create Decision Table in a Customer class.
If the Decision table is using the properties from the Customer Class, if you want to refer the very few computed properties from SR class, creating Decision Table in Customer Class OR SR class OR both options are valid. The design decision here could be, if you want to set result of the Decision Table to a specific property directly from the Decision Table. If you want to set the result of DecisionTable to a SR class, Create the Decision Table in SR class. If we want to set the result of DecisionTable to a Customer class, Create the Decision Table in Customer class. If the Decision Table returns the result and result of the Decision table referred using pxSegment result property, creating DecisionTable in Customer,SR class both valid.
Let us take an example below. Customer CreditScore is a derived property from SR class. OutstandingLoanAmount is a Customer class property. Based on these two property values, Decision Table returns RiskScore.
Decision Table to compute the RiskScore
Creating the table requires two condition columns. First is the Principal Loan, which is the property in the data model representing the outstanding loan amount.
The Operator represents the condition applied to the column. In this case, greater than, which allows you to express the Outstanding loan amount condition from the requirement.
The second condition column is the Credit Score property. The Credit Score is a parameter, so you need to use the Param.PropertyName construct.
The Use Range checkbox groups the credit scores together.
Fill in the bank’s requirements and specify a Return value for each row in the table.
Filter credit cards based on the calculated risk segment
Configure two Filter components to ensure that you identify High Risk and Low Risk customers.
Based on the Customers in the risk category, we can compute the customers eligiblity. The pxSegment Strategy property contains the output of the Decision Table.
Still confused with the Desion option to Define the Decision Table in a PEGA Decisioning application? Feel free to reachout to me.
Happy Learning,
Nanjundan Chinnasamy
