A process consists of a definition record and a record per activity which is called an “Action template”.
A run consists of a definition record and a record per activity, which is called an “Action”.
One flow can be used by multiple activities.
An action is always assigned to either a role or an user.
The process definition record consists of the following metadata:
- A unique ID
- An abbreviation
- If it is an active process or not
- A description
- A title
- A link to more information
- The unique ID of its parent process
- Retention period information: Minimum, Maximum, Unit
- The role needed to start a run
- If the process is a subprocess or not
- A version
The action template record consists of the following metadata:
- A unique ID
- If it is an active action template or not
- A link to another app which displays a custom form
- The checks to perform on the fields
- A description
- A title
- The form definition
- A link to more information about the action
- The unique ID of the related process
- The process step of the related process
- The select values for the fields of type “select”
A run record consists of the following metadata:
- A unique ID
- If it is an active run or not
- The timestamp the run was closed
- The timestamp the run was created
- An identifier for the run
- The email address of the account that started the run
- The display name of the account that started the run
- The User Principal Name (UPN) of the account that started the run
- The role the user had when starting the run
- The email address of the user that started the run
- The display name of the user that started the run
- The User Principal Name (UPN) of the user that started the run
- The timestamp the run metadata was updated the last time
- The abbreviation of the related process
- The title of the related process
- The unique ID of the related process
- The version of the related process
- An unique ID of the run
- The status of the run
An action record consists of the following metadata:
- A unique ID
- An abbreviation
- The unique ID of the related action template
- If it is an active action or not
- A link to another app which displays a custom form
- The checks to perform on the fields
- The timestamp the action was closed
- The timestamp the action was created
- A deadline timestamp
- A description
- A title
- The form definition
- The form values
- The timestamp the action metadata was updated the last time
- A link to more information about the action
- The abbreviation of the related process
- The title of the related process
- The unique ID of the related process
- The process step of the related process
- The version of the related process
- The role the action is assigned to
- The unique ID of the related run
- The select values for the fields of type “select”
- The status of the action
- The mail address of the user assigned to the action
- The display name of the user assigned to the action
- The User Principal Name (UPN) of the user assigned to the action
A process can have multiple process managers. A user can be process manager of multiple processes.
An action can be a manual action or an automated action.
A manual action is a form that must be submitted by an end user.
An automated action is an form that is automatically filled in and submitted by a flow.