Adobe Campaign comes with a set of built-in technical workflows. Technical workflows execute processes or jobs, scheduled on a regular basis on the server.
These workflows perform maintenance operations on the database, leverage the tracking information in the delivery logs, create recurring campaigns, and more.
↗️ The full list of technical workflows is detailed in Campaign Classic v7 documentation
In addition to these technical workflows, Campaign v8 relies on specific technical workflows to manage data replication.
These technical workflows are available from the Administration > Production > Technical workflows > Full FFDA replication node of Campaign Explorer. They must not be modified.
If needed, you can launch data synchronization manually. To perform this, right-click on the Scheduler activity and select Execute pending task(s) now.
Some built-in tables are replicated from Campaign local database to Snowflake Cloud database through dedicated workflows described above.
Understand which databases Adobe Campaign v8 uses, why data is being replicated, which data is being replicated and how the replication process works.
Replication policies are based on the size of the tables. Some tables will be replicated in real-time, some others will be replicated on hourly basis. Some tables will have incremental updates when others will be replaced.
In addition to the built-in Replicate Reference Tables technical workflow, you can force data replication in your workflows.
nlserver ffdaReplicateStaging -stagingSchema -instance:acc1
↗️ Learn how to get started with worflows in Campaign Classic v7 documentation
💡 Access data retention periods in this section