默认的工作流

Chapter 3 covered the default workflow and the default settings when publishing content. I discussed the security and settings for each state in the workflow. However, a picture is worth a thousand words, so Figure 8-2 shows the workflow state.

第3章介绍过在发布内容时我们所能见到的默认工作流及其默认的设置。那会儿我也探讨了工作流中每个状态的安全和设置。然而，一张形象化的图片胜过千言万语——来看图8-2，它展示出工作流状态（workflow state）。

Figure 8-2. The default workflow for content that comes with Plone

图8-2 Plone自带的默认工作流，它将改变内容的状态

Figure 8-2 shows the main states and the transitions. This figure has a gray dotted line that represents a sort of security divider. To the left of the line is where owners of the content usually interact with the content. To the right of the line is where reviewers usually interact with the content.

图8-2呈现了主要的状态和过渡。再仔细看一下，图中有条灰色虚线表示安全分界线（security divider）。分界线左边是所有者（owners）和内容频繁交互的区域，右边则是审批者（reviewers）和内容频繁交互的区域。

NOTE The owner of the content is the person who created the content originally. An owner is one particular member of a Plone site. Although many members exist in a Plone site, only one person can be the owner of a piece of content in a Plone site. Because the owner role is calculated when an object is created, the owner role is special.

注意 内容的所有者（the owner of the content）是指最先创建它的人。所有者（an owner）是Plone站点中特殊的成员（member）。尽管在一个Plone站点中存在许多成员，但是只有一名成员是某条内容的所有者。因为当一个对象被创建时，专门形成了所有者这个角色，它是特殊的（special）。

Just like with the credit card example, an associated set of permissions exists for the default workflow. Table 8-4 outlines all the permissions and the states.

正如信用卡的例子，一组与之相关联的许可（permissions）为默认的工作流而存在。表格8-4描绘出所有的许可和状态。

Table 8-4. The Default Workflow Permissions

表格8-4 默认工作流的许可

View refers to the following permissions: Access Contents Information and View

查看（view）引用的许可有：访问内容信息（Access Contents Information）和查看（View）

Edit refers to the following permission: Modify Portal Content

编辑（Edit）引用的许可有：修改入口内容（Modify Portal Content）

As you can see from Table 8-4, by default only when content is in the private state is it truly hidden from everyone else. When content is in the published state, only the manager can edit it. Later in the "Editing Permissions" section, I'll show you how to change these permissions easily through the Web.

正如你在表格8-4中看到的，默认情况下当内容处于私有状态时，对任何人来说它是真正隐藏着的。当内容处于发布状态时，只有管理员可以编辑内容。稍后在“编辑许可（Editing Permissions）”部分，我会向你介绍如何简单地通过Web来改变这些许可。

文件夹工作流

I also discussed the folder workflow in Chapter 3, when I covered publishing content with you. However, as I noted in that chapter, no pending state exists for folders. Instead, you have a slightly simpler workflow, as shown in Figure 8-3.

在第3章中我向你介绍了发布内容（publishing content），那会儿也讨论过文件夹工作流（folder workflow）。然而，那时我已经注意到，文件夹并不存在提交状态，我们是用一个更简单的工作流来替代，如图8-3。

Figure 8-3. The folder workflow for content that comes with Plone

图8-3 Plone自带的文件夹工作流，它将改变内容的状态

其他形式的工作流

其他形式的工作流
,,,,,,,,,,,,,,,

Numerous workflows are available to a Plone site, including private workflow, community workflow, one-step publication workflow, and so on. ZopeZen<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=ZopeZen" title="create this page">?</a> comes with a workflow, and PloneCollectorNG<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=PloneCollectorNG" title="create this page">?</a> also comes with a workflow. DCWorkflow<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=DCWorkflow" title="create this page">?</a> comes with four workflows.

一个Plone站点可以包含各种各样的工作流，包括私有工作流（private workflow），共有工作流（community workflow），一步式发布工作流（one-step publication workflow），等等。ZopeZen自带一个工作流，PloneCollectorNG也是自带一个工作流。DCWorkflow自带四个工作流。

Currently, two workflows come in the PloneWorkflows<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=PloneWorkflows" title="create this page">?</a> product in the collective project on SourceForge<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=SourceForge" title="create this page">?</a> (<a href="http://sf.net/projects/collective">http://sf.net/projects/collective</a>): the community workflow and one-step publication workflow. The community workflow is similar to the Plone workflow, with a few changes. The one-step publication workflow has two states: private and published.

目前，在SourceForge (<a href="http://sf.net/projects/collective">http://sf.net/projects/collective</a>)的集体项目（collective project）中PloneWorkflows产品携带了两个工作流：共有工作流和一步式发布工作流。共有工作流和Plone工作流类似，但稍有变化。一步式发布工作流包括两种状态：私有和（已）发布。

At the moment, you have no easy way to install and uninstall workflows, and you have no real easy way to transition content between one state and another. For example, if you install the one-step publication workflow into an existing state, you also need to fix the states for all objects and move them into one of the new states. In this case, it's probably simple-everything in a published state should stay as it is, and everything else should move into the private state.

此刻，你没有简单的方法来安装或卸载工作流，也没有真正简单的方法在任何两种状态间过渡内容。例如，如果你想在一个已经存在的状态下安装一步式发布工作流，你需要为所有的对象调整状态并且将它们转移至一个新的状态中去。这样的话，事情大概会简单的——即所有处于（已）发布状态的东西应该保持现有状态，其他的则该转移至私有状态。

设置初始状态

To set the initial state, go to the States tab and check out the states available; next to one of the states you'll see an asterisk, as shown in Figure 8-6.

设置初始状态时，点击状态标签（States tab）然后检查可用的状态；在图8-6中，有一个状态旁边是用星号（asterisk）标注的。

Figure 8-6. Setting the initial state for this workflow

图8-6 为这个工作流设置初始状态

You set the initial state for your workflow on this page by checking the box next to the state and then clicking Set Initial State. All content that uses this workflow will be created with an initial state. Any content that has already been created will remain in its initial state; changing the state afterward won't change that state. You can set only one initial state for each workflow.

通过逐项核对每个状态旁的复选框然后点击设定初始状态按钮（Set Initial State），你可以为你的工作流设置初始状态。所有使用这个工作流的内容在被创建时都会拥有一个初始状态。任何（在重新设置初态之前）已经被创建的内容仍将保持它已有的初始状态；后来改变的状态不会影响这些状态。你可以为每个工作流只设置一个初始状态。

编辑状态

The States tab lists the states that are present in this workflow. At the beginning of this chapter, I explained that a state represents an object at a particular point in time. Each state has an ID that's unique; this is usually a simple verb such as pending or published. To add a state, enter an ID and click Add at the bottom of the page.

状态标签（States tab）列出了在这个工作流中存在的所有状态。在本章开始，我解释过状态代表着对象处于某个特定的时间点。每种状态持有唯一的ID；通常，状态更像是一个动词，比如 草案（pending） 或 （已）发布（published） 一样。若要添加一个状态，就输入一个ID然后点击页面下方的添加（Add）按钮。

You'll also see the following options:

添加状态时你会看见下列选项：

Title: The title of the state is displayed in your Plone site and is a user-friendly version of the state.

标题 ：状态的标题在你的Plone站点中显示，实际上是状态这个比较抽象的概念对于用户来说较友好的一个表征（a user-friendly version of the state）。

Description: The description of the state is a long description of the state. This isn't currently shown to users but may be in the future.

描述 ：状态的描述是关于状态的一个详细的文字说明。目前来说它不会显示给用户，但也许会在未来派上用场。

Possible transitions: This lists all the possible transitions that can occur from the state. This list will show only if you actually have a transition in the system. Simply select the transitions that need to occur on this state. By selecting a transition for this state, you're selecting the start point for this transition to be this state.

可能存在的过渡 ：这一项列出了所有可能发生于状态之间的过渡。只有当你的系统真正用到过渡时它才会显示。我们只需要选择会在这个状态下发生的过渡。一旦你为这个状态选择好一个过渡，你也就选择了这个状态来作为这个过渡的开始点。

To alter a state, enter the changes and then click Save to commit the changes. The Permissions tab will open with the permissions that will be applied to an object while it's in this state. This may mean changing the permissions on an object when it transitions into that state. The form is rather self-explanatory; to enable an anonymous user to view the object, check the boxes that correspond to View and Anonymous and click Save, as shown in Figure 8-7.

若要改变一个状态，就输入变更然后点击保存按钮（Save）提交这些变更。许可标签（Permissions tab）打开时，如果对象在这种状态下，则会看到能应用其上的各种许可选项。这可能意味着当对象过渡至这个状态时，相应地要改变载于其上的各种许可。（图8-7中）这个表单是相当自明的（self-explanatory）；若要让匿名者可以查看对象，就勾选查看（View）和匿名者（Anonymous）旁边的复选框，并保存。见图8-7。

Figure 8-7. State permissions page

图8-7 状态许可的页面

If you change the permissions for a particular workflow state, you've created an issue that needs resolving. Any existing content in that state won't have the new workflow permissions set on it. The content will have the old workflow permissions, and you'll need to update them. When you've finished making all your changes, go to the root workflow page and click Update Security Settings, as shown in Figure 8-4. Performing that update may take a while depending upon the number of objects to be altered.

如果你改变了某个特定工作流状态的许可，你就创建了一个需要解析的结果。所有处于那个状态但已经存在的内容不会顺应新的工作流。这些已存在的内容持有的是旧有工作流许可，你需要更新（update）它们。具体来说，就是当你完成所有变更设置后，去工作流的根页面并点击更新安全设置（Update Security Settings），如图8-4所示。执行这个变更可能会花些时间，这取决于需要改变的对象的数量。

The Variables tab allows you to assign a value to a variable when the object is in this state. The workflow determines the list of variables available to each state. For more information on these, see the "Editing Variables" section.

变量标签（Variables tab）允许你当对象处于这种状态时赋（assign）一个值给一个变量。工作流会确定那些对应于每个状态的可用变量列表。关于这方面的更多内容，详见“编辑变量（Editing Variables）”部分。

编辑过渡（Transitions）

编辑过渡（Transitions）
,,,,,,,,,,,,,,,,,,,

The Transitions tab lists the transitions that will occur in this workflow. In the beginning of this chapter, I showed you how a transition represents the changes that will occur to the object. Each transition has a few variables that are shown on the summary page. To add a transition, enter an ID and click Add at the bottom of the page, as shown in Figure 8-8.

过渡标签（Transitions tab）列出了在工作流中将会发生的过渡。在本章开始，我向你展示了过渡如何作用于对象使其发生改变。每个过渡都有自己的摘要页面（summary page），其中含有一些变量（variables）。若要添加一个过渡，在过渡页面下方输入ID并点击添加按钮（Add），如图8-8。

Figure 8-8. Transition details page

图8-8 定义过渡的页面

If you now click a transition, you'll open the following details for that transition:

如果你点击了指向过渡的一个链接，就会打开一个用以显示该过渡的详细内容的页面。其中包括：

Title: This is the title for this transition.

标题: 过渡的标题。

Description: This is the detailed description for this transition.

描述: 关于该过渡的详细描述。

Destination state: This is the state that will be the target for this transition. The initial source state is defined by assigning the transition to the state.

目标状态: 目标状态是这个过渡发生时所要抵达的状态，可以把它理解为过渡的“靶子”。通过把携带了目标状态的过渡分配给初始状态，初始状态才被真正定义下来。

Trigger type: This indicates how the transition will be triggered. Automatic means that this will happen as soon as it moves into this state. Initiated by user action is the most common choice and means a user has enacted the transition by clicking a link.

触发器类型: 指出过渡如何被触发。自动式（Automatic）表示内容一旦移至该状态（从上下文和Plone机制分析，这个状态应该指的是初始状态，欢迎指正——译者注），这个过渡就会发生。而通过用户动作触发（Initiated by user action）是最通常的选择，意味着某个用户点击一个链接时就能触发这个过渡。

Script (before): This runs this script before this transition occurs.

脚本（之前）: 在这个过渡发生之前执行脚本（此时内容尚未到达目标状态——译者注）。

Script (after): This runs this script after this transition occurs.

脚本（之后）: 在这个过渡发生之后执行脚本（内容到达目标状态后，执行脚本——译者注）。

Guard: This is the security for this state (explained shortly).

安全: 该状态的安全设置（稍后再作解释）。

Display in actions box: This is how this transition will be displayed in Plone. Entering a value here also ensures that the transition will be entered as an action. You can then get this transition as an action by querying for actions.

动作箱中的显示方式: 是指这个过渡在Plone中如何显示。在这里输入值也可以确保把这个过渡作为一个动作来开始，你可以通过查询动作来获得这个过渡。

Of these values, the destination state is quite interesting. Although I've already mentioned that transitions normally change state, this isn't required. Because each transition can run scripts and write something into the history, it can be useful sometimes not to change state. For an example of this, see the "Using Workflow to Track Changes" section later in this chapter. If your transition does change the state, then select the new state as the destination state.

在上面罗列的各项中，目标状态（destination state）相当引人好奇。我已经提到过渡通常会改变状态，但这不是必需的。因为任何过渡都可以执行脚本、向历史记录中写入一些东西，在某些时候这样做会很有用。过渡 并不 只局限于改变状态。关于这方面的实例，可以阅读一下稍后出现的“运用工作流跟踪变化（Using Workflow to Track Changes）”章节。如果你配置的过渡确实需要改变状态，那么就选择一个新状态作为目标状态。

A transition can have multiple starting points but only one destination; if you need multiple destinations, you'll have to make multiple transitions. You can specify scripts to run before or after this transition. Two common examples are moving an object in workflow and sending an e-mail notification. The "Common Tasks and Examples" section covers both of these examples.

一个过渡可以有多个开始点（starting points），但只能有一个目标（状态）；如果你需要多个目标状态，你必须设置多个过渡。你可以指定脚本在过渡发生之前或之后运行——有两个常见的例子：在工作流中移动对象和发送e-mail通知。这些例子将在“常见任务和实例（Common Tasks and Examples）”一节见到。

Before any transition can be executed, a security guard checks the entire transition to ensure that the user running the transition has the right to do so. The guard has the following three components:

在过渡开始执行之前，安全设置（security guard）将检验所有的过渡来确保执行过渡的使用者有权限进行操作。安全设置由三部分组成：

Permission(s): These are the required permissions. Multiple permissions should have a semicolon (;) to separate them.

许可 ：包含了必需的许可。多个许可之间应该用分号（semicolon）分隔开。

Role(s): These are the required roles. Multiple roles should have a semicolon (;) to separate them.

角色 ：包含了必需的角色。多个角色之间应该用分号分隔开。

Expression: This is a workflow expression. For more information on this, see the "Editing Workflow Expressions" section later in this chapter. For each value specified, the guard must evaluate as true before continuing. If a test of any of the values fail, then the transition won't execute. Usually you'll find most guards have only one or two values specified.

表达式 ：是一个工作流表达式（workflow expression）。关于这方面的更多信息，请阅读本章稍后讲到的“编辑工作流表达式（Editing Workflow Expressions）”一节。在过渡执行之前，对于每一个已被指定的值，安全设置都要对其进行评估，以确保正确。如果对其中任一值的评估测试失败，这个过渡将不能执行。通常你会发现大多数安全设置只有一或两个被指定好的值。

编辑变量

The Variables tab lists the variables that will be created and changed in the workflow. I haven't discussed variables much with you up to this point; instead, I've focused on states and transitions. This section covers variables.

变量标签罗列出所有在工作流中被创建或被更改的变量。至此我还没有和你过多讨论变量，相反，我们刚刚关注了状态和过渡。这一节我们来研究一下变量。

It isn't always possible, and I don't recommend that you try, to encapsulate all the information you'll need in a workflow within just states and transitions. Instead, you can use variables to store some workflow-related information. For example, in the credit card bill example, the bill could be paid by several methods (Internet banking, check, and so on). You could store the amount method ($100, for example) in a variable. Should the bill be rejected or altered, that amount would be updated. The point of a variable is to have something that changes between each state and transition.

我并不赞成你尝试着将所有可用的信息以“填充胶囊”的方式汇集在一起并只运用状态和过渡来表达——这样做也是不太可能的。取而代之，你可以用变量来存储与工作流相关的信息。举个例子，信用卡账单可以多种方式支付（网上银行或支票等等）。你可以把支付的钱（比如100美元）存储在一个变量里。账单被拒绝或被更改时，支付的钱数（这个变量）都会更新。变量的作用就是持有一些在每个过渡与状态之间发生改变的元素（something）。

So, returning to the main workflow page, click the Variables tab to get a list of all the variables. To add a variable, enter a variable ID and click Add at the bottom of the page. To determine what state an object is in at any time, DCWorkflow<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=DCWorkflow" title="create this page">?</a> stores the current state in a variable on the object. The default name of that variable is review_state.

那么，返回到工作流的主页面，点击变量标签（Variables tab）就能得到一个包含所有变量的列表。需要添加变量时，可以输入 变量 ID，然后点击页面下方的添加（Add）按钮。DCWorkflow在一个变量中保存着对象目前所处的状态，这样就可以在任何时候去查看此对象的状态了。那个变量的默认名称是 review_state 。

NOTE If you need to change this because it conflicts with another name, you can do so at the bottom of that page. However, doing this will cause all your current objects to lose their state, so be careful about changing that value.

注意 如果你是因为这个变量的名称和其他变量名称发生冲突而这么做，那么你可以在页面下方来更改名称。然而，这样做会让你所有的对象失去它们的状态，所以对这个值的改变，你要慎重考虑。

Each workflow variable has the following properties:

每个工作流变量含有下列属性：

• Description: This is the variable description.
• 描述 ：对变量自身的描述文字。
• Make available to catalog: These variables will be placed in a list exposable to the catalog. This doesn't add indexes or metadata to the catalog; you still have to do that manually.
• 在目录中有效 ：此项属性表明这些变量会被置入一个列表，并显式地存在于目录（catalog）中。变量在目录中有效并不意味着向目录中添加了索引（indexes）或元数据（metadata）；你仍然要自己动手去做。
• Store in workflow: This determines if the information is to be stored in the workflow or on the object.
• 存储在工作流中 ：此项属性会检查信息是否被保存在工作流中，或是附加在对象上。
• Variable update mode: This determines when to update the variable.
• 变量更新模式 ：此项属性检查什么时候来更新变量。
• Default value: This determines a default value as a string.
• 默认值 ：此项属性认为默认值是一个字符串，对其进行检查。
• Default expression: This is the default value as an expression. If this is present, it'll be used instead of default value (for more information, see the "Editing Workflow Expressions" section later in this chapter).
• 默认表达式 ：此项属性中的默认值是一个表达式。如果它出现在此，就会被用来替代默认值（更多信息，请阅读本章后面的“编辑工作流表达式（Editing Workflow Expressions）”一节）。
• Info. guard: These are security settings for accessing this variable. These guard settings are similar to the guard settings for a transition; however, the guard occurs when accessing the variable here.
• 信息安全设置 ：此项属性包含了访问变量时所定义的安全设置。这些安全设置和过渡中的安全设置很相似；但是这里说到的安全性检查是在访问变量时才会发生的。

编辑工作列表（Worklists）

编辑工作列表（Worklists）
,,,,,,,,,,,,,,,,,

The Worklists tab provides access to all the worklists that are assigned in this workflow. A worklist is a method of querying the workflow for information about the numbers of objects in that workflow. For example, I'd like to be able to easily ask the workflow for all the outstanding credit card bills I have.

工作流中所有被分配的工作列表，是由工作列表标签（worklists tab）来提供对它们的访问（access）。 工作列表 是一种用于查询（querying）工作流中特定信息的方法（method），它被用来查询存在于工作流中的对象数目的信息。例如，我希望很容易地从工作流中查询出全部尚未付清的信用卡。

To add a worklist, enter an ID and click Add. Each worklist has the following properties:

添加工作列表时，输入ID并点击添加按钮（Add）。每个工作列表含有下列属性：

• Description: This is a description of the worklist.
• 描述 ：对工作列表自身的描述文字。
• Cataloged variable matches: This is the value that the worklist must match to be added in this worklist. The variable matched is the workflow state variable given in the variables list (the default variable name for this variable is review_state).
• 编成目录的变量匹配 ：此项属性包含的是工作列表必须匹配的值，此值被添加在这个工作列表中。进行匹配的变量是变量列表中给出的工作流状态变量（workflow state variable）（这个变量的默认名称是 review_state ）。
• Display in actions box: This is information to display on the user interface. Entering a value here also ensures that the transition will be entered as an action. You can then get this transition as an action by querying for actions.
• 在动作箱中（actions box）的显示 ：此项属性包含的东西将会以某种形式在用户界面上表现出来。在这里输入值也可以确保过渡会以一个动作作为开始。然后你就可以通过查询动作来获取这个过渡。
• Guard: This is a guard for accessing this worklist.
• 安全设置 ：此项属性包含了访问工作列表时所定义的安全设置。

Returning to the credit card example, if I wanted to know all the credit card bills that need reviewing by me, then I could place this information in a worklist. First, the variable review_state would contain the current state for each item. All the credit card bills that need reviewing would be in the review state. Second, I'd add a worklist called review_queue, and the value for variable would be pending. I could now ask the worklist for all the items in the review_queue.

回到信用卡的例子，如果我想知道哪些信用卡需要自己来审核，那么我可以把这些信息置入一个工作列表中。首先， review_state 变量会包含有每张信用卡当前的状态，而那些需要审核的信用卡会在审核（review）状态下。其次，我已经添加了一个名为 review_queue 的工作列表，其中，变量的值会是 pending （中文译为“未决的”，在默认的中文Plone中也有“提交”的意思——译者注）。现在，我就可以在 review_queue 这个工作列表中查询所有的信用卡项目（items）了。

Although a worklist is a convenient way of storing this information, Plone doesn't use them. Instead, Plone uses ZCatalog<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=ZCatalog" title="create this page">?</a> directly to query objects that are workflowed. Since the DCWorkflow<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=DCWorkflow" title="create this page">?</a> worklist uses the catalog tool, the end result is the same.

尽管工作列表是存储此类信息的便利方式，但是Plone并不使用这些信息，它以另一种方式——ZCatalog——替代工作列表。Plone直接用ZCatalog查询那些处于工作流内（workflowed）的对象。从DCWorkflow使用目录工具以来（catalog tool），最终的结果都是一样的。

编辑脚本

The Scripts tab lists the scripts that are available this workflow. This list is actually a standard folder in the ZMI, and you can add almost anything there. Since the main reason you'd want to do this would be to add a script to perform advanced handling of transitions, you should add only Script (Python) objects here.

脚本标签（Scripts tab）列出了工作流中有效的脚本。这个列表实际上是ZMI中的标准文件夹（standard folder），你几乎可以在这里添加任何东西。既然你希望在这里添加脚本的主要原因是想对过渡进行高级处理，那么你应该只添加脚本（Python）对象。

To add a script from the Scripts tab, select Script (Python) from the Add drop-down menu, and give the script an ID. The script is passed one and only one object, which is the base workflow expression object; for more information on this object, see the "Editing Workflow Scripts" section later in this chapter. For example, if you need to access the actual object in the workflow, you can use a Python script such as the following:

若要从脚本标签（Scripts tab）中添加脚本，先从添加（Add）下拉菜单中选择Script(Python)，然后给所要添加的脚本起个ID名。一个脚本只被传递给一个对象——即基本工作流表达式对象；关于这个对象的更多信息，请阅读本章稍后介绍的“编辑工作流脚本（Editing Workflow Scripts）”一节。先来举个例子，如果你需要访问目前存在于工作流中的对象，你可以用下面这个Python脚本来实现：

##parameters=state_change
obj = state_change.object

What happens in this script is up to the developer-you can run almost anything here. You can trigger events, and you can access other workflows and transitions. For some example scripts, see the "Sending E-Mail Notifications" and "Moving Objects" sections later in this chapter. When the script executes, it will execute as the user who initiated the transition. You could assign proxy roles on the script if it needs to happen as someone else. Returning to the transitions, you can assign this script to any number of transitions in the script (after) and script (before) settings. You can run the script either before or after a transition.

这个脚本中将会发生的事情完全要依赖于开发者——作为开发者，你在这里几乎可以做任何事情（you can run almost anything here）。你可以引发事件，你也可以访问其他的工作流和过渡。本章稍后介绍的“发送E-Mail通知（Sending E-Mail Notifications）”和“移动对象（Moving Objects）”两节会给出一些脚本实例。当脚本执行时，往往是启动了过渡的用户同时启动了脚本。如果需要让其他人来这样做，你可以把代理人角色（proxy roles）分配到脚本中。在返回过渡时，你可以在 script(after) 和 script(before) 设置中把脚本分配给任意数量的过渡。你可以在过渡发生之前或之后执行脚本。

编辑许可（Permissions）

编辑许可（Permissions）
,,,,,,,,,,,,,,,,,,,

The Permissions tab lists the permissions that are managed by this workflow. You've seen these permissions already when examining the states. You set the list of permissions manageable in those states in this tab. To add a new permission, select the permission from the drop-down box and select Add.

许可标签（Permissions tab）列出了可被这个工作流管理的所有许可。在检查状态时你已经见到这些许可了。在这个标签下，你建立了一系列可供管理的许可，它们存在于各种状态下。若要添加一个许可，从下拉菜单中选择permission然后选择添加（Add）。

编辑工作流脚本

Scripts are an opportunity for the developer to perform some logic upon a transition. That logic can be almost anything you want. You could be checking that some conditions have been performed (for example, is the document spell checked?) or that some special actions have been performed. When the object is transitioned, the script will be called.

脚本为开发人员提供了机会，使他们可以在过渡之上执行一些逻辑——几乎可以是任何你想要的逻辑。你可以检查一些条件是否已被执行（例如文档拼写检查是否执行了？）或者一些特殊动作是否已被执行。当对象处于过渡时期，脚本就会被唤起执行。

When a script is called, one extra parameter is passed to that script. That extra parameter provides access to all sorts of transition-related elements and attributes. That parameter is called the state_change parameter, and it has the following attributes:

当脚本被唤起执行时，会有一个额外的参数传递给它。这个额外的参数提供了对与过渡相关的各种元素和属性的访问通路。这个参数被称作state_change参数，它有如下属性：

status: This is the workflow status.

status: 工作流状态。

object: This is the object being transitioned in the workflow.

object: 在工作流中历经过渡的对象。

workflow: This is the current workflow object for the object being transitioned.

workflow: 历经过渡的对象所依赖的当前工作流对象。

transition: This is the current transition object being executed.

transition: 当前正在执行的过渡（过渡也被看作是一个对象）。

old_state: This is original state of the object.

old_state: 历经过渡的对象的原始状态。

new_state: This is destination state of the object.

new_state: 历经过渡的对象的目标状态。

kwargs: These are keyword arguments passed to the doActionFor method.

kwargs: 传递给 doActionFor 方法的关键字自变量。

getHistory: This is a method that takes no parameters and returns a copy of the object's workflow history.

getHistory: 一个不含参数的方法，返回对象的工作流历史的一个拷贝。

getPortal: This is a method that takes no parameters and returns the root Plone object.

getPortal: 一个不含参数的方法，返回Plone的根对象（root Plone object）。

ObjectDeleted<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=ObjectDeleted" title="create this page">?</a>(folder): This tells workflow that the object being transitioned has been deleted; it takes the object to which you'd like to return the user. Pass to the exception the folder you'd like the user to be redirected to (see the "Moving Objects" section later in this chapter).

ObjectDeleted<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=ObjectDeleted" title="create this page">?</a>(folder): 告诉工作流历经过渡的对象已经被删除；它含有你希望返还给用户的对象，它会转到异常，把用户重定位到你希望的folder（可参考本章后面的“移动对象”一节）。

ObjectMoved<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=ObjectMoved" title="create this page">?</a>(newObject, newObject): This tells workflow that the object being transitioned has moved. Pass to the exception the folder you'd like the user to be redirected to (see the "Moving Objects" section later in the next chapter).

ObjectMoved<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=ObjectMoved" title="create this page">?</a>(newObject, newObject): 告诉工作流历经过渡的对象已经被移动。它会转到异常，把用户重定位到你希望的folder（可参考本章后面的“移动对象”一节）。

WorkflowException<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=WorkflowException" title="create this page">?</a>: This raises an expectation back to workflow and aborts the transaction (and hence the transition).

WorkflowException<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=WorkflowException" title="create this page">?</a>: 抛出一个异常，回到工作流并中止事务（在这种情况下中止的是过渡）。

getDateTime: This is a method that takes no parameters and returns the DateTime<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=DateTime" title="create this page">?</a> object that relates to the transition.

getDateTime: 一个不含参数的方法，返回与过渡相关的DateTime对象。

For example, to find out what state is being transitioned to and when, the following is a Script (Python) object that will tell you just that information. This script logs the information about the transition into the log file:

举个例子，如果想要知道哪些状态以及在什么时候历经过渡，下面的（Python）脚本对象可以告诉你答案。这个脚本会把你想了解的过渡信息记录到日志文件（log file）中：

##parameters=state_change
st = 'From %s to %s on %s' % (
    state_change.old_state,
    state_change.new_state,
    state_change.getDateTime())
context.plone_log(st)

TIP When you're writing a Script (Python) object, you may need to print to the log file to help with debugging. A script called plone_log does this, which takes a string and passes it to Plone's logging functions. Hence, calling context.plone_log is a useful tool for debugging.

提示 当你撰写（Python）脚本对象的时候，你可能需要把它打印到日志文件中以备用来帮助调试。一个叫做plone_log的脚本会做这些工作，它会获取一些字符串信息并把这些信息传递给Plone的日志函数（Plone's logging functions）。之后便可使用context.plone_log，它是进行调试的有用工具。

When assigning a script to a transition, you have two choices: before and after. As the names suggest, a script that's set assigned to before runs prior to the transition running. This is suitable for scripts that may check if something should happen prior to the transition running, such as testing that another dependent object or page has been uploaded or there are no spelling errors. The script assigned to after runs once the transition completes-although if at any time an uncaught exception is raised on a script, this will cause the transition to fail, the object to remain in its original state, and the exception to display to the user.

当把脚本添加给过渡时，你有两种选择：before和after。正如这两个名字暗示的——以before形式添加的脚本会在过渡运行之前执行，before形式适合于那些在过渡运行之前能够检查某些事情是否应该发生的脚本，像测试其他需要依赖的对象或页面是否已被提交、或者是否没有拼写错误。以after形式添加的脚本会在过渡完毕后立即运行。虽然在任何时候，未被捕获的异常可在脚本运行时被抛出，但是这都会引发过渡失败。对象仍会保持它原来的状态，异常则会显示给用户。

编辑工作流表达式

Throughout this chapter you've seen values that can be expressed as workflow expressions. For example, the value assigned to a variable is the result of a workflow expression. This expression is nothing special; it's merely a Template Attribute Language (TAL) expression with a few different variables available. You already learned about TAL expressions in Chapter 5, so you should be familiar with these expression and all their options, such as Python, string, and path expressions.

贯穿本章你已纪看到值串（values）可以用工作流表达式（workflow expressions）表达。举个例子，赋给一个变量的值是（或称来自于）一个工作流表达式的结果。这个表达式没有什么特殊的；它只不过是一个模板属性语言（简称TAL）表达式并带有一些不同的可用变量。你已经在第5章学习了TAL表达式，那么你应该熟悉这些表达式和它们的选项，像Python表达式、字符串表达式和路径表达式。

Unlike the standard TAL expression, a few extra parameters are passed through to the namespace, relating to the particular workflow. The namespace for a workflow expression contains the following:

不像标准的TAL表达式，一些额外的参数直接由名字空间传递过来（passed through to the namespace），与特殊的工作流相关联。一个工作流表达式的名字空间包含有：

• here: This is the object being transitioned in the workflow.
• here: 在工作流中历经过渡的对象。
• container: This is the container of the object being transitioned in the workflow.
• container: 在工作流中历经过渡的对象的容器。
• state_change: This is the state change object referenced in the "Editing Workflow Scripts" section.
• state_change: 这个是在“编辑工作流脚本”一节提到的状态改变对象（state change object）。
• transition: This is the transition being executed, identical to state_change.transition.
• transition: 正在被执行的过渡，等同于 state_change.transition。
• status: This is the original state, identical to state_change.old_state.
• status: 原始的状态，等同于state_change.old_state。
• workflow: This is the workflow for this object.
• workflow: 对象所依赖的工作流。
• scripts: These are the scripts available in this workflow.
• scripts: 工作流中可用的脚本。
• user: This is the user executing this transition.
• user: 执行此过渡的用户。

通过ZMI撰写工作流

Probably the simplest but most laborious way to write workflow is to use the ZMI. Although the ZMI drives many people crazy, it's a simple way to set up the options. Unfortunately, once you've started writing through the ZMI, you're stuck in that paradigm. In other words, there's no easy to edit or alter that workflow on the file system. I discussed editing a workflow through the Web with you earlier in this chapter, of course.

可能最简单但是最费力的方式是使用ZMI撰写工作流。尽管ZMI让很多人抓狂，但它仍是建立各种选择的简单方式。不幸地是，一旦你已经开始通过ZMI撰写工作流，你会对这种方式产生依赖。换句话说，今后在文件系统中没有容易的方法编辑或更改那些工作流。当然，在本章早些时候我和你探讨了通过Web编辑工作流。

To export a workflow from the ZMI, click portal_workflow and select the Contents tab. Select the created workflows you'd like to export by checking the boxes on the left of the ZMI, and then click import/export. At the top part of the export page, select Download to local machine, and click export. A file with extension .zexp will be created that can be saved and redistributed. Selecting XML Format will provide a file in Extensible Markup Language (XML) format with an .xml extension.

若要从ZMI中输出工作流，点击portal_workflow选择内容标签（Contents tab），在已经建立的工作流中选择你希望输出的，先勾选ZMI左边的方框，然后点击import/export。在输出页的顶部选择Download to local machine，再点击export。这样，一个带有.zexp扩展名的文件被创建了，并可以保存下来也可分发。选择XML Format会生成一个可扩展标记语言（XML）格式的文件，带有.xml扩展名。

If you're provided a workflow in a the .zexp or .xml format, then importing the workflow into your Plone is straightforward. Place that file in the import directory of Zope on the file system. This can be the instance home directory or the Zope directory.

如果你有.zexp或.xml格式的工作流，那么把这个工作流导入Plone中是很简易的，在发文件系统中，把这个文件移动到Zope的导入目录下就可以。导入目录可以是实例化的主目录或Zope目录。

Then click portal_workflow, select the Contents tab, and click import/export. At the bottom part of the page, you'll see a small form that takes an import filename. Enter the name of the filename there, and leave Take ownership of imported objects selected. Click the Import button to import the workflow. The workflow will now be imported and given the name specified in the export.

然后点击portal_workflow，选择内容标签（Contents tab），选择import/export。在页面底部，你会看见一个小表单，含有导入文件名的输入框。在输入框中输入文件名，然后勾选Take ownership of imported objects。点击导入按钮导入工作流。现在工作流将被导入，并配以在输出时确定的名称。

用Python撰写工作流

Using Python is probably the favorite way of programmers to write a workflow, since it can all be done in Python and easily distributed. First, make a Python module on the file system. At the top of the file, import the appropriate tools, as follows:

使用Python撰写工作流可能是最受程序员欢迎的方式，因为这些都可以用Python来做并能很容易地分发。首先，在文件系统中建立一个Python模块（即一个Python文件，可以.py为扩展名，含有Python代码——译者注），在文件开头，导入合适的工具，如下所示：

from Products.CMFCore<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=CMFCore" title="create this page">?</a>.WorkflowTool<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=WorkflowTool" title="create this page">?</a> import addWorkflowFactory
from Products.DCWorkflow<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=DCWorkflow" title="create this page">?</a>.DCWorkflow<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=DCWorkflow" title="create this page">?</a> import DCWorkflowDefinition<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=DCWorkflowDefinition" title="create this page">?</a>

Second, make a function that creates the workflow. Appendix A lists the API for writing a workflow in a little more detail. But you could just cheat and look at all the great examples available in the PloneWorkflow<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=PloneWorkflow" title="create this page">?</a>'s project in the collective (<a href="http://sf.net/projects/collective">http://sf.net/projects/collective</a>), or even the ones contained in Plone. For example:

然后，建立一个创建工作流的函数。附录A更详细列出了撰写工作流时需要用到的API。但是你可以先不那么用功。只需去collective（<a href="http://sf.net/projects/collective">http://sf.net/projects/collective</a>）看看PloneWorkflow项目中那些优秀的例子，或者Plone系统中的一些实际例子。例如:

def sample(id):
    """ Sample workflow """
    ob = DCWorkflowDefinition<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=DCWorkflowDefinition" title="create this page">?</a>(id)
    ob.states.addState('private')
    ob.states.addState('public')
    # add transitions
    return ob

Finally, register the workflow in the system, like so:

最后，在系统中注册工作流，如下所示：

addWorkflowFactory(sample,
                   id='sample_workflow',
                   title='Sample workflow')

This script will need to be as part of a product installation. Chapter 12 covers writing and installing products.

这个脚本需要作为一个产品的一部分安装上去。第12章介绍撰写和安装产品。

Now, of course, a shortcut is available, which is called DCWorkflowDump<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=DCWorkflowDump" title="create this page">?</a>. This will take the code from the ZMI and dump it into a Python module for you. You can find the source code for DCWorkflowDump<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=DCWorkflowDump" title="create this page">?</a> in the collective at <a href="http://sf.net/projects/collective">http://sf.net/projects/collective</a>, but you can also find a zip file of the code on the Plone book Web site at <a href="http://plone-book.agmweb.ca">http://plone-book.agmweb.ca</a>.

当然现在有一个捷径——有一个产品叫DCWorkflowDump。它能够从ZMI中集成代码，为你装配成Python模块。你可在 <a href="http://sf.net/projects/collective">http://sf.net/projects/collective</a> collective中找到DCWorkflowDump的源代码，你也能在Plone Book网站 <a href="http://plone-book.agmweb.ca">http://plone-book.agmweb.ca</a> 找到源代码的zip文件。

To install DCWorkflowDump<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=DCWorkflowDump" title="create this page">?</a>, unzip the file and copy the directory called DCWorkflowDump<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=DCWorkflowDump" title="create this page">?</a> into the Products directory of your Plone installation. To check that you're in the right directory, your Products directory should also contain a directory for DCWorkflow<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=DCWorkflow" title="create this page">?</a>, among other things. Then restart your Plone instance.

安装DCWorkflowDump时，解压缩文件然后把DCWorkflowDump目录拷贝到你的Plone安装路径的Products目录下。验证你的目录是否正确，它应该包含有DCWorkflow目录以及其他目录。然后重新启动你的Plone实例。

Once you've restarted Plone, go to the particular workflow in the ZMI, and you'll notice a new tab called dump. Click that page to get the dump screen, and then click Dump it! to dump the workflow to the screen. This will take your workflow and format it in Python for you. Save that file to your product, and you now have a Python file you can manipulate. This product is a great tool because it allows you to create the workflow in the ZMI and then distribute and alter it through Python.

一旦重启Plone，访问ZMI中的工作流，你会发现一个新的标签dump。进入那个标签页面浏览一下，然后就可以点击Dump it!来装配工作流了。它会收集你的工作流并把它们转换成Python模块。在产品中保存这个模块文件，现在你就可以利用它了。这是很棒的产品因为它允许你在ZMI中创建工作流，并通过Python模块的形式分发和改变它。

From panjy Mon Feb 14 00:51:18 +0800 2005 From: panjy Date: Mon, 14 Feb 2005 00:51:18 +0800 Subject: NG的翻译 Message-ID: <20050214005118+0800@nocache.czug.org>

NG应该不是那个NG ;-) 据我了解是Next Generation的意思，也就是下一代的新版本。PloneCollectNG之前, 有CMFCollector, CMFCollectorNG<a class="new" href="http://members.czug.org/plone/newplonebook/Chapter8/createform?page=CMFCollectorNG" title="create this page">?</a>等替代产品。

From unknown Thu Oct 13 09:45:48 +0800 2005 From: Date: Thu, 13 Oct 2005 09:45:48 +0800 Subject: dsfasd Message-ID: <20051013094548+0800@www.czug.org>

sdfksgj

From unknown Mon Nov 14 08:23:08 +0800 2005 From: Date: Mon, 14 Nov 2005 08:23:08 +0800 Subject: 翻译问题 Message-ID: <20051114082308+0800@www.czug.org>

“首先，DCWorkflow假定在系统中存在一种对象（object）——比如一条内容或一个配件。然后它又进一步假定，属于同类型的对象会通过同一个工作流。而通过重新规划（repurposing）内容（阅读第11章可获得更多此方面的知识），你可以使用不同的工作流来持有相似的内容。”中的最后一句应该是“你可以让相同的内容使用不同的工作流”。