Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
en:extensions:workflowdesigner:tasks:flow:auth-request [2014/01/01 16:43] swarnat created |
en:extensions:workflowdesigner:tasks:flow:auth-request [2014/06/30 17:40] (current) swarnat [Summary Page] |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| {{ :en:extensions:workflowdesigner:tasks:permission.png?nolink|}} | {{ :en:extensions:workflowdesigner:tasks:permission.png?nolink|}} | ||
| - | This task allows to stop an automatic workflow and manually choose the path, the record should take. | + | The Authorization Request could be used to integrate a manually check of the current situation into your workflow. |
| + | If the execution will be arrive the block, it will be paused until a user makes a decision about the next actions. This break could take hours,days or weeks. | ||
| <WRAP tip> | <WRAP tip> | ||
| === Example === | === Example === | ||
| - | this allows to check a record, before an email will be send* | + | this allows to check a record, before an email will be send |
| </WRAP> | </WRAP> | ||
| You could use three different output points for this task to handle three different decisions. (Default: ok/rework/decline) | You could use three different output points for this task to handle three different decisions. (Default: ok/rework/decline) | ||
| - | The text on this task could be changed easily in the configuration. | + | This task must be connected to one/multiple User CRM Object, because the authorization request is bind to one/multiple person/s to allow checks by superior or chief. Only one user needs to set the decision and will see if other users already process an entry. |
| + | |||
| + | {{ :en:extensions:workflowdesigner:tasks:flow:authconfiguration.png?300|}} | ||
| + | |||
| + | In the configuration you could set an individual background color for this task, which will be shown on the summary page. Also you could define an info for the user, which you get, if you hold the mouse on this record on the summary page. | ||
| + | |||
| + | The option **run direct after confirmation** will define the execution time after the user confirm the process. | ||
| + | If you enable this checkbox, the workflow will be directly continued in the moment the user press the button. | ||
| + | In this situation the user have to wait, until the Workflow is finished. | ||
| + | |||
| + | If you don't enable this option, the workflow will be continued during the next execution of the workflow. | ||
| + | |||
| + | Also you could define the labels of the 3 buttons on the summary page. | ||
| + | The default ones will be translated in every supported language. | ||
| + | |||
| + | But you you could define your own labels if you want set different actions on the three buttons. | ||
| + | |||
| + | ==== Summary Page ==== | ||
| - | This task must be connected to an User CRM Object, because the authorization request is bind to one/multiple person/s to allow checks by superior or chief. Only one user have to set the decision. Probably later a more individual handling will be integrated. | + | You reach this authorization page over the navigation, like every other module. There will be a link "Workflows" |
| - | You reach this authorization page over the navigation, like every other module. There will be a link "Workflow2" | + | {{:en:extensions:workflowdesigner:tasks:flow:documentation2.png|}} |
| + | //Here you see two records waits for a confirmation. The first record already was process and will be continued during next cronjob. You could modify the decision until this moment.// | ||