Form Settings
(1) This checkbox must be set so that files can be added to the workflow via this form. But see also section Rights for Workflow Files and (2) and (3).
(2) Even if (1) is set, files in this form can be seen in the add-on module DataCockpit only by a DataCockpit user if he has the role selected here. Note: See also workflow variable VAR_SYS_WF_ATTACHMENT_ACCESSLIST (to override).
(3) The number of files set here must at least be assigned to the workflow job, in forms or with function attach file to workflow(a,b,c,d,[e]), in order to successfully change to the next state.
(4) The _data users (login name) who can see this form. Note: See also function change permission of workflow-form(a,b,c,d), REST operation dump.
(5) DataCockpit users with this role can see this form. Note: See also function change permission of workflow-form(a,b,c,d) und REST operation dump and workflow variable VAR_SYS_WF_ACCESSLIST (to override).
(6) All existing transitions of the state (to which this form belongs) are automatically checked. If this option is not set, the transition to the subsequent state must be selected manually in the form (→ see following section).
(7) Email notifications can be sent.
(8) A variety of form components are available via the context menu.
(9) Shows how the form looks at runtime.
Form in GUI
The following is how a form of a running workflow job is displayed. You can open forms in the following places (if you have the appropriate rights).
Control Center → Jobs → Workflows
Start → My tasks
Pinboard → My tasks and → Active workflows
DataCockpit → Tab Workflows
(10) If option (6) is not set, the subsequent state can be selected manually here in the form. For orientation use (11). If (6) is set, then the subsequent state is searched for automatically.
Selecting a subsequent state means that the transition leading to this subsequent state will be checked after clicking (12). Note: The transition is shown as a tooltip of a state and directly after you select a state.
If the check is successful, the transition (and actions set there) is executed and a change to the subsequent state takes place. If the check is not successful, the transition will not be executed and there will be no state change.
(11) Here you can see the diagram of the workflow, which is helpful when selecting a subsequent state (10). Note: Not displayed in the DataCockpit module.
(12) When you click this button, the transition check is started (i.e. the attempt to change to a subsequent state).