| ... |
... |
@@ -1,5
+1,13 @@ |
| 1 |
1 |
{{content/}} |
| 2 |
2 |
|
|
3 |
+{{figure image="workflow_overview_en.png"}} |
|
4 |
+Dialog for configuring the workflow: (1) On the left users can find the list of states and their actions. (2) Right next to it there is the configuration screen for the selected state or action. |
|
5 |
+{{/figure}} |
|
6 |
+ |
|
7 |
+Workflow processing allows you to perform certain [[actions>>Formcycle.UserInterface.MyForms.WorkflowProcessing.Actions.WebHome]] such as sending mails, generating PDF files or making custom HTTP requests to external web services, depending on the current state of the form. When a form has been submitted, it takes on the system state //Received// automatically. State transitions are possible either by certain actions, or they can be performed by users in the inbox. |
|
8 |
+ |
|
9 |
+The workflow configuration dialog can be accessed by clicking the appropriate button {{ficon name="workflow-fill"/}} in the [[form menu>>doc:Formcycle.UserInterface.MyForms.WebHome||anchor="form_menu"]]. |
|
10 |
+ |
| 3 |
3 |
== Workflow processing |
| 4 |
4 |
|
| 5 |
5 |
When the user submits a form, a new form record will be created. Initially, it will start in the special system state //Received//. Additional states and custom actions can be added in this menu. A state transition may be triggered either by the system or manually by a user. Furthermore, a state transition can also be triggered after the forms has been idle for a certain amount of time by setting up a timed state transition. |