Processing Flow

EngageOne™ Enrichment processes your application in a specific manner depending on the types of print stream manipulations that your application performs. EngageOne™ Enrichment automatically picks the method based on the functions being performed in the application. There are three types of processing that can occur:

• One-at-a-time processing
• All-at-a-time processing without presort
• All-at-a-time processing with presort

It is critical that EngageOne™ Enrichment application developers fully understand these processes to code effectively. The key points for application developers to remember are:

• The order of the steps is important, especially when processing occurs for rule file sections.
• Some steps create data that is saved in system variables (non-user-defined variables set by EngageOne™ Enrichment). For example, the CASS step produces variables that contain the cleansed address lines. You should not use system variables in EngageOne™ Enrichment steps that occur prior to the step in which the system variable is populated with a value (so, you should not use CASS system variables in the START section of the rule file, for example).
• In both all-at-a-time processing methods, EngageOne™ Enrichment reads and stores all documents in memory before processing them. This requires more memory and I/O than one-at-a-time processing.