When a workflow activity in Adobe Campaign Classic encounters an error, it pauses and the activity is highlighted with a blinking red halo. The most direct and standard method for any user, including a business practitioner, to diagnose the issue is to access the activity's specific execution log. This log contains detailed messages, including the specific error that caused the failure. Right-clicking the problematic activity and selecting "Display Logs" opens this log, allowing for immediate troubleshooting.

B. Open the activity and view errors in the Advanced tab

The 'Advanced' tab within an activity's properties is used for configuration, such as scripting or setting execution parameters, not for displaying runtime error logs.

C. Under Campaign Administration, click "Error Logs"

This section shows global system-wide logs, not logs filtered for a specific activity in a particular workflow. It would be inefficient for diagnosing a single activity's error.

D. Ask a system administrator

While an administrator can help, the platform provides tools for business practitioners to perform initial troubleshooting themselves. This is a procedural step, not a direct technical solution within the tool.

1. Adobe Campaign Classic v7 Documentation - Workflow monitoring:

Section: Monitoring a workflow instance

Content: "A red halo means that an error has occurred. To find out the cause of an error

display the logs. To do this

right-click the faulty activity and select Display the logs." This directly confirms that right-clicking the activity to display its logs is the correct procedure.

2. Adobe Campaign Classic v7 Documentation - Get started with workflows:

Section: Executing a workflow > Logs and tasks

Content: "The Log tab lists the execution messages for the selected task. The same log is displayed if you right-click a task and select Display logs." This reinforces that the logs contain execution messages and are accessed via the right-click menu.

The 'Label' is the primary, human-readable identifier for a campaign in Adobe Campaign Classic. It is a mandatory field that must be populated to create and save a new campaign instance. This allows users and the system to uniquely identify and reference the campaign within the marketing plan. While other attributes are important for execution, the label is fundamental to the object's creation.

B. Start date: A campaign can be created in a 'Planning' or 'Draft' state without an immediate start date. Scheduling is often configured after the initial setup and content are finalized.

C. Plan: A campaign can exist independently without being assigned to a 'Plan' or 'Program'. This linkage is for organizational and budgetary hierarchy and is not required for creation.

D. Channel: The communication channel (e.g., email, SMS) is determined by the delivery activities configured within the campaign's workflow, not as a mandatory top-level property of the campaign itself.

1. Adobe Experience League - Campaign Classic v7 Documentation: In the section on creating a marketing campaign

the first step after selecting a template is to define the campaign's properties. The documentation states

"Enter a label for the campaign." This

along with the 'Internal name'

serves as the campaign's primary identifier

which is a prerequisite for creating any new entry in the system.

Source: Adobe Campaign Classic v7 Documentation

"Get started with marketing campaigns > Campaign properties"

Section: "General tab".

2. Adobe Experience League - Campaign Classic v7 Documentation: The data model for campaigns (nms:operation) requires a primary key and a label for identification in the user interface and database. While the internal name (internalName) is also mandatory

it is often automatically derived from the label (label) upon creation

making the label the essential user-provided field.

Source: Adobe Campaign Classic v7 Documentation

"Data model description > nms:operation".

The install URL for an Adobe Campaign instance (typically formatted as http:///nl/jsp/logon.jsp) directs the user to the main access portal. The first and mandatory step upon reaching this page is user authentication. The system presents a login screen where the practitioner must enter their username and password. This is a security measure to ensure that only authorized users can access the instance's resources, including the link to download the client console. Access to the download link is granted only after a successful login.

A. The Practitioner is redirected to the download page only after successfully authenticating through the login prompt.

B. The Adobe Campaign Client console is a rich-client (desktop) application that must be downloaded and installed; it does not open from a browser URL.

C. A blank page would indicate a server-side error or a network configuration issue, not the expected operational behavior.

1. Adobe Campaign Classic v7 Documentation

Installation

Client console installation: "To install the client console

you need to access your Adobe Campaign instance with the following URL: http:///nl/jsp/logon.jsp. On the connection page

enter your login and password... Once you are connected

a page offers a link to download the client console setup program." This confirms that the login prompt is the immediate step.

2. Adobe Campaign Classic v7 Documentation

Getting Started

Accessing Campaign: This section describes the general access procedure

which always begins with the login page presented by the logon.jsp URL. The documentation states

"To connect to an Adobe Campaign instance

you can use the rich client or connect via a web browser

" and for web access

it directs users to the login page.

A recurring scheduler activity initiates a completely new instance of the workflow at each scheduled interval. The standard "Delivery" activity in a workflow is configured based on a delivery template. Each time a new workflow instance runs and reaches the delivery activity, it creates a new, distinct delivery instance by duplicating this template. Consequently, a unique delivery is prepared and sent for each recurrence. This is the standard, expected behavior, allowing the delivery to be sent successfully on the first, second, and all subsequent scheduled runs without errors or warnings.

A. The delivery executes once and errors on the second send.

This is incorrect. An error would only occur if you tried to re-execute the same delivery instance within a single workflow run (e.g., with a loop), not when a new instance is created by a recurring scheduler.

B. The delivery executes once and enters a finished state.

This statement is true for the first execution's delivery instance, but it is an incomplete answer as it fails to address the core of the question, which is about the behavior in a recurring workflow.

C. The delivery throws a warning message and executes as scheduled for first and second send.

This is incorrect because creating a new delivery instance from a template for each scheduled run is the intended and normal behavior; therefore, no warning message is generated.

1. Adobe Experience League - Campaign Classic v7 Documentation

"Delivery (workflow activity)": Under the "Operating principle" section

the documentation states: "When the workflow is executed

this activity will: Duplicate the delivery template to create a new delivery." This confirms that a new delivery is created each time the activity is executed

which happens in each new workflow instance triggered by the scheduler.

2. Adobe Experience League - Campaign Classic v7 Documentation

"Scheduler (workflow activity)": This documentation describes how the scheduler triggers the execution of a workflow. For a recurring frequency

it states

"The workflow will be started automatically according to the defined schedule." This implies a new start or instance for each scheduled time

which then executes all subsequent activities

including creating a new delivery as per the first reference.

A campaign template in Adobe Campaign Classic is a blueprint that pre-defines key elements of a marketing campaign. Using an incorrect template directly impacts the campaign's execution and measurement. The template contains a pre-built workflow that specifies the targeting logic (queries), the type of delivery (e.g., email, SMS), and various parameters like cost tracking and control groups. Therefore, selecting the wrong template can cause the workflow to target the wrong audience, use an unintended delivery channel, and misalign the campaign's data with reporting structures, leading to inaccurate performance analysis.

D. The campaign template could send to individual without a delivery selected

This is functionally impossible in Adobe Campaign. A delivery activity is a mandatory component within a workflow to execute any communication send; a send cannot occur without a delivery.

---

1. Adobe Experience League Documentation - Get started with campaign templates: "Campaign templates allow you to define the main settings of your campaigns

such as the targeting workflow

one or more deliveries

and the processes to be executed." This source confirms that templates define the targeting workflow (supporting answer A) and the deliveries (supporting answer B).

2. Adobe Experience League Documentation - Campaign templates: "A campaign template lets you define a set of characteristics that can be reused for other campaigns. The template can contain: A workflow... A set of services... A set of advanced parameters." The workflow contains targeting and delivery activities. Advanced parameters and campaign properties influence how data is categorized and tracked

which directly impacts reporting (supporting answer C).

3. Adobe Experience League Documentation - Targeting workflows: "The targeting workflow defines the main process of the campaign: population to be targeted

deliveries

etc." This explicitly links the workflow (defined in the template) to targeting the correct population (A) and configuring the correct deliveries (B). The "etc." encompasses other processes that can affect reporting (C).

When targeting recipients based on a custom schema (e.g., policy holders) instead of the default nms:recipient schema, a new targeting dimension must be created. The best practice for this involves creating a new, custom target mapping. This new mapping must reference the custom schema for targeting. Crucially, it also requires the creation of new, custom broadlog and tracking log schemas. These custom log schemas are necessary to correctly link delivery events and user tracking activities back to the records in the custom targeting schema, ensuring data integrity and enabling accurate reporting.

A. Use the out-of-the-box recipient target mapping

This is incorrect because the out-of-the-box mapping is configured to work exclusively with the nms:recipient schema, not the custom policy schema.

C. Modify the out-of-the-box recipient target mapping to use email id from policy

Modifying out-of-the-box components is strongly discouraged as a best practice. Such changes can be overwritten during system upgrades and may lead to instability.

D. Create a custom target mapping using the out of box broadlog and tracking log schemas

This is incorrect because the out-of-the-box log schemas (nms:broadLogRcp, nms:trackingLogRcp) contain a mandatory link to the nms:recipient schema and cannot be used with a different targeting schema.

1. Adobe Experience League - Campaign Classic v7 Documentation

"Creating a new targeting dimension": This guide explicitly outlines the required steps. It states

"To be able to use your new schema as a targeting dimension for deliveries

you must... Create the delivery log schema... Create the tracking log schema... Create the new target mapping." The instructions detail creating new schemas for logs (e.g.

cus:broadLogEx

cus:trackingLogEx) that link to the new custom recipient schema

not the OOTB nms:recipient. This directly supports creating custom log schemas as part of the process. (See Steps 2

3

and 4 in the guide).

2. Adobe Experience League - Campaign Classic v7 Documentation

"Target mapping": This document explains the purpose of target mappings and their components. It specifies that a mapping defines the "schema for delivery logs" and the "schema for tracking logs" for a given targeting dimension. This confirms that the log schemas are an integral part of the mapping definition and must be compatible with the chosen targeting schema.

The "contact date" is a specific setting within the delivery activity of an Adobe Campaign workflow. By setting the contact date to Monday at 8 AM, the practitioner schedules the delivery for that future time. Crucially, this setting is coupled with an option to "Compute target on contact date." Enabling this ensures that the target audience is calculated just before the delivery is sent on Monday, rather than when the workflow is initially executed on Friday. This directly fulfills the requirement to use the most up-to-date target data at the time of sending.

A. extraction date: This is not a distinct configuration option. The date and time of target extraction are determined by other settings, such as the workflow's execution time or the delivery's contact date.

C. scheduler: A Scheduler activity triggers the start of an entire workflow at a specified time. While this could be used, the "contact date" is the more specific and direct configuration for scheduling the delivery itself.

D. approval: An approval activity is used for workflow governance to pause execution pending a user's sign-off. It has no function related to scheduling or target calculation timing.

1. Adobe Campaign Classic v7 Documentation

Delivery properties: In the "Scheduling" section of the delivery activity properties

the documentation states

"You can postpone the delivery by setting a contact date in the future... The Compute target on contact date option lets you recalculate the target on the specified contact date instead of using the target calculated during the execution of the workflow." This directly supports using the contact date to ensure the target is up-to-date.

Source: Adobe Experience League

"Delivery properties".

2. Adobe Campaign Classic v7 Documentation

Scheduler: The documentation for the Scheduler activity explains its function: "The Scheduler activity lets you trigger the execution of a workflow according to a defined schedule." This highlights its role in starting the entire workflow

which is a different mechanism from scheduling an individual delivery within the workflow.

Source: Adobe Experience League

"Scheduler".

In the Adobe Campaign Classic explorer interface, entities such as marketing plans, programs, and campaigns are organized within a folder hierarchy. The most direct and standard method for relocating an entity from an incorrect folder to the correct one is to use the drag-and-drop functionality. This action is intuitive and efficient, allowing the user to simply click on the Marketing Plan, drag it to the desired parent folder in the navigation tree, and release it. Deleting the plan (A) would result in loss of work. Editing properties (B) is used for changing metadata like names or dates, not its folder location. Renaming the folder (D) does not move the plan to the correct location.

1. Adobe Experience League - Campaign Classic v7 Documentation, Explorer workspace: In the section describing the user interface, it is stated that the navigation tree in the Explorer allows for direct manipulation of its elements. "You can move the nodes of the tree using drag and drop. To do this, select the node to be moved and, while holding the mouse button down, drag it to the desired level." This confirms that drag-and-drop is the intended method for reorganizing entities within the folder structure.

2. Adobe Experience League - Campaign Classic v7 Documentation, Programs and plans: This section details how marketing plans and programs are created and organized within a hierarchical structure. The management of this structure, including moving items, is handled through the standard Explorer interface functionalities, where drag-and-drop is a primary feature for organization.

The Deduplication activity in an Adobe Campaign Classic workflow is specifically designed to identify and remove duplicate entries from a target population. To prevent sending a delivery to multiple recipients with the same email address, this activity is configured to use the email address field as the deduplication criterion. It processes the inbound population, identifies records with identical email addresses, and retains only a single record per unique email address for the subsequent delivery activity, thereby ensuring each email address receives the communication only once.

A union activity combines multiple target populations into one. It does not remove duplicates and can, in fact, increase their number if the same recipient exists in multiple inbound sets.

A change dimension activity alters the targeting dimension of the workflow's population (e.g., from profiles to transactions). It does not perform any deduplication of records.

A split activity is used for segmentation. It divides a single target population into multiple distinct subsets based on specified criteria, rather than removing duplicate entries.

---

1. Adobe Experience League. (n.d.). Campaign Classic v7 Documentation: Deduplication.

Section: Workflows > Activities > Targeting activities > Deduplication.

Quote/Paraphrase: The documentation explicitly states

"The Deduplication activity lets you remove duplicates from the results of the upstream activities in the workflow." It further provides an example: "you can deduplicate on the email address or telephone number to send a single delivery per household." This directly supports using the deduplication activity on the email address field before a delivery.

2. Adobe Experience League. (n.d.). Campaign Classic v7 Documentation: Targeting activities.

Section: Workflows > Activities > Targeting activities.

Quote/Paraphrase: This overview page describes the purpose of various targeting activities. The description for Union confirms it "lets you group the result of several activities

" Split "lets you create subsets

" and Change dimension "lets you change the targeting dimension." None of these descriptions include functionality for removing duplicates based on a field value.

In Adobe Campaign Classic, delivery templates are used to pre-configure properties for new deliveries. The "Execution folder" is a specific property within a delivery template that dictates the folder where any delivery created from that template will be stored. By setting this property in the template, the practitioner ensures all related deliveries are automatically and consistently saved to the business-defined folder, fulfilling the requirement efficiently without manual intervention.

A. Define Routing within the delivery properties of each delivery template.

Routing defines the external account (e.g., SMTP server) used for sending the delivery, not the internal folder where the delivery instance is stored.

B. Move all deliveries manually into defined folders.

This approach is inefficient, prone to human error, and does not leverage the automation capabilities of delivery templates as requested for the "most effective" implementation.

C. Modify the delivery mapping to define the routing.

Delivery mappings link targeting and filtering dimensions to a delivery. They do not control the storage location (folder) of the delivery instance within the Campaign tree.

1. Adobe Campaign Classic v7 Documentation - Delivery templates:

Section: Platform > Templates > Delivery templates

Content: "Delivery templates let you define the main characteristics of a delivery and save them to be reused for future deliveries... All the parameters saved in the template will be duplicated in the deliveries created from it." This establishes that properties are inherited. The "Execution folder" is one such property configured in the delivery's properties tab

which is part of the template's configuration.

2. Adobe Campaign Classic v7 Documentation - Delivery properties:

Section: Get started with deliveries > Prepare and send a delivery > Delivery properties

Content: The "Properties" tab of a delivery allows the user to define its label

internal name

and the execution folder where it is created and stored. When a delivery is created from a template

this folder is pre-populated from the template's settings

automating the storage process.