Understanding Workflow Names/Titles

Workflow Name/Title is Influencing Behavior

When instantiating a workflow you can choose a title for the instance. Titles influence the concurrency behavior of workflows. A workflow is only instantiated when no other workflow of same type and title is already scheduled or running. If you have workflows that should not run at the same time you can name them accordingly. Prefixing your workflow title with "!0" will skip the concurrency check for this workflow.

Examples:

"ProcessVideo %tableid% %entryid%" : workflow for a specific table+entry should not be instantiated twice at the same time
"Mytest %guid%" : workflow that may be instantiated without restriction
"!0 %tableid% %entryid%": workflow that may be instantiated without restriction

Symbolic Variables

Symbolic variables (placeholders) can be used in workflow titles.

TW = WorfklowTableWatcher, FW = WorkflowFolderWatcher, WS = WorkflowScheduler

Symbolic Variable	Available In	Description
%guid%	All	Globally unique ID
%id%	All	Internal counter, not unique!
%event%	TW	"Created", "Updated", "Deleted"
%event%	FW	"Created", "Changed", "Deleted", "Renamed"
%tableid%	TW	Unique table id, e.g. "IWO\DBMTest"
%tablealias%	TW	Table alias, e.g. "DBM-Test"
%entryid%	TW	Entry id, e.g. "12345678"
%entry.XXX%	TW	XXX can be any metadata fieldname of the entry which triggered the workflow. e.g. %entry.Title% will be replaced by the entry title
%filter%	FW	Filter pattern, e.g. "*.wav"
%filename%	FW	Filename (without directory information)

Examples:

Nr	Example
1	TW: "PreProduction %tableid% %entryid%"
2	FW: "DaletImport %filename%"
3	WS: "Periodic Check %guid%"