[otrs-cvs] doc-admin/de/content/customization acl.xml, 1.4, 1.5 themes.xml, 1.4, 1.5 process-management.xml, 1.4, 1.5 language-translation.xml, 1.4, 1.5
"CVS commits notifications of OTRS.org" <[email protected]>
| Newsgroups | gmane.comp.otrs.cvs |
|---|---|
| Message-ID | <[email protected]> |
Comments:
Update of /home/cvs/doc-admin/de/content/customization
In directory lancelot:/tmp/cvs-serv29819/de/content/customization
Modified Files:
acl.xml themes.xml process-management.xml
language-translation.xml
Log Message:
Synchronized translation files.
Author: mg
Author: mg
Author: mg
Index: process-management.xml
===================================================================
RCS file: /home/cvs/doc-admin/de/content/customization/process-management.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -2 -u -d -r1.4 -r1.5
--- process-management.xml 3 Dec 2012 08:37:27 -0000 1.4
+++ process-management.xml 10 Dec 2012 09:02:10 -0000 1.5
@@ -6,13 +6,11 @@
<section id="process-management" >
<title>Process Management</title>
-
- <!-- TODO CR2 Review -->
-<section>
+ <section>
<title>Introduction</title>
<para>
- This feature of OTRS allows you to model processes (workflows) in the ticket
-system. The basic idea is to be able to define reoccurring processes, and
-to delegate work items to different people, as well as leading the progress
-of a process in different directions based on certain criteria.
+ This feature of OTRS allows you to model processes (work-flows) in the
+ticket system. The basic idea is to be able to define recurring processes,
+and to delegate work items to different people, as well as leading the
+progress of a process in different directions based on certain criteria.
</para>
</section>
@@ -28,5 +26,5 @@
<para>
Before an order will be placed, the demand for literature by an employee
-will be recorded. The following book is needed in our example:
+will be recorded. The following book is needed in our example:
</para>
<para>
@@ -42,6 +40,6 @@
<title>Approval by superior</title>
<para>
- The head of the employee's department needs to decide on the order. In case
-of a denial, a reason should be recorded by the superior. In case of
+ The head of the employee's department needs to decide on the order. In case
+of a denial, a reason should be recorded by the superior. In case of
approval, the order is passed to the purchasing department.
</para>
@@ -52,6 +50,6 @@
<para>
Purchasing now has the task to find out where the book can be ordered with
-the best conditions. If it is out of stock, this can be recorded in the
-order. In case of a successful order purchasing will record the supplier,
+the best conditions. If it is out of stock, this can be recorded in the
+order. In case of a successful order purchasing will record the supplier,
the price and the delivery date.
</para>
@@ -59,17 +57,16 @@
<section>
- <title>Processing by the mailroom</title>
+ <title>Processing by the mail room</title>
<para>
The shipment will arrive at the company. The incoming goods department
-checks the shipment and records the date of receipt. Now the employee will
+checks the shipment and records the date of receipt. Now the employee will
be informed that their order has arrived and is ready to be collected.
</para>
</section>
</section>
-
<section>
<title>Implementing the example</title>
<para>
- If we assume that a ticket acts in this workflow like an accompanying
+ If we assume that a ticket acts in this work-flow like an accompanying
document that can receive change notes, we already have a clear picture of
process tickets.
@@ -77,15 +74,27 @@
<para>
From the analysis of the example process we can identify the following
-neccessary items:
+necessary items:
</para>
<para>
<itemizedlist>
- <listitem><para>Possiblities to record data, let's call them <emphasis>Activity
-Dialogs</emphasis>,</para></listitem>
- <listitem><para>checks which can react to changed data automatically, let's call them
-<emphasis>Transitions</emphasis>,</para></listitem>
- <listitem><para>changes which can be applied to a process ticket after successful
+ <listitem>
+ <para>
+ Possibilities to record data, let's call them <emphasis>Activity
+Dialogs</emphasis>,
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Checks which can react to changed data automatically, let's call them
+<emphasis>Transitions</emphasis>,
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ changes which can be applied to a process ticket after successful
transitions of a process ticket, let's call them <emphasis>Transition
-Actions</emphasis>.</para></listitem>
+Actions</emphasis>.
+ </para>
+ </listitem>
</itemizedlist>
</para>
@@ -99,6 +108,7 @@
A possibility to offer more than just one Activity Dialog to be available.
In our example this is needed when the superior must have the choice between
-"Approve" and "Deny". Let's call this <emphasis>Activity</emphasis>.
- </para></listitem>
+"Approve" and "Deny". Let's call this <emphasis>Activity</emphasis>.
+ </para>
+ </listitem>
</itemizedlist>
</para>
@@ -106,5 +116,5 @@
Now, with Activities, Activity Dialogs, Transitions and Transition Actions
we have the necessary tools to model the individual steps of our
-example. What's still missing is an area where for each workflow the order
+example. What's still missing is an area where for each work-flow the order
of the steps can be specified. Let's call this
<emphasis>Process</emphasis>. To be able to refer to all these entities
@@ -388,5 +398,4 @@
will define the individual entities that we need.
</para>
-
<section>
<title>Process (as a container)</title>
@@ -406,5 +415,5 @@
<screenshot>
<screeninfo>The OTRS Admin screen - System Administration</screeninfo> <graphic
-srccredit="process-management - screenshot"
+srccredit="process-management - screenshot" scale='40'
fileref="screenshots/pm-admin-sysadmin.png"></graphic></screenshot>
</para>
@@ -419,5 +428,5 @@
<screenshot>
<screeninfo>Create New Process button</screeninfo> <graphic
-srccredit="process-management - screenshot"
+srccredit="process-management - screenshot" scale='40'
fileref="screenshots/pm-newprocess-button.png"></graphic></screenshot>
</para>
@@ -425,5 +434,4 @@
<emphasis>Figure: Create New Process button.</emphasis>
</para>
-
<para>
Fill the process information,set Process Name and the Description, we will
@@ -434,5 +442,5 @@
<screenshot>
<screeninfo>Add new process</screeninfo> <graphic
-srccredit="process-management - screenshot" scale='70'
+srccredit="process-management - screenshot" scale='40'
fileref="screenshots/pm-newprocess-info.png"></graphic></screenshot>
</para>
@@ -441,5 +449,4 @@
</para>
</section>
-
<section>
<title>Activity Dialogs</title>
@@ -454,5 +461,5 @@
<screenshot>
<screeninfo>Create New Activity Dialog button</screeninfo> <graphic
-srccredit="process-management - screenshot"
+srccredit="process-management - scale='40'screenshot" scale='40'
fileref="screenshots/pm-accordion-new-activitydialog.png"></graphic></screenshot>
</para>
@@ -472,5 +479,5 @@
<screenshot>
<screeninfo>Add new Activity Dialog</screeninfo> <graphic
-srccredit="process-management - screenshot"
+srccredit="process-management - screenshot" scale='40'
fileref="screenshots/pm-edit-activitydialog.png"></graphic></screenshot>
</para>
@@ -487,5 +494,5 @@
<screenshot>
<screeninfo>Edit field details (Article)</screeninfo> <graphic
-srccredit="process-management - screenshot"
+srccredit="process-management - screenshot" scale='40'
fileref="screenshots/pm-edit-field-article.png"></graphic></screenshot>
</para>
@@ -534,5 +541,5 @@
</listitem>
<listitem>
- <para>"Order rejected" (AD4)</para>
+ <para>"Order denied" (AD4)</para>
<para>
An activity dialog which makes it possible for purchasing to reject an
@@ -551,5 +558,5 @@
<para>"Shipment received" (AD6)</para>
<para>
- An activity for the mailroom with a field for the Date of receipt and the
+ An activity for the mail room with a field for the Date of receipt and the
Status field with the option "Shipment received".
</para>
@@ -644,5 +651,4 @@
</para>
</section>
-
<section>
<title>Transitions</title>
@@ -654,5 +660,5 @@
<screenshot>
<screeninfo>Create New Transition button</screeninfo> <graphic
-srccredit="process-management - screenshot"
+srccredit="process-management - screenshot" scale='40'
fileref="screenshots/pm-accordion-new-transition.png"></graphic></screenshot>
</para>
@@ -669,6 +675,6 @@
<screenshot>
<screeninfo>Add new Transition</screeninfo> <graphic
-srccredit="process-management - screenshot"
-fileref="screenshots/pm-edit-transtion.png"></graphic></screenshot>
+srccredit="process-management - screenshot" scale='40'
+fileref="screenshots/pm-edit-transition.png"></graphic></screenshot>
</para>
<para>
@@ -723,13 +729,13 @@
</section>
<section>
- <title>TransitionActions</title>
+ <title>Transition Actions</title>
<para>
- Click on "Transition Actions " in the "Available Process Elements", then
-click on "Create New TransitionAction".
+ Click on "Transition Actions" in the "Available Process Elements", then
+click on "Create New Transition Action".
</para>
<para>
<screenshot>
<screeninfo>Create New Transition Action button</screeninfo> <graphic
-srccredit="process-management - screenshot"
+srccredit="process-management - screenshot" scale='40'
fileref="screenshots/pm-accordion-new-transitionaction.png"></graphic></screenshot>
</para>
@@ -766,6 +772,6 @@
<screenshot>
<screeninfo>Add new Transition Action</screeninfo> <graphic
-srccredit="process-management - screenshot"
-fileref="screenshots/pm-edit-transtionaction.png"></graphic></screenshot>
+srccredit="process-management - screenshot" scale='40'
+fileref="screenshots/pm-edit-transitionaction.png"></graphic></screenshot>
</para>
<para>
@@ -782,5 +788,5 @@
<itemizedlist>
<listitem>
- <para>Move the process ticket into the "Superior" queue (TA1)</para>
+ <para>"Move the process ticket into the 'Superior' queue" (TA1)</para>
<para>
This action is supposed to be executed when the Transition "Approval" (T1)
@@ -789,5 +795,5 @@
</listitem>
<listitem>
- <para>Change ticket responsible to "Superior" (TA2)</para>
+ <para>"Change ticket responsible to 'Superior'" (TA2)</para>
<para>
To be executed when the Transition "Approval" (T1) applied.
@@ -795,5 +801,5 @@
</listitem>
<listitem>
- <para>Move the process ticket into the "Employee" queue (TA3)</para>
+ <para>"Move the process ticket into the 'Employee' queue"" (TA3)</para>
<para>To be executed when:</para>
<itemizedlist>
@@ -810,5 +816,5 @@
</listitem>
<listitem>
- <para>Change ticket responsible to "Employee" (TA4)</para>
+ <para>"Change ticket responsible to 'Employee'" (TA4)</para>
<para>To be executed when:</para>
<itemizedlist>
@@ -825,11 +831,32 @@
</listitem>
<listitem>
- <para>Move process ticket into the "Purchasing" queue (TA5)</para>
+ <para>"Move process ticket into the 'Purchasing' queue" (TA5)</para>
<para>To be executed when the transition "Approved" (T3) applied.</para>
</listitem>
<listitem>
- <para>Move process ticket into the "Post office" queue (TA6)</para>
+ <para>"Move process ticket into the 'Post office' queue" (TA6)</para>
<para>To be executed when the transition "Order placed" (T5) applied.</para>
</listitem>
+ <listitem>
+ <para>"Close ticket successfully" (TA7)</para>
+ <para>To be executed when:</para>
+ <itemizedlist>
+ <listitem><para>
+ The transition "Shipment received" (T6) applied
+ </para></listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>"Close ticket unsuccessfully" (TA8)</para>
+ <para>To be executed when:</para>
+ <itemizedlist>
+ <listitem><para>
+ The transition "Approval denied" (T2) applied
+ </para></listitem>
+ <listitem><para>
+ The transition "Order denied" (T4) applied
+ </para></listitem>
+ </itemizedlist>
+ </listitem>
</itemizedlist>
</para>
@@ -853,5 +880,5 @@
<screenshot>
<screeninfo>Create New Activity button</screeninfo> <graphic
-srccredit="process-management - screenshot"
+srccredit="process-management - screenshot" scale='40'
fileref="screenshots/pm-accordion-new-activity.png"></graphic></screenshot>
</para>
@@ -877,9 +904,9 @@
<itemizedlist>
<listitem>
- <para>Recording the demand (A1)</para>
+ <para>"Recording the demand" (A1)</para>
<para>Contains the Activity Dialog "Recording the demand" (AD1)</para>
</listitem>
<listitem>
- <para>Approval (A2)</para>
+ <para>"Approval" (A2)</para>
<para>
Contains the Activity Dialogs "Approval denied" (AD2) as well as "Approved"
@@ -888,5 +915,5 @@
</listitem>
<listitem>
- <para>Order (A3)</para>
+ <para>"Order" (A3)</para>
<para>
Contains the Activity Dialogs "Order rejected" (AD4) as well as "Order
@@ -895,9 +922,9 @@
</listitem>
<listitem>
- <para>Incoming (A4)</para>
+ <para>"Incoming" (A4)</para>
<para>Contains the Activity Dialog "Shipment received" (AD6)</para>
</listitem>
<listitem>
- <para>Process complete (A5): This is an Activity without possible
+ <para>"Process complete" (A5): This is an Activity without possible
ActivityDialogs. It will be set after "Approval denied", "Order denied" or
"Shipment received" and represents the end of the process.
@@ -912,24 +939,19 @@
</para>
</section>
-
-
- <!-- TOTO CR2 END -->
-<!-- TODO CR1 The following Lines Needs to be changed to the new format... add Screens -->
-<section>
- <title>Book ordering Process</title>
+ <section>
+ <title>Book ordering process Path</title>
<para>
Let us conclude our example with the last missing piece in the puzzle, the
-Process. In our case this is the whole ordering workflow. Other processes
-could be office supply ordering or completely different processes.
+Process as the a flow describer. In our case this is the whole ordering
+work-flow. Other processes could be office supply ordering or completely
+different processes.
</para>
-
<para>
The process has a starting point which consists of the start Activity and
-the start Activity Dialog. For any new book order, the start Activity
-Dialog is the first screen that is displayed. If this is completed and
-saved, the Process ticket will be created and can follow the configured
-workflow.
+the start Activity Dialog. For any new book order, the start Activity Dialog
+(first Activity Dialog for the first Activity) is the first screen that is
+displayed. If this is completed and saved, the Process ticket will be
+created and can follow the configured work-flow.
</para>
-
<para>
The process also contains the directions for how the process ticket can move
@@ -938,52 +960,133 @@
other Activities.
</para>
- <para>Recording the demand until "Approval"</para>
<para>
- <itemizedlist>
- <listitem>
- <para>Starting point: Activity A1 (Recording the demand)</para>
- </listitem>
- <listitem>
- <para>Possible Transition: T1 (Approval)</para>
- <itemizedlist>
- <listitem>
- <para>If the condition of this activity is fulfilled, the ticket will move to
-Activity A2 (Approval)</para>
- </listitem>
- <listitem>
- <para>Additionally, the following TransitionActions are executed:</para>
- <itemizedlist>
- <listitem>
- <para>TA1 (Moving the ticket into the "Superior" Queue)</para>
- </listitem>
- <listitem>
- <para>TA2 (Set ticket responsible to "Superior")</para>
- </listitem>
- </itemizedlist>
- </listitem>
- </itemizedlist>
- </listitem>
- </itemizedlist>
+ Assuming that the Activities has already assigned their Activity Dialogs
+drag an Activity from the accordion (in the left part of the screen) and
+drop it into the canvas area (below process information). Notice that an
+arrow from the process start (green circle) to the Activity is placed
+automatically. (This is the first Activity and its first Activity Dialog is
+the first screen that will be shown when the process starts).
</para>
<para>
- That's the first step in the path of the book ordering process. It looks
-like this (slightly simplified):
+ <screenshot>
+<screeninfo>Drag first Activity into the canvas</screeninfo> <graphic
+srccredit="process-management - screenshot" scale='40'
+fileref="screenshots/pm-canvas-drag-activity.png"></graphic></screenshot>
</para>
<para>
- <screen>
- 'A1' => {
- 'T1' => {
- ActivityEntityID => 'A2',
- TransitionAction => [ 'TA1', 'TA2',],
- },
- },
- </screen>
+ <emphasis>Figure: Drag first Activity into the canvas.</emphasis>
</para>
<para>
- Action 'A1' is a defined state of the process ticket, where there is the
-possibility for the Transition 'T1'. If this applies, the ticket will move
-to the next Activity 'A2', and the TransitionActions 'TA1' and 'TA2' are
-executed. In Activity 'A2', the Activity Dialogs 'AD2' (Approval denied)
-and 'AD3' (Approved) are available.
+ Next, drag another Activity into the canvas too. now we will have two
+Activities in the canvas the first one is connected to the start point and
+the second has no connections, you can hover the mouse over each activity to
+reveal their own Activity Dialogs.
+ </para>
+ <para>
+ <screenshot>
+<screeninfo>Drag second Activity into the canvas</screeninfo> <graphic
+srccredit="process-management - screenshot" scale='40'
+fileref="screenshots/pm-canvas-drag-activity2.png"></graphic></screenshot>
+ </para>
+ <para>
+ <emphasis>Figure: Drag second Activity into the canvas.</emphasis>
+ </para>
+ <para>
+ Then let's create the "Path" (connection) between this two Activities, for
+this we will use the Transitions, Click on Transitions in the accordion drag
+a Transition and drop it inside the first Activity, notice that the Activity
+change its color indicating that the Transition is attached, as soon as the
+Transition is dropped the end point of the Transition arrow will be placed
+next to the process start point. Drag the Transition arrow end point and
+drop it inside the other Activity to create the connection between the
+Activities.
+ </para>
+ <para>
+ <screenshot>
+<screeninfo>Drag a Transition into the canvas</screeninfo> <graphic
+srccredit="process-management - screenshot" scale='40'
+fileref="screenshots/pm-canvas-drag-transition.png"></graphic></screenshot>
+ </para>
+ <para>
+ <emphasis>Figure: Drag a Transition into the canvas.</emphasis>
+ </para>
+ <para>
+ Now that the "Path" between the Actions is defined, then we need to assign
+the Transition Actions to the Transition, double click the Transition label
+(in the canvas), this will open a new popup window.
+ </para>
+ <para>
+ <screenshot>
+<screeninfo>Connect Activities using Transitions</screeninfo> <graphic
+srccredit="process-management - screenshot" scale='40'
+fileref="screenshots/pm-canvas-drag-transition2.png"></graphic></screenshot>
+ </para>
+ <para>
+ <emphasis>Figure: Connect Activities using Transitions.</emphasis>
+ </para>
+ <para>
+ Drag the needed Transition Actions from Available Transition Actions pool
+and drop them into the Assigned Transition Actions pool and click on submit
+button.
+ </para>
+ <para>
+ <screenshot>
+<screeninfo>Assign Transition Actions</screeninfo> <graphic
+srccredit="process-management - screenshot" scale='40'
+fileref="screenshots/pm-edit-path.png"></graphic></screenshot>
+ </para>
+ <para>
+ <emphasis>Figure: Assign Transition Actions.</emphasis>
+ </para>
+ <para>
+ Then back in the main process edit screen click on save button below the
+canvas to save all other changes.
+ </para>
+ <para>
+ Complete the "path"" adding the following Activities, Transitions and
+Transition Actions:
+ </para>
+ <para>Recording the demand until "Approval"</para>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>Starting point: Activity: Recording the demand (A1)</para>
+ </listitem>
+ <listitem>
+ <para>Possible Transition: Approval (T1)</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ If the condition of this activity is fulfilled, the ticket will move to
+Activity: Approval (A2)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Additionally, the following TransitionActions are executed:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ "Moving the ticket into the 'Superior' Queue" (TA1)
+ </para>
+ </listitem>
+ <listitem>
+ <para>"Set ticket responsible to 'Superior'" (TA2)</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ </para>
+ <para>
+ The Activity: "Recording the demand" (A1) is a defined step of the process
+ticket, where there is the possibility for the Transition: "Approval"
+(T1). If this applies, the ticket will move to the next Activity: "Approval"
+(A2), and the Transition Actions: "Moving the ticket into the 'Superior'
+Queue" (TA1) and "Set ticket responsible to 'Superior'" (TA2) are
+executed. In the Activity: "Approval" (A2), the Activity Dialogs: "Approval
+denied" (AD2) and "Approved" (AD3) are available.
</para>
<para>Approval</para>
@@ -991,5 +1094,5 @@
<itemizedlist>
<listitem>
- <para>Starting Point: Activity A2 (Approval)</para>
+ <para>Starting Point: Activity "Approval" (A2)</para>
</listitem>
<listitem>
@@ -997,20 +1100,31 @@
<itemizedlist>
<listitem>
- <para>T2 (Approval denied)</para>
+ <para>"Approval denied" (T2)</para>
<itemizedlist>
<listitem>
<para>
- If this matches, the process ticket will move to Activity A5 (Process
-complete).
+ If this matches, the process ticket will move to Activity:"Process complete"
+(A5).
</para>
</listitem>
<listitem>
- <para>Additionally, the following TransitionActions are executed:</para>
+ <para>
+ Additionally, the following Transition Actions are executed:
+ </para>
<itemizedlist>
<listitem>
- <para>TA3 (move process ticket to the "Employee" Queue)</para>
+ <para>
+ "Move process ticket to the 'Employee' Queue" (TA3)
+ </para>
</listitem>
<listitem>
- <para>TA4 (set ticket responsible to "Employee")</para>
+ <para>
+ "Set ticket responsible to 'Employee'" (TA4)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ "Close ticket unsuccessfully" (TA8)
+ </para>
</listitem>
</itemizedlist>
@@ -1019,16 +1133,20 @@
</listitem>
<listitem>
- <para>T3 (Approved)</para>
+ <para>"Approved" (T3)</para>
<itemizedlist>
<listitem>
<para>
- If this matches, the process ticket will move to Activity A3 (Order).
+ If this matches, the process ticket will move to Activity: "Order" (A3).
</para>
</listitem>
<listitem>
- <para>Additionally, the following TransitionAction is executed:</para>
+ <para>
+ Additionally, the following Transition Action is executed:
+ </para>
<itemizedlist>
<listitem>
- <para>TA5 (move process ticket to "Purchasing" Queue)</para>
+ <para>
+ "Move process ticket to 'Purchasing' Queue" (TA5)
+ </para>
</listitem>
</itemizedlist>
@@ -1040,47 +1158,123 @@
</itemizedlist>
</para>
- <para>Simplified representation:</para>
<para>
- <screen>
- 'A2' => {
- 'T2' => {
- ActivityEntityID => 'A5',
- TransitionAction => [ 'TA3', 'TA4'],
- },
- 'T3' => {
- ActivityEntityID => 'A3',
- TransitionAction => [ 'TA5'],
- }
- },
- </screen>
+ We can see that from the current Activity, which defines a step of the
+process ticket, there are one or more possibilities for Transition which
+have exactly one target Activity (and possibly one or more Transition
+Actions).
</para>
- <para>The path for these two steps together looks like this:</para>
+ <para>Order</para>
<para>
- <screen>
- Path => {
- 'A1' => {
- 'T1' => {
- ActivityEntityID => 'A2',
- TransitionAction => [ 'TA1', 'TA2'],
- },
- },
- 'A2' => {
- 'T2' => {
- ActivityEntityID => 'A5',
- TransitionAction => [ 'TA3', 'TA4'],
- },
- 'T3' => {
- ActivityEntityID => 'A3',
- TransitionAction => [ 'TA5'],
- },
- },
- },
- </screen>
+ <itemizedlist>
+ <listitem>
+ <para>Starting Point: Activity "Order" (A3)</para>
+ </listitem>
+ <listitem>
+ <para>Possible Transitions:</para>
+ <itemizedlist>
+ <listitem>
+ <para>"Order denied" (T4)</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ If this matches, the process ticket will move to Activity:"Process complete"
+(A5).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Additionally, the following Transition Actions are executed:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ "Move process ticket to the 'Employee' Queue" (TA3)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ "Set ticket responsible to 'Employee'" (TA4)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ "Close ticket unsuccessfully" (TA8)
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>"Order placed" (T5)</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ If this matches, the process ticket will move to Activity: "Incoming" (A5).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Additionally, the following Transition Action is executed:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ "Move process ticket to 'Post office' Queue" (TA6)
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
</para>
+ <para>Incoming</para>
<para>
- We can see that from the current Activity, which defines a state of the
-process ticket, there are one or more possibilities for Transition which
-have exactly one target Activity (and possibly one or more
-TransitionActions).
+ <itemizedlist>
+ <listitem>
+ <para>Starting Point: Activity "Incoming" (A4)</para>
+ </listitem>
+ <listitem>
+ <para>Possible Transitions:</para>
+ <itemizedlist>
+ <listitem>
+ <para>"Shipment received" (T6)</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ If this matches, the process ticket will move to Activity:"Process complete"
+(A5).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Additionally, the following Transition Actions are executed:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ "Move process ticket to the 'Employee' Queue" (TA3)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ "Set ticket responsible to 'Employee'" (TA4)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ "Close ticket successfully" (TA7)
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
</para>
<para>
@@ -1088,47 +1282,16 @@
</para>
<para>
- <screen>
- Path => {
- 'A1' => {
- 'T1' => {
- ActivityEntityID => 'A2',
- TransitionAction => [ 'TA1', 'TA2'],
- },
- },
- 'A2' => {
- 'T2' => {
- ActivityEntityID => 'A5',
- TransitionAction => [ 'TA3', 'TA4'],
- },
- 'T3' => {
- ActivityEntityID => 'A3',
- TransitionAction => [ 'TA5'],
- },
- },
- 'A3' => {
- 'T4' => {
- ActivityEntityID => 'A5',
- TransitionAction => [ 'TA3', 'TA4'],
- },
- 'T5' => {
- ActivityEntityID => 'A4',
- TransitionAction => [ 'TA6'],
- },
- }
- 'A4' => {
- 'T6' => {
- ActivityEntityID => 'A5',
- TransitionAction => [ 'TA3', 'TA4'],
- },
- },
- },
- </screen>
- </para>
- </section>
+ <screenshot>
+<screeninfo>Book ordering complete process path</screeninfo> <graphic
+srccredit="process-management - screenshot" scale='40'
+fileref="screenshots/pm-edit-process.png"></graphic></screenshot>
+ </para>
+ <para>
+ <emphasis>Figure: Book ordering complete process path.</emphasis>
+ </para>
+ </section>
</section>
-
-<!-- TODO CR1 END -->
<!--
<section>
Author: mg
---------------------------------------------------------------------
OTRS mailing list: cvs-log - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/cvs-log
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/cvs-log