Processing Plugins

An event processor consists of an outer Event Processor Framework for finding and reacting on events, and an inner processing mechanism (processing plugin) that deals with the actual event batch. The Event Processor Framework is the same for all event processors, whereas there are many different types of processing plugins.

For more information on Event Processors, refer to the Event Processors documentation here.

When creating an event processor to monitor events within STEP, a processing plugin must be selected and configured. By default, all processing plugins skip deleted objects (objects in the recycle bin).

Below is a list of available processing plugins and links to their configuration details. Custom processors can be created for various business requirements. For more information, contact Stibo Systems.

Note: Some processing plugins may not be available without enablement of a corresponding add-on component and/or license. Contact Stibo Systems to begin the process of enabling a license or licenses for your system. For on-premises systems, instructions for installing components can be found in the 'SPOT Program' topic in the System Administration documentation found in 'Downloadable Documentation'. For Stibo Systems SaaS environments, contact Stibo Systems Support.

Processing Plugin Name

Description

Asset Publisher

Offers many of the same options as traditional Asset Push functionality and can be configured to publish asset content directly to cloud blob storage. Refer to the Asset Publisher Processing Plugin Parameters and Triggers documentation here. Also, refer to the Asset Push documentation within the Digital Assets documentation.

Asynchronous Translation Message Processor

Allows users to send scheduled translation jobs to asynchronous translation services based on a derived event, and depending on user preferences, batch translation events into as little as one translation job, reducing translation costs. Refer to the Asynchronous Translation Message Processor Processing Plugin Parameters and Triggers documentation here.

CASS Certification Report

Generates CASS (Coding Accuracy Support System) certification reports. Only available for users in the US who have both a Loqate Local integration and a CASS license. Refer to the CASS Certification Report Processing Plugin Parameters and Triggers documentation here.

Data Sufficiency Calculator

Works in tandem with the sufficiency configuration type to calculate sufficiency scores for a given product. Assesses all the sufficiency configuration types within a system and calculates the sufficiency scores for the products included in the 'Triggering Object Types' parameter in the 'Event Triggering Definitions' tab of the event processor. Refer to the Data Sufficiency Calculator Processing Plugin Parameters and Triggers documentation here.

Elasticsearch Indexer

Allows STEP to publish data to Elasticsearch for a faceted search experience. Refer to the Elasticsearch Indexer Processing Plugin Parameters and Triggers documentation here.

Execute Business Action

Allows a business action to be run from an event processor, so that when changes occur, a custom business action on objects can be asynchronously triggered. Refer to Execute Business Action Processing Plugin Parameters and Triggers documentation here.

Execute Business Action for Event Batch

Allows a business action to be run from an event processor, so that when changes occur, a custom business action can be asynchronously triggered. The configured business action executes once per event batch (instead of once per event like the Execute Business Action). Refer to Execute Business Action for Event Batch Processing Plugin Parameters and Triggers documentation here.

Expand LOV Value Changes

Allows the event processor to react on all LOV value update events (only for LOVs that use Value IDs), including those made manually from workbench or Web UI, via LOV value merge, via import, etc. Refer to Expand LOV Value Changes Processing Plugin Parameters and Triggers documentation here.

Experian Email Validation

Allows the event processor to be configured with an Experian Email Validation Configuration, and a business condition used to revalidate email information (Email Revalidation). The common setup is to configure to listen for 'Account' events made by changes in the 'Email Field' and the 'Experian Email Validation' processing plugin. Refer to Experian Email Validation Processing Plugin Parameters and Triggers here.

Historic Data Analyzer

Allows for the analysis for data for historic reporting. The event processor (IdOfReport_RA) is created automatically when starting the report. Refer to the Historic Reporting documentation in Resource Materials here.

Historic Data Generator

Allows for the generation of historic reports. The event processor (IdOfReport_RG) is created automatically upon generation of a historic report. Refer to the Historic Reporting documentation in Resource Materials here.

Image Cache

Allows the event processor to generate images for required conversions asynchronously and saves the resulting files to the image cache. Refer to Image Cache Processing Plugin Parameters and Triggers documentation here.

Matching

Allows for the generation and/or updating of match code values, as well as the option to run matching algorithms, whenever an event is processed on the objects acted on by the algorithm. Refer to Matching Processing Plugin Parameters and Triggers documentation here.

Revision Management

Allows automatic purging of object revisions to limit the total number of revisions retained. Refer to Revision Management Processing Plugin Parameters and Triggers documentation here.

Source Record Data Management – Historical Values Cleanup

Allows incremental purging of the oldest historical source data and optimizing storage to keep disk usage as low as possible. Storage of source data is only supported on object types identified by the 'Matching - Merge Golden Records' component model. Refer to Source Record Data Management Processing Plugin Parameters and Triggers documentation here.

Splitting Processor

Designed for historical reporting. The functionality is in ramp-up status, and while accessible, may not work for you as expected since it is still under development. Historical reporting is traditionally extremely slow, and there is a need to distribute events in a controlled manner. The Splitting Processor takes a number of queues from other event processors or outbound integration endpoints, and either copies the entire batch of events to all of them or distributes the events evenly between the queues. Refer to Splitting Processor Processing Plugin Parameters and Triggers documentation here.