List of Campaign Classic options configuring-campaign-options
The Administration / Platform / Options node allows you to configure Adobe Campaign options. Some of them are built-in when installing Campaign, and others can be added manually when needed. Available options vary according to the packages installed with your instance.
-
Options not listed in this page are internal only and must not be modified.
-
Modifying or updating Adobe Campaign options can be performed by experts users only.
Delivery delivery
Lets you allow the operator in charge of the delivery to confirm the send, if a specific operator or group of operators is designated for starting a delivery in the delivery's properties.
To do this, activate the option by entering "1" as the value. To deactivate this option, enter "0".
The send confirmation process will then function as default: only the operator or group of operators designated for the send in the delivery properties (or an administrator) will be able to confirm and carry out the send. See this section.
The option value must correspond to the name of the schema which matches the external recipient table.
"You are receiving this message because you have been in contact with `Organization` or an affiliated company. To no longer receive messages from `Organization`
This option is used by the operationMgt technical workflow when counting the number of running deliveries.
It allows you to define the number of days above which deliveries with inconsistent status will be excluded from the count of running deliveries.
By default, the value is set to "7", meaning that inconsistent deliveries older than 7 days will be excluded.
It is the default value of email deliveries when the URL is not specified in the routing definition.
Resources resources
For more on HTML and Text contents generation, refer to this section.
For build versions <= 5098, we use the URL of the images that were uploaded onto the instance.
For build versions > 5098, we use instead the delivery's public URL or the XtkFileRes_Public_URL option's URL.
Campaign & workflow management campaign-e-workflow-management
Security security
Message Center message-center
JavaScript library to be personalized for enriching events. Must contain the implementation of these two functions:
-
enrichRtEvents(aiEventId); : enriches and saves events in the database (where aiEventId corresponds to the table of real time events processed).
-
enrichBatchEvents(aiEventId); : enriches and saves events in the database (where aiEventId corresponds to the ID table of batch events processed).
JavaScript library to be personalized for routing events. Must contain the implementation of these two functions:
-
dispatchRtEvent(iEventId); : returns the internal name of the transactional message selected to process the real time event (where iEventId corresponds to the ID of the real time event processed).
-
dispatchBatchEvent(iEventId); : returns the internal name of the transactional message selected to process the batch event (where iEventId corresponds to the ID of the batch event processed).
Database database
Lets you define the delay after which broadlog are erased from the database.
This option is automatically created once the delay is modified within the interface. If you modify the value from the options list, it should be expressed in seconds.
Lets you define the delay after which the event history is erased from the database.
This option is automatically created once the delay is modified within the interface. If you modify the value from the options list, it should be expressed in seconds.
Lets you define the delay after which events are erased from the database.
This option is automatically created once the delay is modified within the interface. If you modify the value from the options list, it should be expressed in seconds.
Lets you define the delay after which the event statistics are erased from the database.
This option is automatically created once the delay is modified within the interface. If you modify the value from the options list, it should be expressed in seconds.
Lets you define the delay after which propositions are erased from the database.
This option is automatically created once the delay is modified within the interface. If you modify the value from the options list, it should be expressed in seconds.
Lets you define the delay after which the quarantines are erased from the database.
This option is automatically created once the delay is modified within the interface. If you modify the value from the options list, it should be expressed in seconds.
Lets you define the delay after which recycled deliveries are erased from the database.
This option is automatically created once the delay is modified within the interface. If you modify the value from the options list, it should be expressed in seconds.
Lets you define the delay after which rejects are erased from the database.
This option is automatically created once the delay is modified within the interface. If you modify the value from the options list, it should be expressed in seconds.
Lets you define the delay after which tracking logs are erased from the database.
This option is automatically created once the delay is modified within the interface. If you modify the value from the options list, it should be expressed in seconds.
Lets you define the delay after which tracking statistics is erased from the database.
This option is automatically created once the delay is modified within the interface. If you modify the value from the options list, it should be expressed in seconds.
Lets you define the delay after which visitors are erased from the database.
This option is automatically created once the delay is modified within the interface. If you modify the value from the options list, it should be expressed in seconds.
Lets you define the delay after which workflow results is erased from the database.
This option is automatically created once the delay is modified within the interface. If you modify the value from the options list, it should be expressed in seconds.
Lets you affect Unconditional Stop behavior on all the workflows and PostgreSQL database queries according to the following potential values:
-
0 – default: stops workflow process, no impact on the database
-
1 - pg_cancel_backend: stops workflow process and cancels query in the database
-
2 – pg_terminate_backend: stops workflow process and terminates query in the database
See Creating and configuring the database.
See Creating and configuring the database.
See Creating and configuring the database.
See Creating and configuring the database.
During migration, the tree structure is automatically reorganized based on the new version standards.
This option allows you to disable the automatic migration of the navigation tree. If you use it, after migration you will have to delete obsolete folders, add the new folders and run all necessary checks.
-
Data type: Integer
-
Value (text) : 1
This option should only be used if the out-of-the-box navigation tree has undergone too many changes.
{Build number}:{mode: pre/post/...}:{The 'lessThan'/'greaterOrEquelThan' where error occurred + sub-step}
Integration integration
This option is used when importing data from a third-party system through a CRM connector. Enabling the option lets you collect only objects modified since the last import. This option has to be manually created and populated as below:
-
Internal name : LASTIMPORT_<%=instance.internalName%>_<%=activityName%>
-
Value (field) : date of the last import, with the yyyy/MM/dd hhss format.
See this section.
See this section.