Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
devel:documentation:workflows:dev:workflow [2018/11/14 13:16] kucerar json example |
devel:documentation:workflows:dev:workflow [2021/06/21 12:47] husniko |
||
---|---|---|---|
Line 15: | Line 15: | ||
=====Design of process===== | =====Design of process===== | ||
- | Design of workflow process is realized with XML in format BPM 2.0. It is very helpful to use Activiti Designer. It is [[http:// | + | Design of workflow process is realized with XML in format BPM 2.0. It is very helpful to use Activiti Designer. It is [[http:// |
+ | A manual could be found [[https:// | ||
**Sample of Activiti process in IDE Eclipse plugin:** | **Sample of Activiti process in IDE Eclipse plugin:** | ||
Line 236: | Line 237: | ||
* **permissions** - Defines required permissions, | * **permissions** - Defines required permissions, | ||
* **skipValidation** - If you not used this attribute the behavioral will same as if you set it to false. When you set it to true then the validation of form(userTask) will be ignored. | * **skipValidation** - If you not used this attribute the behavioral will same as if you set it to false. When you set it to true then the validation of form(userTask) will be ignored. | ||
+ | * **reasonRequired ** - This property set to true enforces decision reason to be provided. | ||
===From properties=== | ===From properties=== | ||
Line 393: | Line 395: | ||
</ | </ | ||
</ | </ | ||
+ | | ||
+ | | ||
+ | | ||
+ | ===Setting solver note message - decision reason=== | ||
+ | The task solver is able to set a reason of the decision or any other note to the solved task. The text area serving to this purpose is part of the confirmation modal window which appears, when user clicks the decision button. Display of this modal window (see in the picture below) has to be enabled by '' | ||
+ | |||
+ | {{ : | ||
+ | | ||
+ | When the task is solved the solver' | ||
+ | | ||
+ | | ||
+ | {{devel: | ||
+ | | ||
+ | | ||
+ | **Configuration** | ||
+ | |||
+ | There exist several ways how to configure solver notes. The general approach is the setting from workflow. Workflow bpmn20 file contains the following section which is used for configuration of decision buttons in userTask. The section looks like this: | ||
+ | |||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | |||
+ | <note tip> | ||
+ | To avoid the need of workflow modification and an easy configuration of the most common decisions i.e. '' | ||
+ | |||
+ | '' | ||
+ | '' | ||
+ | </ | ||
+ | |||
+ | If decision button '' | ||
+ | In most cases the userTask uses two decision types: '' | ||
+ | |||
+ | |||
+ | |||
=====Custom task detail===== | =====Custom task detail===== | ||
Line 494: | Line 534: | ||
Sending notification can be turnd off in each UserTask by setting Form property **sendNotification**. Example of this setting: | Sending notification can be turnd off in each UserTask by setting Form property **sendNotification**. Example of this setting: | ||
- | {{ :navrh:wf001.png |}} | + | <code xml> |
+ | < | ||
+ | id=" | ||
+ | type=" | ||
+ | expression=" | ||
+ | writable=" | ||
+ | </ | ||
+ | </ | ||
Type of variable have to be **configuration**. It is FormType, which is not propagated to frontend. ID or name have to be **sendNotification**. It does not matter even in case of **idm.sec.core.wf.notification.send** is setted to false, because form property **sendNotification** has **higher priority**. | Type of variable have to be **configuration**. It is FormType, which is not propagated to frontend. ID or name have to be **sendNotification**. It does not matter even in case of **idm.sec.core.wf.notification.send** is setted to false, because form property **sendNotification** has **higher priority**. | ||