When an action happens in STEP, it is common to want information about the data that was created, modified, or deleted to be sent to a 'downstream' system, also called an external system. A 'downstream' system is a system outside of STEP that uses data from STEP to perform a task. For example:
- A new product image is approved in STEP, and that image should also appear on the website for the product.
- An object lifecycle has been updated and should be reported to a separate system used for tracking.
- A duplicate customer record was identified and should be deleted from STEP, and also removed from the system used to generate mass mailing material.
Of course, a person could manually update the same data in both systems, but a more efficient way to manage this is to allow STEP to automatically send the new, modified, or deleted data.
Configuration
This is a road map of the setup for automatically sending data using several STEP elements. This is the recommended order that the elements should be configured, as well as links to the online help with details for configuration.
- Establish one or more attribute groups to contain the data required by the downstream system, as defined in the Attribute Groups topic in System Setup here.
Using attribute groups allows you to easily view only the data being exported. When using an output format other than STEPXML, it also makes the data mapping process easier since all required attributes are stored in the same place.
- Create an event-based OIEP, as defined in the Creating an Event-Based Outbound Integration Endpoint topic in Data Exchange here.
An event-based OIEP uses triggers to define what changes are important for this export, how the data should be formatted and delivered, as well as when the output should be generated.
Setting up an OIEP includes both a wizard and some manual configuration. Of particular interest are the following settings:
- Set the OIEP event triggers, as defined in the OIEP - Event-Based - Event Triggering Definitions Tab topic in Data Exchange here.
- Set the export delivery method, as defined in the OIEP - Delivery Method Flipper topic in Data Exchange here.
- Consider if a workflow should be used to manage the maintenance and approval process, as defined in the Getting Started with STEP Workflows topic of Workflows here.
A workflow can help managers and users track data moving toward the export process. Use assignments within the workflow to indicate when human intervention is required, and keep the process moving.
- Consider if a business rule should be used to automate any part of the process, as defined in the Business Rule Use Cases topic of Business Rules here.
A business rule can test for conditions that would eventually cause a blocking issue, and when used with a workflow, can reroute an object back to the person who can address the problem.