Task 2: Orchestrating

To create a rule package:

1. In Rule Designer, in the Orchestrate part of the Rule Project Map, click Add rule package.
   Tip: You can also right-click the my rule project/rules folder in the Rule Explorer and click New > Rule Package.
2. In the New Rule Package wizard, enter validation in the Package field, and then click Finish.

   The new validation rule package opens in the Rule Explorer.

3. Create another package named eligibility.

Your rule project now contains two packages for storing your rules:

To create a ruleflow:

1. In the Orchestrate part of the Rule Project Map, click Add ruleflow.
   Tip: You can also right-click the my rule project/rules folder in the Rule Explorer and click New > Ruleflow.
2. In the New Ruleflow wizard, make sure that the Source folder field is set to /my rule project/rules, and that the Package field is empty.
3. In the Name field, type miniloan.
4. Click Finish.

   The ruleflow editor opens, and enables you to construct the flow of tasks graphically. You specify how tasks are chained together: how, when, and under what conditions they will be executed.

5. Click Create a start node and then click in the ruleflow editor.

   The ruleflow start node is displayed in the ruleflow editor.

6. Click Create an end node and then click in the ruleflow editor.

   You now have a start node and an end node for your ruleflow.

To define the rule tasks:

1. Drag the validation rule package from the Rule Explorer and drop it into the ruleflow editor.

   The validation rule package becomes a rule task in the ruleflow. By dropping this package into the ruleflow editor, any rule that you create in the package will be part of the execution, unless you specify otherwise.

2. Drag the eligibility rule package from the Rule Explorer and drop it into the ruleflow editor.
3. Click Create a transition and create the following transitions (shown as arrows) by clicking the first item and then clicking the second item:
   1. The start node and the validation task.
   2. The validation task and the eligibility task.
   3. The eligibility task and the end node.
   4. The validation task and the end node.

      Some errors are displayed on the transitions to indicate that the conditions are missing:

      
4. Click Create a transition to deselect the transition tool.
5. Click Layout All Nodes to format the ruleflow diagram.
6. Save your work.

To define the main transition:

1. Click the transition from validation to eligibility.

   The Properties view opens and shows the condition for this transition.

   Tip: If you cannot see the Properties view, click Window > Show View > Properties to open the Properties view.
2. In the Label field, type data approved.
3. Make sure Use BAL for transition condition is selected, to write the condition using the Business Action Language (BAL).
4. In the text area, type a space to display the Content Assist box, and double-click the items to form the following statement: 'the loan' is approved.
   Tip: You can also type the statement directly in the text area.

   The Properties view should look like this:

   

   The transition from validation to the end node is automatically set to else.

5. Save the changes.

   Your ruleflow should now look like this:

   

To define the final action:

1. Click the end node.

   The Properties view lets you enter the final action.

2. In the Final Action section, make sure Use BAL for action is selected.
3. In the text area, type a space to display the Content Assist box, and enter the following final action:

   print the approval status of 'the loan' ;

   Note: You must add a semicolon (;) at the end of the line.

   At execution time, this final action displays a message in the Console indicating the status of the loan at the end of rule execution.

4. In the ruleflow editor, click outside the diagram, and in the Properties view, make sure that the main flow task is set to true.
5. Save your work and close the ruleflow editor.