Understanding Workflow Arguments
Workflow Arguments allow to pass information to a workflow. Each workflow (template) has a set of arguments. In general there are 3 categories of arguments:
- Mandatory arguments
- Trigger specific arguments
- Additional arguments
All workflows must have these arguments, even if those are not used inside the workflow itself. The values for this properties are automatically set. Normally there is no need to expicitly set them.
|ServiceRootAddress||String||The Service Root Address of the DPE Services.|
|User||String||The DigaSystem user used to execute the workflow.|
|Priority||Int32||Priority of the workflow. Default: 50.|
|CurrentWorkflowId||Int32||Current workflow id.|
|Creator||String||Optional, WorkflowServer >= 1.8.21|
These arguments are needed for proper inter-working with a specific trigger (e.g. Workflow Table Watcher, Folder Watcher or one of our application PlugIns).
|Arg_TableId||String||TableId of the entry, for which the workflow has been created|
|Arg_EntryId||Int32||EntryId of the entry, for which the workflow has been created|
|Arg_Event||String||"Created", "Renamed", "Manual", ...|
|Arg_File||String||Path and filename for which the workflow has been created|
|Arg_Subclips||String||List of marked 1...n subclip names|
|Arg_Frame||Int32||Current frame of video head, from begin of related entry|
|Arg_MarkIn||Int32||currently not used|
|Arg_MarkOut||Int32||currently not used|
|Arg_AudioChannelRouting||String||currently not used|
These arguments can be added for feeding the workflows business logic.
All names are allowed, using above mentioned ones and using arguments beginning with "Arg_" should be prevented.