Skip to main content
Skip table of contents

Configuring Workflow Table Watcher

Workflow Table Watcher is the component that creates workflow instances based on DigaSystem table changes. It is part of Workflow Server and based on the SAF platform, also see Introduction to SAF.

Workflow Table Watcher is configured using the SAF Administration application which can be found in the previously specified installation folder:

Also see Introduction to SAF Administration.

Adding a New Watch Task

  1. After starting SAF Administration

  2. Navigate in the tree of Registered Servers and Modules to WorkflowServer\WorkflowTableWatcher\Module specific properties:

  3. For trying out new configurations you can enable different test modes.
    Test will only create log messages (without changing any state). As soon as you switch back to Standard workflows will be triggered for the stuff tested.
    Test + Remove will create log messages and update state. When you switch back to Standard mode no workflows will be created for the changes in test mode.

  4. Click Add to open the Watch Table Properties for a new task:

    If DigaSystem tables are deleted or renamed you have to adapt the DigaSystem parameters defining these tables.

    Tables that are used in the TableWatcher config but are not existing in DigaSystem table base configuration are visualized like "<<tablename>>" in the table list and must be removed manually by an administrator.

  5. Fill out the tab Scanner properties:

    DescriptionA short description that is displayed in the task list
    IntervalTime interval for checking for changes
    Selected TablesMonitored DigaSystem tables
    FilterA filter limiting the creation of workflows to conditions of entry metadata, see XmlFilter Syntax And Examples
    EventSpecify the monitored event
    On first start
  6. Fill out the tab Workflow properties:

    NameName of the created workflow instance, see also Understanding Workflow Names/Titles
    TypeWorkflow Type (= Template)
    ParameterArgument List, see also Understanding Workflow Arguments
    AccountOptional: the credentials used to execute the workflow. We recommend to use credentials inherited from SAF server
JavaScript errors detected

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

If this problem persists, please contact our support.