Testing the Order Handling business process

The order handling process has been modeled, developed, optimized with points of agility, and is configured to emit events for monitoring. The order handling monitor model has been developed to handle those emitted events for display in the Business Space. The Order Handling projects (executables) have been deployed to the WebSphere® Process Server and WebSphere Business Monitor. Now you will test this code to observe the corresponding output and behavior.

Run the process multiple times so there is enough data to display in the Business Space widgets. Create a process instance for each of the following orders. For the non-specified values, any value is acceptable as long as it does not repeat values for value-unique fields, such as the shipping number.

To run the process instances, do the steps that were used during the runtime testing in the section Testing the initial shipping policies.

You can create more scenarios than are listed here.

Scenario 1: Process tasks run; approve without review; account in good standing; ship the order
1. Form data to start this instance of the process.
  1. Rating: 800
  2. Available Credit: 800
  3. Total Price: 200
2. Ship task
  1. Packing Slip Number: Any unique value
Scenario 2: Process tasks run; approve without review; account not in good standing; approve the order; ship the order
1. Form data to start this instance of the process.
  1. Rating: 800
  2. Available Credit: 100
  3. Total Price: 300
2. Review task
  1. Order Status: APPROVED
3. Ship task
  1. Packing Slip Number: Any unique value
Scenario 3: Process tasks run; approve without review; account not in good standing; decline the order
1. Form data to start this instance of the process.
  1. Rating: 800
  2. Available Credit: 100
  3. Total Price: 400
2. Review task
  1. Order Status: REJECTED
Scenario 4: Process tasks run; do not approve without review; approve the order, ship the order
1. Form data to start this instance of the process.
  1. Rating: 10
  2. Available Credit: 100
  3. Total Price: 900
2. Review task
  1. Order Status: APPROVED
3. Ship task
  1. Packing Slip Number: Any value
Scenario 5: Process tasks run; do not approve without review; decline the order
1. Form data to start this instance of the process.
  1. Rating: 10
  2. Available Credit: 100
  3. Total Price: 800
2. Review task
  1. Order Status: REJECTED
Scenario 6: Repeat Scenario 5
Repeating the declined order scenario is necessary to see an alert in the Alerts view of the business space dashboard. The monitor model is configured to raise an alert when the number of shipped orders is less than 85 percent of the total number of orders. You will see this alert when you complete the steps in the Creating a business dashboard in Business Space section.