Task 2: Touring the decision service

You open your branch and display its decision artifacts.

1. Click My Branch in the Branches tab of the Miniloan Service decision service.
   Note: The branch might be open already from task 1.
2. Click Decision Artifacts to see the rule artifacts.
   By default, only the rules are displayed.
3. Hover over Types(1/7) X and click the X to display all the artifacts in the decision service. The labels indicate the types of artifacts, and some show the number of artifacts:
   

You open the ruleflow to determine how it works.

About this task

A decision service keeps its decision points in projects and folders. The Miniloan Service decision service contains one project, and two folders for different decision points. The rule in the validation folder determines whether incoming loan data is valid, and the rules in the eligibility folder apply various conditions for eligibility.

The ruleflow states the sequence for applying the rules:

The ruleflow starts by running the rule in the validation folder. If the data from a loan request passes the rule, the ruleflow directs the data to the eligibility rules. However, if the validation decision point does not approve the data, the ruleflow skips the eligibility decision point, and the decision service stops processing the loan request. For more information, see Editing ruleflows.

1. Hover over miniloan in the list of decision artifacts.
2. Click the ruleflow to open it in the preview window.

You open an action rule to determine how it works.

1. In the list of decision artifacts, click eligibility to open the folder in the preview window.
2. Click minimum credit score to open the action rule in the preview window.
   An action rule associates one or more actions with one or more conditions. When the conditions are met, the actions are triggered. The rule statement in the minimum credit score rule looks as follows:

   if
     the credit score of 'the borrower' is less than 200
   then
     add "Credit score below 200" to the messages of 'the loan';
     reject 'the loan';

   As data for the borrower enters the decision service, the action rule tests the credit score variable. If the variable is less than 200, the prescribed action is to reject the loan and work stops on the loan. If the variable is equal to or more than 200, the loan is further processed. For more information, see Action rules.

You open a decision table to determine how it works.

1. In the list of decision artifacts, click eligibility to open the folder in the preview window.
2. Click repayment and score to open the decision table in the preview window.
   A decision table provides a way to view and manage sets of similar rules. Each row in a decision table represents a complete rule. The rules in the table share the same rule statement, but the condition and action values vary. The first two columns (debt to income and credit score) contain the condition variables, and the next two columns (message and rejected) contain the action variables.

   The repayment and score decision table looks as follows:

   

   When the decision table checks a loan request, it rejects the request if the borrower must pay back an annual amount that is too high for the borrower's credit score. Otherwise, the table does not reject the loan. For more information, see Decision tables.

You add a test suite and run it to verify that the decision service works correctly before changes are made.

1. Click Tests > Test Suites to open the subtab.
2. Click the New Test Suite button .
   The dialog for creating a new test suite opens.
3. Click Choose, and navigate to <InstallDir>/odm-cloud-getting-started-master/Miniloan Service.
   InstallDir is your directory for the extracted files from the GitHub repository, as shown in task1, step2.
4. Select miniloan-test.xlsx, and then click Open.
5. Make sure that the selected server is Testing And Simulation Runtime, which is the default server for running tests and simulations.
6. Click the Save and Run button .
7. Enter the information that is shown in the following image:
   
8. Click Create New Version, and then click OK in the Run Test Suite dialog.
   The console runs the test and switches to the Reports tab. A new report indicates a successful test by displaying a check mark in the Status column:

   
9. Click the name of the report.
   The report opens, and displays details that include the following summary:

   
10. Close the report.