Plugin installed incorrectly. Rename plugin directory 'swiftmail.backup' to 'swiftmail'.
en:software:igrafx_documentation
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
en:software:igrafx_documentation [2017/09/12 13:26] julian.le |
en:software:igrafx_documentation [2021/07/01 09:52] (current) |
||
|---|---|---|---|
| Line 155: | Line 155: | ||
| ==== Attending to the attribute of a starting element ==== | ==== Attending to the attribute of a starting element ==== | ||
| - | <note important>Certain attributes of the starting element of a process need special attention to ensure that a process model will be properly executed by TIM. \\ {{:en:software:igrafx_tim_attribute5.png?200 }} | + | <note important>Certain attributes of the starting element of a process need special attention to ensure that a process model will be properly executed by TIM.\\ |
| + | {{:en:software:igrafx_tim_attribute5.png?200 }} | ||
| - | **__Owner MANDATORYFIELD__** = A user or a group must be entered in this field. This gives the designated user or group the right to own the process in TIM at a later point in time. Multiple groups or users can be added and are separated with a semicolon: "user(a);group(b)" For example: user(john.doe) or group(owner) | + | **__Owner MANDATORYFIELD__** = A user or a group must be entered in this field. This gives the designated user or group the right to own the process in TIM at a later point in time. Multiple groups or users can be added and are separated with a semicolon: "user(a);group(b)" For example: user(john.doe) or group(owner) or all() |
| - | **__Starter MANDATORYFIELD__** = A user or a group must be entered in this field in order to be eligible to start the process in TIM at a later point in time. Multiple groups or users can be added and are separated with a semicolon: "user(a);group(b)" For example: user(john.doe) or group(starter) | + | **__Starter MANDATORYFIELD__** = A user or a group must be entered in this field in order to be eligible to start the process in TIM at a later point in time. Multiple groups or users can be added and are separated with a semicolon: "user(a);group(b)" For example: user(john.doe) or group(starter) or all() |
| - | **__Deployer MANDATORYFIELD__** = A user or a group must be entered in this field in order to be entitled to deploy the process in TIM. Multiple groups or users can be added and are separated with a semicolon: "user(a);group(b)" For example: user(john.doe) or group(deployer) | + | **__Deployer MANDATORYFIELD__** = A user or a group must be entered in this field in order to be entitled to deploy the process in TIM. Multiple groups or users can be added and are separated with a semicolon: "user(a);group(b)" For example: user(john.doe) or group(deployer) or all() |
| **__Description__** = Here, a description of the process is entered. This will be shown in TIM | **__Description__** = Here, a description of the process is entered. This will be shown in TIM | ||
| Line 176: | Line 177: | ||
| </note> | </note> | ||
| + | |||
| ==== Caring for an Attribute of an activity ==== | ==== Caring for an Attribute of an activity ==== | ||
| Line 229: | Line 231: | ||
| {{:en:software:igrafx_tim_xor.png?200}} \\ In the case of a XOR gateway, transitions will be directly linked to alternative activities (i.e. the user has to decide which specific activity to choose). At a later stage the user will receive access to a related selection via a pop-up window. This will enables users to manually select the pathway themselves. \\ \\ These decisions will be shown within the TIM pop-up window. They will be shown according to the specific order assigned to them as a result of the previously created XOR gateways of the process modelling stage. | {{:en:software:igrafx_tim_xor.png?200}} \\ In the case of a XOR gateway, transitions will be directly linked to alternative activities (i.e. the user has to decide which specific activity to choose). At a later stage the user will receive access to a related selection via a pop-up window. This will enables users to manually select the pathway themselves. \\ \\ These decisions will be shown within the TIM pop-up window. They will be shown according to the specific order assigned to them as a result of the previously created XOR gateways of the process modelling stage. | ||
| - | ====== 4. Ednings====== | + | ====== 4. Endings====== |
| - | ==== 4.1 Big Ending ==== | + | ==== 4.1 Completely Terminating Ending ==== |
| - | If you use a "Big Ending" (Terminate Event in the Shape Library), it will upon arrving at that ending terminate the whole process. | + | If you use a "Completely Terminating Ending" (Terminate Event in the Shape Library), it will upon arrving at that ending terminate the whole process. |
| {{:software:dickes_ende.png?40x41 }} | {{:software:dickes_ende.png?40x41 }} | ||
| - | ==== 4.2 Small Ending ==== | + | ==== 4.2 Partially Terminating Ending ==== |
| - | A "Small Ending" can be used in the model by inserting a Generic Event and the drawing an arrow from an Activity to it. \\ | + | A "Partially Terminating Ending" can be used in the model by inserting a Generic Event and the drawing an arrow from an Activity to it. \\ |
| Once you arrive at a "Small Ending" it will not terminate the whole event, but rather just one way. This way you can terminate one "Way" of an AND Gateway, but the process will still continue. | Once you arrive at a "Small Ending" it will not terminate the whole event, but rather just one way. This way you can terminate one "Way" of an AND Gateway, but the process will still continue. | ||
| - | |||
| - | Ein "Dünnes Ende" wird in das Modell eingefügt, indem man aus der Symbolpalette ein Ereignis zieht und einen Pfeil aus einer Aktivität zu dem Ereignis zieht. Der Kreis wird dann eine dickere Umrandung haben. \\ | ||
| - | Hierbei wird beim Erreichen nicht der ganze Prozess beendet, sondern nur ein Strang des Prozesses. So kann man einen "Weg" aus einem AND Gateway terminieren lassen wobei der Prozess noch fortgeführt wird. | ||
| {{:software:duennes_ende.png?50 }} | {{:software:duennes_ende.png?50 }} | ||
en/software/igrafx_documentation.1505215597.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
