Plugin installed incorrectly. Rename plugin directory 'swiftmail.backup' to 'swiftmail'.
en:software:tim:stencils
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
en:software:tim:stencils [2015/06/29 15:22] jan.mayer |
en:software:tim:stencils [2021/07/01 09:52] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | |||
| ====Overview of symbols BPMN 2.0==== | ====Overview of symbols BPMN 2.0==== | ||
| ^ Symbol ^ Name ^ Description ^ | ^ Symbol ^ Name ^ Description ^ | ||
| - | | {{ software:tim:pool.png?400 }} | Pool | A pool comprises a higher-ranking unit of organisation, e.g., a company. | | + | | {{ software:tim:pool.png?400 }} | Pool | A pool comprises a higher-ranking unit of organisation, e.g. a company. | |
| - | | {{ en:software:tim:pool_lanes.png?400 }}| Swimlane | Swimlanes subdivide the pool into subordinate units. | | + | | {{ en:software:tim:pool_lanes.png?400 }}| Swimlane | Swimlanes divide the pool into subordinate units. | |
| | {{ en:software:tim:activity.png }} | Activity | This symbol represents an activity within a process. | | | {{ en:software:tim:activity.png }} | Activity | This symbol represents an activity within a process. | | ||
| - | | {{ en:software:tim:send.png }} | E-mail / Send | This symbol enables automatic sending of e-mails directly from within the process. | | + | | {{ en:software:tim:send.png }} | E-mail / Send | This symbol enables e-mails to be sent automatically and directly from within the process. | |
| | {{ en:software:tim:subprocess.png }} | Embedded subprocess | This symbol represents an embedded subprocess. | | | {{ en:software:tim:subprocess.png }} | Embedded subprocess | This symbol represents an embedded subprocess. | | ||
| | {{ software:tim:wait_state.png }} | Signal | At this point, the process will be on hold until a certain event or signal occurs. | | | {{ software:tim:wait_state.png }} | Signal | At this point, the process will be on hold until a certain event or signal occurs. | | ||
| | {{ software:tim:start.png }} | Start | This symbol marks the starting point of a process. | | | {{ software:tim:start.png }} | Start | This symbol marks the starting point of a process. | | ||
| | {{ software:tim:ende.png }} | End | This symbol marks the ending point of this specific branch within the current process. | | | {{ software:tim:ende.png }} | End | This symbol marks the ending point of this specific branch within the current process. | | ||
| - | | {{ software:tim:terminierung.png }} | terminate event | The entire process will be terminated with occurance of the terminate event. | | + | | {{ software:tim:terminierung.png }} | terminate event | The entire process will be terminated when the termination event occurs. | |
| - | | {{ software:tim:xor.png }} | XOR-Gateway | This symbolizes an exclusive intersection/gateway with only one single active output. | | + | | {{ software:tim:xor.png }} | XOR-Gateway | This symbolizes an exclusive intersection/gateway with one single active output. | |
| | {{ software:tim:and.png }} | AND-Gateway | This symbolizes a parallel gateway at which all available outputs are active. | | | {{ software:tim:and.png }} | AND-Gateway | This symbolizes a parallel gateway at which all available outputs are active. | | ||
| - | | {{ software:tim:boundary_exception.png }} | Boundary exception | This pathway will be activated in case of an error. | | + | | {{ software:tim:boundary_exception.png }} | [[en:software:tim:stencils:boundaryexception|Boundary Exception]] | This pathway will be activated in case of an error. | |
| - | | {{ software:tim:boundary_escalation.png }} | Boundary escalation | This pathway will be activated in case of an escalation. The current activity will either be terminated (the symbol marked by a non-dashed line) or continue to go on (the symbol marked by a dashed line). | | + | | {{ software:tim:boundary_escalation.png }} | Boundary escalation | This pathway will be activated in case of an escalation. The current activity will either be terminated (the symbol marked by a non-dashed line) or continued (the symbol marked by a dashed line). | |
| - | | {{ software:tim:scriptTask_eng.png }} | Script Task | A Script Task is executed by TIM without any human interaction of a user. At the moment Script Tasks can only be used in combination with action handlers. The action handler is executed by TIM when the sequence flow arrives. | | + | | {{ software:tim:scriptTask_eng.png }} | Script Task | A script task is executed by TIM without any interaction by a user. At the moment, script tasks can only be used in combination with action handlers. The action handler is executed by TIM when the sequence flow arrives. | |
| - | | {{ software:tim:maualTask_eng.png }} | Manual Task | A Manual Task is solely performed by a user outside of and without the assistance of TIM or any other application. Therefore there is no connection to TIM. | | + | | {{ software:tim:maualTask_eng.png }} | Manual Task | A manual task is performed only by a user, outside of and without the assistance of TIM or any other application. Therefore, there is no connection to TIM. | |
| - | | {{ software:tim:userTask_eng.png }} | User Task | A User Task is a typical “workflow” task where a user performs the task with the assistance of TIM. In contrast to a Manual Task User Tasks are performed within TIM. | | + | | {{ software:tim:userTask_eng.png }} | User Task | A user task is a typical “workflow” task where a user performs the task with the assistance of TIM. In contrast to a manual task, user tasks are performed within TIM. | |
| - | | {{ software:tim:automatedTask_eng.png }} | Automated Task | An Automated Task uses a service (e.g. a Webservice or an automated application). The service is started when the sequence flow arrives at the task. | | + | | {{ software:tim:automatedTask_eng.png }} | Automated Task | An automated task uses a service (e.g. a webservice or an automated application). The service is started when the sequence flow arrives at the task. | |
| === Mandatory Handler === | === Mandatory Handler === | ||
| - | Before completing a task, the Mandatory Handler checks if all mandatory fields in the respective smartform filled in. If the mandatory fields are empty, the handler prevents the task from completing. Subsequently the user is informed to fill in the mandatory fields | + | Before completing a task, the [[en:software:tim:actionhandler:mandatoryhandler| mandatory handler]] checks if all mandatory fields of the respective smartform are filled in. If the mandatory fields are empty, the handler prevents the task from completing. Subsequently the user is informed to fill in the mandatory fields. |
en/software/tim/stencils.1435584164.txt.gz · Last modified: 2021/07/01 09:55 (external edit)
Except where otherwise noted, content on this wiki is licensed under the following license: 2013 T!M Solutions GmbH
