Writeback tables run on Writeback workflows: a workflow groups the tables of one destination and starts them together, by hand or on a schedule. Use the Workflows view to reach a destination's workflows, run one, switch its schedule and follow its runs, without leaving Writeback.
The view has two lists on the left. Destination lists the destinations of Writeback; Workflows lists the workflows of the selected one. Drag the divider between the lists to change the split; the split is remembered.
Adding a destination creates its first workflow for you: one named after the destination, with (Standard) after the name. Imported tables start on it. To add another:
A destination can hold several workflows. Splitting its tables between them lets each group run on its own schedule. When you close the window, the Writeback tree and this list refresh.
Hover a workflow card to show its buttons.
Run now appears only with Execute WriteBack Workflow Objects, and only when the workflow has at least one table. If the workflow cannot start yet, the button is disabled and pointing at it reads Can’t run yet and explains what is missing. See Run a workflow by hand.
On the card, the power button turns the workflow's schedule on or off; its tooltip reads Turn schedule on or Turn schedule off. While the schedule is on, the card shows how often the workflow runs, such as Every day.
A schedule belongs to the whole workflow. Turning it off stops every table in that workflow from starting on its schedule. A table you run by hand still runs.
Select a workflow card and the right side shows its runs. The header above the runs names the destination and the selected workflow, and drops a (Standard) suffix from the workflow's name.
At the top of the left panel, switch the mode from Runs to Transfer to move tables between the workflows of one destination. Only fully mapped tables move, only within the same destination, and only into a workflow you may modify. The steps are on Transfer tables between workflows.
| To | You need |
|---|---|
| Open the Workflows view, with the button or Alt+4 | View WriteBack Workflow Objects |
| Use Add Workflow | Add WriteBack Workflows |
| Use Run now | Execute WriteBack Workflow Objects |
| Turn a schedule on or off, or edit a workflow | Modify WriteBack Workflows |
| Delete a workflow | Remove WriteBack Workflows |
Without Modify WriteBack Workflows, the pencil shows as View and the power button is disabled. Running a single table by hand uses Execute/Abort WriteBack Objects; see Synchronize a table and read the Sync Log.
Only destinations with at least one imported table are listed. Import a table first, see Import destination tables. Until a destination qualifies, the view reads No destinations ready.
Yes. Select the destination and click Add Workflow. Splitting a destination's tables across workflows lets each group keep its own schedule, and you can move tables between the workflows later, see Transfer tables between workflows.
New workflows start with their schedule on. To stop it, click the power button on the card; to change when it runs, click Edit and open Schedule Settings. For what a schedule needs before it starts a run, see Schedules and when a workflow starts.
No. A schedule belongs to the whole workflow, so turning it off stops every table in that workflow from starting on its schedule. To give some tables different timing, create another workflow for the destination and move those tables to it, see Transfer tables between workflows. A table you run by hand runs whenever you ask, see Synchronize a table and read the Sync Log.
Yes. It is an ordinary workflow of the Writeback type: it also appears on the Workflows screen, and its runs appear in Job runs. This view narrows the same workflows to one destination.
No. It shows the runs of the selected workflow only. Select another workflow to switch; to read the runs of all workflows together, open Job runs on the Workflows screen.
A Writeback workflow runs the tables assigned to it. A workflow with no tables has nothing to run, so no Run now button shows; put a table on it from the table's General step, see Configure a Writeback table. If its tables are not mapped yet, Run now is disabled; point at it to read Can’t run yet and the fix, then map a table on Map columns.
Yes. Once a run starts, it continues whether or not the page is open, and a scheduled run needs no page open at all. Open the view later, or follow the run in Job runs.