How On-demand Campaign or List selections are stored

When the list selection flowchart associated with an On-demand Campaign or List runs in Campaign, the selected customers are stored in the Collaborate system database.

On-demand Campaign selections are stored in the uacc_ondemand_lists table.

List selections are stored in the uacc_lists table.

Generating and storing the list through the flowchart

Note: Before the flowchart can store the list selections in the uacc_ondemand_lists or uacc_lists table, the table must be mapped in Campaign.

List selections are made through one or more Select processes in the flowchart. You define the SQL statements to select desired customers for the On-demand Campaign or List. For example, the Select process might select all customers with a savings account within a specific range.

You also use user variables to specify parameters in Collaborate that are used as selection criteria in the flowchart in Campaign.

If you are using the List Manager following the Select processes, you add a Snapshot or Extract process. When configuring the Snapshot or Extract process, ensure that you:

Export the selections to the uacc_ondemand_lists or uacc_lists table.
Select the the Add to Existing Data radio button.
Note: The uacc_ondemand_lists and uacc_lists tables contain the histories of all the generated lists. In the flowchart in Campaign, if you select either Replace All Records or Update Records, the contents of the tables are overwritten or updated and all the lists are deleted or updated. The lifecycle of data in these tables is meant to be managed through Collaborate. For example, when you delete a List, the data for that List is cleared. In addition, when the List is rerun, entries from previous runs of that list are cleared from the table.

Mapping database fields to the uacc_ondemand_lists or uacc_lists table

In the list selection flowchart, you must map fields in your customer database to the following fields in the uacc_ondemand_lists or uacc_lists table:


Field	Field Type	Saved Value
ListId	User Variable	`UserVar.ListId`
AudienceLevel	Derived Field	The audience level(s) configured in the List Manager module must be hardcoded with the values configured in the `listmanager_tables.xml` file (for example, "P" for People Table or "P/C" for People Table/Contract Table).
UserBranch	N/A	N/A
UserID	User Variable	`UserVar.UserName` User to which the selected customer is associated. The value must correspond to the ID that the user uses to log in.
GenerationDate	`<Generate_Date>`	Date on which the records are generated. This can be a specific date, a formula, or a date indicated in the campaign.
Status	Derived Field	"V" is hardcoded. All records are set to "Accepted" by default. List records can have one of four status values, depending on the actions of field marketers during validation: T: To Accept V: Accepted A: Added D: Deleted
AudienceLevelID	`<CustomerID>`	ID of references

You may need to map additional fields for filtering purposes. For example, if the region_id column was added for Data Level Filtering, you need to map it as well.