Open topic with navigation

Event Processors

An event processor includes a queue of generated events and an engine for processing the events. For information about how and when events are generated, see the Events section of the System Setup / STEP Super User Guide documentation here.

An event processor has no delivery method, but is otherwise similar to an event-based outbound integration endpoint (OIEP). Event processors can be used alone when the results are only required internally to STEP. However, if the delivery of the results of the event processor is required externally, the event processor can be used in conjunction with an OIEP. For more information, see the Creating an Event-Based Outbound Integration Endpoint documentation here.

As described in the Configuring an Event Processors topic referenced below, event processors can be used to automatically perform actions based on triggering events, including:

• Managing revisions on objects via the Revision Management processor.
• Propagating updated LOV values to the objects that use the LOV via the Expand LOV Value Changes processor.
• Caching assets via the Image Cache processor.
• Generating new match code values and/or running a matching algorithm via the Matching processor.

Configuring an Event Processor

To configure an event processor, complete the following steps:

1. Perform one-time setup tasks to allow for the creation of event processors as described in Setting Up for Event Processors here.

2. Create an event processor as described in Creating Event Processors here.
3. Enable the event processor as described in Enabling Event Processors here.

Important: If an event processor is being used in the process of moving data outside of STEP, an OIEP is required as a delivery method.

2017, Stibo Systems