Skip to main content
Skip table of contents

TableSync

Workflows described in sub pages:

Page content:

Watching DigaSystem Tables in WFS v2.x

Workflow instance is created in workflow queue. No need for TableWatcher to wait until it is finished

Example: PreProductionAudio

image-20250423-085831.png

Even workflows are fire-and-forget we have to keep track of the state on source table side to decide which event to trigger

image-20250423-085801.png

Many use cases can be covered but not a sync between 2 DigaSystem tables

image-20250423-090045.png

Aligning DigaSystem Tables in WFS v3.x

TableWatcher 3.x introduces new optional features: Sync Context option.

This feature allows to cover alignment of tables.

To support this we need to remember the relationship between source and target entries, therefore TableWatcher has to wait for the workflow to finish.

We recommend to run a dedicated TableWatcher for tasks using Sync Context, so tasks that are not using Sync Context are not blocked/delayed.

image-20250423-090513.png

New workflow TableSync_MasterSlave

image-20250423-090813.png

TableSync_ScheduledFullCompare to replace DigAlign

As an alternative to TableWatcher driven alignment you can use the scheduled workflow TableSync_ScheduledFullCompare to achieve a more DigAlign-alike behavior

image-20250423-091436.png

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close