Quiz du module

Creating the Credit Risk Output Strategy

The Credit Offers decision strategy outputs three crucial flows: credit offers, credit scores, and credit eligibility when a customer applies for a cash loan.

To use the strategy to make a final decision and present this decision alongside relevant credit offers, credit scores, and credit eligibility policy information, you create a strategy that integrates the three flows, resulting in a comprehensive decision strategy. The strategy enables the system to communicate the final decision, along with relevant credit offers, credit score, and credit eligibility policy information back to the calling credit application.

Creating the Credit Risk Output Strategy

Start by creating the Credit Risk Output strategy, and then configure three sub-strategy components to import the three flows from the Credit Offers Decision strategy: Credit Offers, Credit Score, and Credit Eligibility.

This setup enables us to use the existing decision logic to inform our final decision-making process.

Calculating the Final Decision

Next, configure the strategy to calculate a final decision. Add a Group By component to aggregate data from the Credit Eligibility component.

Note: Group By components set strategy properties using an aggregation method applied to properties from the source components.

Set up the aggregation to check if all eligibility rules are met, and string the reasons for ineligibility together.

Also aggregate the information from the Credit Offers component, to determine if any requested or alternative offers are available offers for the customer.

After aggregating the data, add a Decision Table to set the final decision.

The following table references the aggregated data to determine whether the final decision is to approve, decline, or further investigate the credit application. The decision table uses predefined conditions and actions to output the appropriate final decision. The first column shows combined result of Eligibility checks. When .IsEligible property equals true, the customer passed all stop-rules (for example age, or debt check). The second column determines if there are alternative offers available. The third column checks if the requested product is available.

If the customer qualifies for the requested offer, the loan is approved. If the customer does not qualify for the requested offer, but an alternative offer is available, the loan application requires further investigation. Otherwise, the loan is declined.

Once the final decision is set, configure a Set Property component to populate the Name property of the decision. This ensures that the final decision is correctly formatted for the output.

Add a Filter component to refine the selection of suitable credit offers. Configure the Filter component to exclude declined offers from the final output.

Finally, connect all components to the Results component, ensuring that the entire strategy flows correctly from input to final decision output.

Test the strategy using a simulation Data Set with various customer profiles to confirm your work. Check the number of decisions and the outputs for different components, ensuring the strategy correctly aggregates data and makes appropriate decisions.

Review the final decision and investigate any declined offers to understand why a customer was declined. This testing confirms that the strategy is robust, accurately determines credit eligibility, and offers suitable credit products.