[otrs-cvs] doc-admin/en/content/customization process-management.xml, 1.14, 1.15
"CVS commits notifications of OTRS.org" <[email protected]>
| Newsgroups | gmane.comp.otrs.cvs |
|---|---|
| Message-ID | <[email protected]> |
Comments:
Update of /home/cvs/doc-admin/en/content/customization
In directory lancelot:/tmp/cvs-serv15838/en/content/customization
Modified Files:
process-management.xml
Log Message:
Small fixes
Added complete process image,
Author: cr
Index: process-management.xml
===================================================================
RCS file: /home/cvs/doc-admin/en/content/customization/process-management.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -2 -u -d -r1.14 -r1.15
--- process-management.xml 7 Dec 2012 12:56:44 -0000 1.14
+++ process-management.xml 7 Dec 2012 16:19:24 -0000 1.15
@@ -5,12 +5,11 @@
<section id="process-management" >
<title>Process Management</title>
- <!-- TODO CR2 Review -->
<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>
@@ -24,6 +23,6 @@
<title>Recording the demand</title>
<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:
+ Before an order will be placed, the demand for literature by an employee will be
+ recorded. The following book is needed in our example:
</para>
<para>
@@ -39,7 +38,7 @@
<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 approval, the order is passed to the purchasing department.
+ 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>
</section>
@@ -48,15 +47,17 @@
<title>Processing by purchasing department</title>
<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 price and the delivery date.
+ 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 price and the delivery
+ date.
</para>
</section>
<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 be informed that their order has arrived and is ready to be collected.
+ The shipment will arrive at the company. The incoming goods department 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>
@@ -65,15 +66,31 @@
<title>Implementing the example</title>
<para>
- If we assume that a ticket acts in this workflow like an accompanying document that can receive change notes,
- we already have a clear picture of process tickets.
+ 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.
</para>
<para>
- From the analysis of the example process we can identify the following neccessary items:
+ From the analysis of the example process we can identify the following 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 transitions of a process ticket, let's call them <emphasis>Transition Actions</emphasis>.</para></listitem>
+ <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>
</itemizedlist>
</para>
@@ -86,7 +103,8 @@
<para>
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>
+ 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>
</itemizedlist>
</para>
@@ -94,5 +112,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 of the steps can be specified. Let's call this
+ 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 later, we will
assign to them an abbreviation in parentheses. This abbreviation is based on an internal
@@ -410,5 +428,4 @@
<emphasis>Figure: Create New Process button.</emphasis>
</para>
-
<para>
Fill the process information,set Process Name and the Description, we will leave the
@@ -754,5 +771,6 @@
</para>
<para>
- After all parameters and values are set click on the submit button to save the changes.
+ After all parameters and values are set click on the submit button to save the
+ changes.
</para>
<para>
@@ -913,6 +931,4 @@
</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 Path</title>
@@ -1260,7 +1276,15 @@
The complete Path for the book ordering Process will then look like this:
</para>
- </section>
+ <para>
+ <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 -->
<!--
---------------------------------------------------------------------
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