Task 3: Reviewing and approving the changes

In this task, you log in as Paul to review and approve Bea's changes, and then complete the validation activity for the release.

About this task

Bea has updated the decision service and posted a comment for Paul. Now, you log in to the Business console as Paul to check her work and validate the release.

Step 1: Reviewing and approving the change activity

In this step, working as Paul, you review and approve Bea's changes.

About this task

In the decision governance framework, after all authors finish their work in a change activity, the owner must manually update the status of the change activity to Ready for approval. Approvers can then start their work.

Procedure

  1. Log in to the Business console by using Paul as the user name and the password.
  2. Click the Work tab.
    This tab shows all activities where work is required of the participant. Paul, as the owner of the Adjust Scoring change activity, must set the status to Ready for approval.
  3. Click the arrow next to the activity title Adjust Scoring. In the drop-down menu, select Proceed to approval.
  4. Click Adjust Scoring to go to the change activity.
    The status is now Ready for approval. Because Paul is also the lone approver, he can approve the change activity immediately.
  5. In the Approvers section, change Not Reviewed to Approve changes.
    A confirmation is requested.
  6. Click Approve.
    The change activity now has a status of Complete. A snapshot of the change activity is automatically created in the release, and the rules that were modified during the change activity are merged into the release. Creating the snapshot might take some time to complete.

Step 2: Running tests in the validation activity

In this step, you start verifying the release before it can be deployed.

About this task

All the change activities of the release are finished, and Paul must complete the validation activity of the release. You use validation activities to manage a testing approach to validate the content of the release. This testing approach can be made up of manual tests that are entered in a test plan, and automatic tests through test suites and simulations. You must use a validation activity to run test suites and simulations on the version of the rules that are contained in the release.

Procedure

  1. In the Spring Release branch, click the Activities tab, and then click Spring Validation.
  2. Click the Test Suites tab, and then click the Spring release test suite, which has been prepared for you.
    Here, Paul wants more information in the report than just the scenario success rate.
  3. Click Edit, and select the following options in the Report section:
    • The number of rules fired.
    • The number of executed ruleflow tasks.
    • The list of rules not fired.
    • The list of not executed ruleflow tasks.
    • Create Excel file with report output values. This file contains the values of your business terms before and after running the rules, which is useful for troubleshooting or to help you to complete the expected results.
  4. Click Save and Run, and then Create New Version.
  5. Click the report name when the status shows a check mark.
    The report shows that 100% of the test scenarios have the expected results.
  6. Click the arrow next to Average risk.
    The Execution Details section shows the information that Paul requested.
  7. Close the report.

Step 3: Running simulations in the validation activity

In this step, you continue verifying the release before its deployment.

About this task

Paul runs a simulation to evaluate the potential effect of the rule changes. Paul imports a simulation from a change activity, runs it in the validation activity, and compares the new report with a report from the change activity. By importing the simulation, Paul can apply the same conditions that were used in the first simulation.

Procedure

  1. On the Spring Validation page, click the Simulations tab and then click the Simulations subtab.
  2. Click the Select multiple simulations icon between the New and Run icons. Select File Simulation, and click Import.
    All the building blocks for File Simulation, including the key performance indicators, data file, and report template, are imported into the validation activity. This operation might take a while to complete.
  3. Click File Simulation in the list of simulations, and then click Run. Once the status is complete, click the report name to open the report.
  4. Click Compare, and select the simulation report from Task 2 to compare it side by side with the new report.
  5. In the breadcrumbs, click Spring Validation to leave the comparison window.

Step 4: Completing the validation activity

In this step, you finish the validation of the release.

About this task

The tests are finished. Paul approves and completes the validation activity so that the release can be approved and completed.

Procedure

  1. In the Testers field, change Working to Finish working.
  2. Next to the Status field, change In Progress to Proceed to approval.
    The status changes to Ready for approval. Because Paul is also the lone approver, he can approve the validation activity immediately.
  3. In the Approvers section, change Not Reviewed to Approve changes.
  4. Click Approve.
    The validation activity now has a status of Complete. A snapshot of the release is automatically created. This operation might take a while to complete.

What to do next

In the next task, Paul completes the current release, deploys it, and creates the new release.