During data extract offer execution, files are created as per execution of an export activity and are made available at the RPI server, via FTP, or at an external content provider root folder.
A data extract offer produces files when executed in Production mode, or in Test mode when its channel’s Create files in Test mode property is checked.
By default, data extract files are created in accordance with system configuration setting FileExportLocation. Writing of files to a server folder, FTP site or external content provider root folder is supported.
If files are generated at the server, they are by default created in a sub-folder named in accordance with the following:
‘[(Global)FileOutputDirectory]\WFAI[WorkflowInstanceID]\Export files\[Export name]’
Where (Global)FileOutputDirectory is accordant with the configuration setting value defined at the cluster or client, Workflow Instance ID is the unique numerical identifier assigned to the workflow instance at its creation, and Export name is the name by which the data extract offer is known within the interaction.
Note that the default folder may be overridden if configured accordingly at the data extract channel.
When created at an FTP site or external content provider, ‘(Global)FileOutputDirectory’ is replaced by an ‘Export’ folder.
If configured to write to an external content provider, and no default file export provider has been identified, files are written to the RPI application server instead.
The resultant data and sample files are accordant with the export template with which the channel is configured; in addition, any extra attributes specified within the Offer Designer are appended within the output files.
If the data extract channel through which the offer is fulfilled is configured to allow duplicates on resolution, if the channel’s export template and/or the activity's offer is configured with any cross-resolution attributes, deduplication is ignored, and multiple records for a single resolution key can be output in the export file. Note that the activity's bubble count continues to reflect its deduplicated count.
On generation of an extract file in Test mode, Offer History and Offer History Meta attribute values are replaced with sandbox equivalents. Note that when the same tables are referenced as aggregation tables, sandbox values are not substituted.
If the channel’s export template is configured with a custom header, it is displayed in accordance with its definition. Any Record Count text parts reflect the full export file count.
Filenames are generated as GUIDs (Globally Unique IDs) unless explicitly defined at the channel.
Behavior of a data extract offer downstream from an interactive activity configured with an audience depends on its and its channel’s configuration. If the file to which data is to be written is local to the RPI server, rows are appended to the output file dynamically as they are targeted by the audience. If the export path has been specified, a new file is written at the arrival of new records.
If configuration setting InteractionDaysToPersistExportTempTables is greater than 0, the temporary table generated during offer activity execution is persisted for a number of days specified by the setting. This occurs both in Production mode, and in Test mode when Create files... is checked at data extract channel configuration. Persisted temporary tables can be tracked in the ExportTempTableLookup table, which can be found in the Interaction Audit database. The Dataflow housekeeper removes temporary tables, and matching rows from the table, after the specified number of days.
When PGP encryption is configured at a data extract channel, full export files generated using the channel are encrypted. Sample and summary files are not encrypted. PGP encryption is also applied when files are generated in Test mode, and when file compression is enabled.
If the offer uses the Database Table extract location, data is persisted within a data warehouse table in accordance the data extract channel’s settings. If using default channel settings, the table will be named ‘RPI_Export_[GUID]’ (the actual table name may be discerned within the offer’s execution log). If the table already exists, it is dropped and re-created. If a lengthy custom table name has been specified, it is truncated in accordance with the maximum number of characters permitted by the database. The table is deleted by RPI Housekeeping in accordance with the relevant Days To Persist Table setting.