About Events

An event signals a meaningful change from an SBM application or an external product. For example:

Any SBM application or external product that is capable of calling a Web service can raise events in SBM. After an event is raised, the Event Manager receives it, and then calls the SBM Orchestration Engine to execute the asynchronous orchestration workflow linked to the event. The orchestration workflow could update an SBM item, create a new SBM item, and so on.

The orchestration workflow provides the integration point between an SBM application and an external product, or two SBM applications in the same process app or in different process apps. In the first case, the orchestration workflow can be initiated from either the application or the external product. In the second case, the orchestration workflow can be initiated from either application. Something happens in one that raises an event, and the orchestration workflow runs in response to the event and updates the other.

An event can be raised in the following ways:

The following diagram illustrates the way an event is processed.

Diagram of external event architecture

Remember: Events are relevant for asynchronous orchestration workflows only. For information about the differences between asynchronous and synchronous orchestration workflows, see Comparing Synchronous With Asynchronous Orchestration Workflows.
In addition to initiating an orchestration workflow, an event sends data to it.

In certain external integrations with SBM, errors are handled in a limited way and cannot be automatically retried. You can manually retry these events in SBM Application Repository. For more information, see Retrying Failed Asynchronous Events.