Task 2: Finishing work on a change activity

In this step, you access a change activity in the Spring release. The release contains two change activities, one that is already completed, and the other that Bea must finish.

1. On the Activities tab of the Spring release, click Adjust Scoring. Notice, on the Change Activity panel, that Bea is the only author for this activity, and that Paul is the owner and approver. An activity can have many authors and approvers, but only one owner.
   
2. Click the Snapshots tab.
   The Initial Snapshot shows the contents of the change activity when it was created. It is an exact replica of the Spring release at that time. Other change activities might have changed the release since. The snapshot was automatically made when the change activity was created.
3. Click the Decision Artifacts tab.
   You can see that Loan Validation Service contains five projects. The top-level project has the same name as the decision service, and the other projects are listed below it.
4. Click the Loan Validation Scoring > computation folder to see the rules in this folder.

In this step, you run a simulation in the change activity.

1. Click the Simulations tab, and then click the Simulations subtab.
   The simulation has been prepared for you.
2. Click File Simulation in the list of simulations. Click Run, and then click OK in the pop-up window.
   Once the status column shows a check mark, click the report name. The report shows different graphs that correspond to key performance indicators.
3. Close the report.

In this step, you change a value in a decision table, and a condition in a business rule.

1. Use the breadcrumbs to return to Spring Release. Click the Decision Artifacts tab and select the Loan Validation Scoring > computation folder.
2. Click the salary2score decision table.
   The decision table is displayed.
3. Click the Edit button just above the table. Accept the default settings and click OK.
4. Double-click 300 in Row 8, change 300 to 400, and press Enter.
5. Click Save. Adding a comment is optional. Click Create New Version.
6. In the Decision Artifacts tab, select the Loan Validation Check > validation > loan folder.
7. Hover over the checkAmount rule.
   Notice that this rule currently has version 1.0.
8. Click checkAmount and then click the Edit icon above the rule.
9. Change maxAmount from 1,000,000 to 200,000.
10. Click Save and then Create New Version.

    Notice how the version number is now 4.0. In Decision Center, each branch is assigned a major version number. Before editing, the version number 1.0 came from the original main branch. Branch 2 is the Initial Release, branch 3 is the Spring Release, and branch 4 is this change activity. Subsequent changes increase the minor version of the rule. When the change activity is completed and merged with the release, the major version number adopts the release version, and the minor version number reflects the sequence of change activity merges.

In this step, you test the results of the rules.

1. Click the Tests tab and then click Scoring test suite.
   This test suite has been prepared for you. Before you run the test suite, notice the following aspects:

   • The test suite runs on the version of the rules that are contained in the Adjust Scoring change activity, but not necessarily all of its rules. The decision operation, in this case loan validation with score and grade, further identifies which subset of rules from the decision service to test. Hover over the decision operation name to get more details on what it contains.
   • The scenarios are stored in the assessment.xlsx file, which is an Excel Workbook that you generate and edit to contain the data that you need: a Scenarios tab for the input data, and an Expected Results tab where you enter what you expect to obtain for specific tests.
2. Click Run, and then click OK.
   Running a test suite generates a report. Once the status of the test shows a check mark, click the report name. The report shows that 100% of the scenarios are successful because they generate the expected results.

   The Results section of the report shows an accepted low risk loan request and two rejected loan requests. Expand one scenario to see all the tests it contains. For each test with a simple type value, it shows the result value and the expected one. For each test with a collection value, a Details dialog can be opened to get the tested collection and the expected one.

3. Close the report.

In this step, you deploy the change activity.

1. In the top banner, click Deploy.
2. Make sure that the sample server is the target of the deployment and click Deploy.
3. Click OK.
4. Once the status is complete, click on the report name to see the details of the deployment.
   You see more details about the report in Task 4.
5. Close the report.

In this step, you change the work status.

1. On the Change Activity panel, change the status from Working to Finish working.
   Bea's working status becomes Finished. No other changes can be made to the change activity unless the owner reopens it.
2. Log out.