Scenarios contain the collaboration's business process logic. A highly simplified example, shown in Figure 23, illustrates the logic in a fictional scenario. The collaboration replicates changes to the employee information in a source application by moving them to a destination application. This scenario specifically handles the Create verb.
Figure 23. High-level view of a scenario
In Figure 23, the scenario's trigger is the Employee.Create event notification business object. When the Employee.Create business object arrives, the scenario starts. First, the scenario checks to see whether the employee information already exists in the destination application.
If the employee information already exists in the destination application, the scenario stops. If the employee information does not yet exist, the scenario passes the Employee.Create request business object to the connector for the destination application. A verification step ensures that the operation is successful.
The business process logic in an actual scenario typically consists of many more steps, each of which implements an action by the collaboration. These are some examples of the types of actions that a collaboration might contain: