Setting Up Execution Options for Campaigns

You can select the default execution options for each campaign when you set up the campaign. After the campaign is loaded, you can modify the execution options for the associated campaign at any time.

To assign contact ownership, make sure that you select the appropriate Campaign Contact Ownership value, your default owners, the Contact editing flags, and an Siebel Assignment Manager rule group.

The following procedure shows how to set execution options for a campaign.

To set execution options for a campaign

Navigate to the Campaigns screen.
In the Campaigns list, click a campaign name.
Click the Design view tab.
In the Design link bar, click Execution Options or Execution Options - Advanced and complete the fields.
Note: Some fields exist only in the Execution Options - Advanced link. The Email Campaign fields exist only in the Execution options link.
Execution options fields are described in the following tables:

Assignment options. (See the following table.)
Collaboration options. (See second table in this topic.)
Delivery options. (See the third table in this topic.)
Load options (See the fourth table in this topic.)
Email campaign options (See the fifth table in this topic.)

The following table describes the assignment options for each Execution option field.

Field	Action
Assignment Rule Group	Required if you select Yes - Assignment Manager in the Campaign Member Ownership field. Use if you want Siebel Assignment Manager to assign the organization owner and position owner to contacts and prospects in the campaign. Select a rule group to apply to contacts in the campaign.
Campaign Member Ownership	Controls assignment of position owner and organization owner during the load process. Values are: No. You do not want to assign ownership. When you select this option, the Organization Owner and Position Owner fields remain empty on the campaign contacts and prospect records. Yes - Manually. When you select this option, the load process populates the Default Position Owner and Default Organization Owner to the Campaign History table (S_CAMP_CON) for the contacts and prospects in the load. After the load process, you can manually assign organization and position owners on the campaign contacts and prospect records. Yes - Assignment Manager. You want Siebel Assignment Manager to assign ownership based on Siebel Assignment Manager rule groups. The load process invokes the Siebel Assignment Manager engine at the end of the process to assign the campaign members based on the rules in the selected Assignment Rule Group.
Default Organization Owner	(Optional) Default value that is populated into the Default Organization Owner field during the load process when assignment is enabled (Yes - Assignment Manager or Yes - Manually). The list of organizations is restricted to the organizations associated with the campaign. After the value is populated, it can be updated if the assignment engine reassigns names. For more information, see Siebel Assignment Manager Administration Guide.
Default Position Owner	(Optional) Default value that is populated into the Default Position Owner fields during the load process when assignment is enabled (Yes - Assignment Manager or Yes - Manually). The list of positions is restricted to the Default Organization Owner organizations associated with the campaign. After the value is populated, it can be updated if the assignment engine reassigns names. For more information, see Siebel Assignment Manager Administration Guide.
Lock Campaign Team Assignment	Campaign managers sometimes create assignment rules that assign additional positions to the campaign team. This lock flag excludes this campaign from the rules, so that new team members would not be assigned.

The following table describes the collaboration options for each Execution option field.

Field	Action
Enable Contact Editing	Default is on (True). Clear the check box to prevent anyone from changing the owner fields and adding and deleting contacts. This flag controls the ability to edit the following fields on the campaign contact or prospect record: Contact Last Name Done Flag Organization Owner Prospect Last Name Position Owner In addition, when this value is True, the New and Delete buttons are available. Note: A contact can only be deleted by the Position Owner to whom it is assigned. The Delete button is unavailable to other users.
Enable Partner Editing of Contacts	Default is on (True). Clear the check box to prevent partners from editing the fields and using the buttons controlled by the Enable Contact Editing check box.
Enable Followup Actions	This value controls which buttons (Create Oppty, Create Order, Create Response, Script) are active in the Campaign agent views (Campaign Members). The following list describes the values: Create Opportunities. The Create Response and Create Oppty buttons are active. Create Orders. The Create Response and Create Order buttons are active. Create Responses. The Create Responses button is active. All. All buttons are active.
Enforce Approvals	When this option is active, the campaign cannot be launched unless the Approval Status for the campaign and its associated offers is Approved. You receive an error if you try to launch a campaign and the conditions are not met.
Control Campaign	This flag denotes that this campaign is meant to be used as a control group for a test and control program. Control campaigns are hidden from the outbound call center agent views (Campaign Members - Outbound), because control groups do not receive offer messages. Control Campaigns do appear in the Inbound version the Campaign Members view, because you want to be able to capture unsolicited responses.

The following describes the delivery options for each Execution option field.

Field	Action
Route Contacts	This flag controls whether or not campaign contacts are routed to mobile clients. By default all routing rules for campaign contacts are disabled.
Use Pregenerated Files	When this option is checked, the launch option uses the most recent list export file for the wave being launched. This option is useful if you have a short time to deliver all of your email, and you want to regenerate the list file before you launch the campaign. To generate an email list file or a list export file for other channels, navigate to the Campaigns screen, Execute, and then the List Distribution view.
Route Prospects	This flag controls whether campaign prospects are routed to mobile clients. By default all routing rules for campaign prospects are disabled.

Field

Action

Route Contacts

This flag controls whether or not campaign contacts are routed to mobile clients. By default all routing rules for campaign contacts are disabled.

Use Pregenerated Files

When this option is checked, the launch option uses the most recent list export file for the wave being launched. This option is useful if you have a short time to deliver all of your email, and you want to regenerate the list file before you launch the campaign.

To generate an email list file or a list export file for other channels, navigate to the Campaigns screen, Execute, and then the List Distribution view.

Route Prospects

This flag controls whether campaign prospects are routed to mobile clients. By default all routing rules for campaign prospects are disabled.

The following table describes the load options for each Execution option field.

Field	Action
Load Behavior	Controls what happens to the previous wave or load when the user opts to load the campaign again. The following is a list of choices: Overwrite Campaign History. Purges entire existing campaign history and creates a new load. Create New Wave. Creates an additional load or wave for the latest load. Add to Existing Wave. Finds the most recent good wave (not purged or suspended) and adds the campaign load members to the existing wave.
Allow Repeated Contacts with Load	Controls whether a specific contact or prospect ID can appear more than one time in the same load in the campaign for the same treatment. The unique index in S_CAMP_CON (campaign members or contacts table) is based on Campaign ID, Load Number, Contact/Prospect ID, Token Number and Treatment ID. By default the application always populates a value of 1 in the column, so that uniqueness is driven by the contact and campaign. However, if you turn off this option, then the token number becomes a running number so there is no uniqueness enforced at the table level. This scenario is typical in certain industries such as Life Sciences where there is a many-to-many relationship between contacts and accounts. For example, in the pharmaceutical industry, doctors are affiliated with multiple hospitals and the pharmaceutical companies send offers to all of their active addresses in the same campaign.
Source Code Format	The source code format to be used to generate source codes for the campaign. If the format is also associated with the program level, then the value is carried over when a campaign is created on the program flow.
Generate Source Codes during Load	Generates source codes for waves that have not been launched at the completion of the campaign load. If the option is disabled, then you must manually generate the source codes using the Generate Source Codes menu option in the campaign screen.
Capacity Limit per Load	If this value is set to a value greater than 0 (zero), then the campaign load stops inserting campaign members as soon as the capacity is reached. For example, you could limit the campaign size to no more than 1000 people for each load.
Max Errors	This setting controls when the campaign load (EAI) process aborts. The load process tabulates the number of rejected records that were not inserted due to errors (bad data and so on). After the Max Errors value is passed, the campaign load process aborts. When this value is 0 (zero), all inserts and updates for the batch are backed out.
Pre-Load Task	A workflow can be associated that executes prior to Campaign Load. This can be used to execute dependent segments, create associated saved result sets, or call a third-party engine to modify existing data prior to segment execution. Available workflows in the picklist are drawn from a workflow group called Marketing Custom Workflows. You can customize these workflows to add your own validation or business logic.
Post-Load Task	If you are manually executing a campaign, then you can create a post-load task that executes a custom workflow immediately after loading the campaign if, for example, you want to employ an optimization engine to optimize the loaded target audience for the launch process. Available workflows in the picklist are drawn from a workflow group called Marketing Custom Workflows. You can customize these workflows to add your own validation or business logic. If a campaign is scheduled to execute automatically, then you cannot run post-load tasks.
Post-launch Task	A workflow can be executed immediately after launching a campaign. This can be used to allow a custom process to transpose the final data set before the vendor picks up the file. Available workflows in the picklist are drawn from a workflow group called Marketing Custom Workflows. You can customize these workflows to add your own validation or business logic.

The following table describes the execution options for email campaigns.

Field Action

Field	Action
Save and Send	For email campaigns, this flag controls whether or not a copy of each email sent to a campaign contact as part of the campaign is saved to a file. If you select the Save and Send option, then a copy of each email is saved as a .txt file and is assigned a name, using the format SEMA-CR-recipient_id_email.txt, where recipient_id is the contact Id. By default, copies of emails sent to contacts as part of a campaign are not saved.
Destination Directory	If you select the Save and Send option, then enter the full path to the directory where you want to save copies of the emails sent to campaign contacts, for example, `D:\esd`. The Email Sending Daemon creates a unique subdirectory within the directory you specify that contains all the emails sent for an individual campaign, and it assigns a name to the subdirectory by combining the campaign task Id and Wave Id with the time the email-send request was submitted (in nanoseconds). For example: `D:\esd\42-7XA4D_42-7XBJ9_512151790974819`

Save and Send

For email campaigns, this flag controls whether or not a copy of each email sent to a campaign contact as part of the campaign is saved to a file.

If you select the Save and Send option, then a copy of each email is saved as a .txt file and is assigned a name, using the format SEMA-CR-recipient_id_email.txt, where recipient_id is the contact Id.

By default, copies of emails sent to contacts as part of a campaign are not saved.

Destination Directory

If you select the Save and Send option, then enter the full path to the directory where you want to save copies of the emails sent to campaign contacts, for example, D:\esd.

The Email Sending Daemon creates a unique subdirectory within the directory you specify that contains all the emails sent for an individual campaign, and it assigns a name to the subdirectory by combining the campaign task Id and Wave Id with the time the email-send request was submitted (in nanoseconds). For example:

D:\esd\42-7XA4D_42-7XBJ9_512151790974819

Note: To use the Save and Send functionality, you must install Email Marketing Server build 8.1.1.2 [610] - EMS[625] or later. Email Marketing Server can be downloaded from My Oracle Support.