In a campaign workflow, how should a Business Practitioner ensure that Adobe Campaign retains data between intermediate activities?

The "Keep the results of interim populations between two executions" option is a specific setting within a workflow's properties. A Business Practitioner selects this option to explicitly instruct Adobe Campaign not to purge the temporary worktables generated by activities after the workflow finishes. This ensures that the data processed by each activity is retained, which is essential for debugging, auditing the workflow's logic, or optimizing performance by reusing the results in subsequent executions without recalculating them. This is the direct action a user takes to control and ensure data retention.

A. This option is for debugging purposes. It logs the SQL code executed by the workflow but does not retain the resulting data populations for use by other activities.

B. Displaying the target is a temporary, in-place visualization feature to check the count of a population at a specific point; it does not affect data persistence within the workflow.

C. While Campaign uses temporary worktables by default to pass data, this describes the internal mechanism. It is not a setting or action a practitioner takes to ensure retention; the "Keep results..." option (D) is that explicit action.

1. Adobe Experience League - Campaign Classic Documentation - Workflow properties: In the 'Execution' section of the workflow properties

the option "Keep the results of interim populations between two executions" is described. The documentation states: "this option allows you to keep the temporary tables so that you can reuse them for the next time the workflow is executed... This option is also enabled for debugging purposes

to analyze the results of intermediate populations." This directly supports option D as the correct action for a practitioner to ensure data is retained.

(Reference: Adobe Experience League > Adobe Campaign Classic v7 Documentation > Workflows > Workflow properties > Execution)

2. Adobe Experience League - Campaign Classic Documentation - Get started with workflows: This documentation explains the fundamental behavior of workflows. It notes

"The data is transported from one activity to another... The result of each activity is stored in a temporary table or list which can be reused in the following activities." This confirms that worktables are the standard mechanism (as in option C)

but it is the setting in option D that a user configures to keep these tables.

(Reference: Adobe Experience League > Adobe Campaign Classic v7 Documentation > Workflows > Get started with workflows > Build a workflow)