Plugin installed incorrectly. Rename plugin directory 'swiftmail.backup' to 'swiftmail'.
en:software:tim:stencils:boundaryescalation
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
en:software:tim:stencils:boundaryescalation [2018/06/12 13:04] Julian Le created |
en:software:tim:stencils:boundaryescalation [2021/07/01 09:52] (current) |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| ===== Not interrupting escalation ===== | ===== Not interrupting escalation ===== | ||
| - | A not interrupting escalation can identified by the dashed edge in the process image. It will not interrupt the normal process sequence, but functions like a parallel gateway, which is activated, when the lodged remaining time is reached.\\ | + | A not interrupting escalation can identified by the dashed border in the process image. It will not interrupt the normal process sequence, but functions like a parallel gateway, which is activated, when the lodged remaining time is reached.\\ |
| This is useful, if e.g. a reminder should be sent.\\ | This is useful, if e.g. a reminder should be sent.\\ | ||
| - | Der Beispiel-Prozess hat eine nicht unterbrechende Eskalation, um eine Stunde vor dem Ablauf der Zeit für die Aufgabe "Essenswünsche einholen" eine automatische Errinerings-Email mittels Mailnode zu verschicken. | + | The example process has a not interrupting escalation, so that an hour before expiration of time for the task "Get Food Wishes" a automatic reminder mail is sent via Mailnode. |
| - | The example process has a not interrupting escalation, so that an hour before expiration of time for the task "Essens | + | |
| - | {{:software:tim:boundary_escalations.png?nolink&670x314}} | + | {{:en:software:tim:stencils:boundaryesc.png?800 }} |
| ---- | ---- | ||
| - | ===== Unterbrechende Eskalation ===== | + | ===== Interrupting Escalations ===== |
| - | Sobald eine unterbrechende Eskalation in Kraft tritt wird der "normale" Prozessverlauf unterbrochen und der Pfad der Boundary Escalation wird eingeschlagen. | + | When an interrupting escalation is effective, the "normal" process sequence is interrupted and the Boundary Escalation path is taken. |
| - | Bei der Modellierung sind die unterbrechenden Eskalationen an einem durchgezogenen Rand erkennbar. | + | The interrupting escalations can be identified by the solid border. |
| - | An einem konkreten Beispiel sieht das folgendermaßen aus: | + | Shown with a concrete example it is as follows: |
| - | In einem Catering-Prozess muss jemand die speziellen Essenswünsche der Kunden erfragen. Falls diese Aufgabe nicht rechtzeitig erledigt wird, macht der normale Prozess-Verlauf keinen SInn mehr, da nicht mehr genug Zeit bleibt spezielle Zutaten zu kaufen und spezielle Speisen zuzubereiten. | + | In the example process someone has to ask for the customers' special food wishes. If this task is not finsihed on time, the normal process sequence does not make any sense anymore, because not enough time is remainig to purchase special ingredients and prepare special food. |
| - | {{:software:tim:boundary_escalations.png?nolink&670x314}} | ||
| - | Tritt nun der Fall ein, dass die Aufgabe "Essenswünsnche einholen" 60 Minuten überzogen wird, springt der Prozess automatisch zu "Standartauswahl zubereiten" | + | {{:en:software:tim:stencils:boundaryesc.png?800 }} |
| + | |||
| + | If the task "Get Food Wishes" exceeds the time by 60 minutes, the process is automatically taken to "Prepare Standard Food". | ||
| ---- | ---- | ||
| - | ===== Enden ===== | + | ===== Endings ===== |
| - | Je nach dem, ob eine Instanz bei einer fertigen Abzweigung komplett terminieren soll oder nur die Abzweigung, wird eines der beiden [[:software:igrafx_documentation#endungen|Enden]] benutzt. | + | Depening on whether a instance should be completely terminated when finishing one path or only the path one of the two [[en:software:igrafx_documentation#endings|endings]] is used. |
en/software/tim/stencils/boundaryescalation.1528801491.txt.gz · Last modified: 2021/07/01 09:54 (external edit)
Except where otherwise noted, content on this wiki is licensed under the following license: 2013 T!M Solutions GmbH
