To run our example in the Stardust Portal, we first deploy the interface, implementation and consumer models. The Model Management view appears as shown below.
Figure: Deploying the interface, implementation and consumer models
Next, we kick off the Product Purchase Process and enter some customer data. We do not enter any value for the Final Outcome field since it is populated by the runtime process implementation selected and displayed as the modified customer data in the final step of the Product Purchase Process.
Figure: Enter Customer Details activity
In the next step, we select the follow-up action (in this case Escalate). The Followup Process field is left blank since it is populated in the subsequent message transformation application (see section Converting Follow-up Actions).
Figure: Select Followup Action activity
In the final step, the Display Final CustData activity displays the modified customer data. The Final Outcome field is populated with a value that depends on the Process Implementation selected at runtime. In this particular case the value Escalated is displayed since we chose the Escalate action in an earlier step (see section ).
Figure: Display Final CustData
The Process History view displays the sequence of activities executed during the process run. It also indicates that the CustData_Escalation_Process was selected at runtime. This agrees with the input provided earlier and validates that our processes have been designed correctly. We can run the process once more and choose the other follow-up action, this time Ship, to test that the CustData_Shipping_Process is executed for this value.
Figure: Process History and display of runtime Process
Implementation information