The Extract process
Use the Extract process to select fields from one table and write them out to another table for subsequent processing. The Extract process is designed to pare down a large amount of data to a manageable size for subsequent operations, resulting in vast performance improvements.
The Extract process can take input from a cell, single table, strategic segment, optimized list (Contact Optimization only), or eMessage landing page (eMessage only). If you select a strategic segment as input, you must join it to a table before you can extract fields.
If you use several Extract processes in a series, only the fields in the final Extract process are written out.
If you use several Extract processes in parallel (in different branches in the same flowchart), they behave the same as persistent derived fields:
*
The extracted fields attach to the inbound cell
*
The extracted fields are calculated before query execution in that process
*
Multiple extracted fields are available in subsequent processes
*
When extracted fields are sent to a contact process:
*
If an extracted field is not defined for a cell, its value = NULL
*
If a single ID is in more than one cell, one row is output for each cell
*
When extracted fields are sent to a Segment or Decision process, the extracted field must exist in all selected input cells for it to be used in segmenting by query.
Extracted tables
Data is extracted as either a binary file on the Campaign server or as a table with a UAC_EX prefix.
Extract tables are not deleted at the end of a flowchart run. An extract table persists so that users can continue to access it to perform operations such as profiling its fields.
An extract table is deleted only when you delete its associated Extract process, flowchart, campaign, or session.
*
To conserve space, system administrators can periodically delete tables with a UAC_EX prefix. However, if these tables are removed, you must rerun the affected Extract processes before you rerun flowcharts or profile fields in the now-missing tables. Otherwise, Campaign generates "Table Not Found" errors.
Example: Extracting transaction data
Prerequisites for extracting data from eMessage landing pages
Extracting subsets of data for further processing and manipulation
Copyright IBM Corporation 2015. All Rights Reserved.