Assignment Rule Group

Required if you select Yes - Assignment Manager in the Campaign Member Ownership field. Use if you want 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 are left 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 all 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 Assignment Manager to assign ownership based on Assignment Manager rule groups. The load process invokes the 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 automatically 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 might 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 automatically 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 might 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.

Enable Contact Editing

Default is on (True). When this option is checked, users on the campaign team or group will have the ability to add an delete contacts from the campaign list.

Enable Contact Editing

Default is on (True). Clear the check box if you want to prevent any one 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:

• Done Flag
• Contact Last Name
• Prospect Last Name
• Organization Owner
• Position Owner

In addition, when this value is True, the New and Delete buttons are available.

Enable Partner Editing of Contacts

Default is on (True). Clear the check box if you want to prevent partners from editing the fields and using the buttons controlled by the Enable Contact Editing check box.

Enable Partner Editing of Contacts

When this option is checked, partners associated to the campaign (as organizations) will have the ability to add an delete contacts from the campaign list.

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 all its associated offers is Approved. You will 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 should 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.

Enable Contact Editing

When this option is checked, users on the campaign team or group will be able to add an delete contacts from the campaign list.

Apply Wave Lags to Export Files

By default all the exported list files for a wave are sent to the vendor on the launch date. If this option is enforced and you use Wave % splitting and wave lag option in the program schedule view, then the lag days are applied to the file. The files for delayed waves will not be sent until the launch date plus the number of lag days is reached.

Route Contacts

This flag controls whether campaign contacts should be routed to mobile clients. By default all routing rules for campaign contacts are disabled. To reactivate these rules, customers must consult Siebel Expert Services because there will be a performance impact for client synchronization (campaigns have a lot of potential data).

Route Prospects

This flag controls whether campaign prospects should be routed to mobile clients. By default all routing rules for campaign prospects are disabled. To reactivate these rules, customers must consult Siebel Expert Services because there will be a performance impact for client synchronization (campaigns have a lot of potential data).

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 once in the same load in the campaign.

The unique index in S_CAMP_CON (campaign members or contacts table) is based on Campaign ID, Load Number, Contact/Prospect ID, and Token Number. 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, 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 pharma companies send offers to all of their active addresses in the same campaign.

Source Code Format

The source code format that will be used to generate source codes for the campaign. If the format is associated to the program level too, the value should be carried over when a campaign is created on the program flow.

Generate Source Codes during Load

This option automatically generates source codes for all waves that have not been launched at the completion of the campaign load. If the option is disabled, you need to 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), the campaign load will stop inserting campaign members as soon as the capacity is reached. For example, you could limit the campaign size to no more than 1000 people per load.

Max Errors

This setting controls when the campaign load (EAI) process should abort. 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.