This is the documentation for older versions of Odoo (formerly OpenERP).

See the new Odoo user documentation.

See the new Odoo technical documentation.

工作流和用户过程

Workflows are used to define the behaviour of a given document. They are used by developers and system implementers to determine which object should execute which actions and at which moments. These are principally technical processes defined in a vertical way on the lifecycle of a complete object (represented by a document). Changing a workflow will have a direct impact on the behaviour of the software in response to user actions. You handle all possible exceptions there so that the software is robust.

/doc_static/5.0/_images/process_sale_workflow.png

一个处理客户订单的流程例子

Unlike workflows, user processes represent workflows across all of a company and its documents. They are used by end users to locate an action for more complete handling. A change of user process won't have any effect on the software but will show the user another way of working on a given problem.

/doc_static/5.0/_images/process_sale_process.png

一个处理客户订单的流程的例子

Processes are used by end users to help them understand the problems which haven't been handled in OpenERP. You can find actions that have no influence on the software, such as “Telephone customer to thank him”, and “Send a fax to reassure him”. As well as providing user help, processes provide functions such as:

  • integration with OpenERP help and the company's quality manual,

  • showing the user menu for finding a specific document.

/doc_static/5.0/_images/process_cross_worfklow_process.png

工作流和用户流之间的关系

User processes are thus connected to technical workflows. If you modify the software's behaviour with a workflow, the changes will be directly visible in the user processes that are based on the modified document. So if you add new required roles for certain transitions on a workflow they will automatically be shown in the process corresponding to the modified document.

To get maximum benefit from the power of user processes and the workflow engine, OpenERP provides an integrated workflow editor and user process editor. This enable you to modify them through the client interface.

You'll only work with the process editor in this chapter. If you want to test the workflow editor click on the link to the bottom left of a document and select the menu Customize ‣ Manage Workflows. OpenERP opens a graphical editor to modify the workflow for the selected document type.

/doc_static/5.0/_images/process_workflow_editor.png

Workflow editor modifying the behaviour of invoices

The workflow editor is only available in OpenERP's web client at the time of writing. If you have the GTK client you can use the menus in Administration ‣ Low Level Objects ‣ Workflow Items. These are text-based not graphical.

Using processes effectively

Regardless of which OpenERP screen you're in you can call up a process on the current document by clicking the Process icon. Depending on the document you can have several processes defined using it, OpenERP then asks you to choose which one of them you want.

For example if you are in a meeting form, OpenERP will ask you to choose from the processes it knows about that involve such forms:

  • 方法选择和新员工入职指引,

  • 售前跟踪客户订单,

  • processes for visiting customers and handling expenses.

/doc_static/5.0/_images/process_screen.png

Button for entering a user process from a form

The element colored red shows the active process for the selected document. Elements in grey are the states that the selected document won't go through because of its configuration. You can use the different icons to open the document, print it, or get its documentation.

Some states have an image inside of arrows formed into a circle. These show that the state refers to another process. To go to this other process you can click on the title of the state. For example you can click on the invoice in the customer order management workflow to see in detail how that invoice is handled.

/doc_static/5.0/_images/process_subflow_icon.png

指向另一个工作流的状态

Finally, you can place your mouse for a second over a transition (hover over a transition) to get a help balloon appearing about this transition. OpenERP then shows you:

  • A description of the transition,

  • The actions you can take at this step,

  • The roles you need to make anything happen from this step.

/doc_static/5.0/_images/process_transition.png

Detail of a transition in a workflow

If you click on the transition, OpenERP opens a dialog box with buttons that enable you to change the document state. These are the same buttons that you see on the active document form. They enable you to confirm an order directly from the process and then see the consequences in real time at a macro level.

Defining your own user processes

Use the menus under Administration ‣ Customization ‣ Enterprise Processes to define new processes or modify existing processes. When entering a process, OpenERP shows you the list of states available for that process.

/doc_static/5.0/_images/process_form.png

Form for defining a process

You can add a new state or modify an existing state. A state can be associated with an object (whose instances are represented by documents). If that is the case, choose it in the case object. You can set an expression that shows if the object can be found in that state or not. Expressions are in Python format. For example for the quotation state choose the object sale.order and set the following expression object.state == 'draft' .

You can also link to a menu so that users can learn which menu to use to access objects in a state. You can set the conditions in which this object is in a greyed-out state in the second tab Conditions. These expressions, too, are encoded in Python format.

Once the node has been defined you should set the transitions leaving this object. For each transition you can:

  • Give the leaving and destination states,

  • Set up a list of buttons that start various transitions in the process,

  • Map between workflow transitions and the document that's selected,

  • Put an explanatory notice in different languages.

/doc_static/5.0/_images/process_transition_form.png

Screen for defining a process transition