The Workflows page lists the technical workflows and their status.
The integration application comes with three workflows:
Microsoft Dynamics 365 to Campaign
Campaign to Microsoft Dynamics 365
Opt-out statuses (e.g., denyList) can be synchronized from Microsoft Dynamics 365 to Adobe Campaign or from Adobe Campaign to Microsoft Dynamics 365. The data can also by synchronized bidirectionally (i.e. data flows in both directions). Learn more.
It is strongly recommended that you stop the Microsoft Dynamics 365 to Campaign workflow before publishing changes to either Adobe Campaign Standard or Microsoft Dynamics 365. These changes include updates to resources/entities (and their associated fields), links, identifier columns, etc… that are currently in use by the integration. Failure to do so could lead to data loss and/or the workflow stopping unexpectedly.
This integration application first reads in data and then writes data to the destination. The Backlog column indicates the number of records that have been queued and are waiting to be written. This value is expected to grow when you have a large amount of data to process (e.g., you are running the integration for the first time, you are replaying the data, etc.).
If your Microsoft Dynamics 365 and/or Campaign records are not updating, you should first check to see if there is a large number of records waiting to be written to the destination.
The Status column indicates the state of the background processes associated with the workflow. Possible values are:
Possible actions are listed below.
Edit: Clicking the pencil icon will send you to another page that will allow you to make updates to the workflow. Keep in mind that any changes you make will NOT take effect until you stop the workflow and then restart it.
Start: A Start button requests that a stopped workflow be started. This button will only appear when the processes associated with the workflow are currently stopped. The processes will first change to “STARTING” and then to “RUNNING”. The data associated with the workflow will not start synching until the workflow is in a “RUNNING” state.
The start button is a toggle. If the workflow processes have been started already, the button will change to a Stop button.
Stop: A Stop button requests that a running workflow be stopped. This button will only appear when the processes associated with the workflow are currently running.
When you edit a workflow, your updates are NOT immediately incorporated into the running processes’ rules, until you stop the workflow and then click the Start button. Then your updates are incorporated into the running processes (once the process returns to a RUNNING state).
A warning indication is added to the Stop button to let you know when you have (a) made updates to workflow, but (b) have not done a Stop/Start of this workflow.