Workflows Table
The Workflows table is a special table with a predefined set of fields. You can add, modify, and delete workflow records just like the records of a normal table. Each record in the Workflows table corresponds to a single workflow.

The fields of each record of the Workflows special table are listed in the table below. The last four fields in the table are read-only.

When MDM autolaunches a job based on a max records or max time threshold, you should expect up to a five-minute delay before the job is actually launched, since the workflow thread sleeps and wakes up every five minutes.
For an automatically generated and immediately launched job (such as those from the Record Update and Record Add triggers), if the owner is set to [Launcher], the launcher will be [System]. The user Admin can assume and delete those jobs owned by [System].
You cannot save a workflow when the following three conditions are all true:
§ Checkout=Yes
§ Owner=Launcher
§ Trigger action is Record Add, Record Update, or Record Import.
This is because with those triggers, [System] is the creator and launcher of the job but is not a real user and cannot check out records.
Field |
Description |
Name |
The workflow name |
Code |
The workflow code |
Description |
The workflow description |
Table |
The table on which the workflow operates |
Workflow |
The Microsoft Visio workflow object itself |
Owner |
The user who owns the workflow |
Active |
Whether the workflow is active (Yes/No) |
Trigger Actions |
The actions that trigger the workflow: · Manual · Record Add1 · Record Import2 · Record Update1,3,4 |
Autolaunch |
Whether or not to automatically launch the workflow job: ● None ● Immediate ● Threshold |
Max Records |
The maximum number of records that can be added to the workflow before it is launched automatically. |
● Autolaunch=Threshold ● 0 means do not autolaunch based on record count |
|
Max Time |
The maximum amount of time that the workflow can remain unlaunched before it is launched automatically. |
● Autolaunch=Threshold ● 0 means do not autolaunch based on unlaunched time |
|
Created By |
The user who created the workflow. |
Created |
The date and time the workflow was created. |
Modified By |
The user who last modified the workflow. |
Modified |
The date and time the workflow was last modified. |
1 Only one workflow is triggered by this action
2 Workflow checkout occurs before record update (update applied to checked out record)
3 Workflow checkout occurs after record update (update applied to original record)
4 Modifying records already in a workflow job will not trigger an additional workflow job.

The Owner of a job is able to do the following:
§ He sees in its task queue every instance of every step that is available to or received by every other user.
§ He is the only user who can delete a job that is not yet complete or take over performing a step.
§ Depending upon the settings of the Start step, he may be the only user who is permitted to send the job from one process step to the next or split a job.
For Autolaunch=Threshold, the workflow thread wakes up every five minutes and launches the job if the number of records in the unlaunched job is greater than Max Records; and/or the time since the unlaunched job was created is greater than Max Time.