人工任务的另一种状态是子任务状态。
将所有的子任务结果组合为最终结果。
首先，确保所有子任务完成。
支持特别的人员协作，包括子任务和后续任务。
Support for human ad-hoc collaboration includes subtasks and follow-on tasks.
对于每个分配的用户，自动地创建一个子任务。
您可以取消子任务并查看已完成的子任务的结果。
You can cancel subtasks and view the results of completed subtasks.
您希望进一步分析这个活动及其子任务。
You want to analyze this activity and further detail its sub-tasks.
在此场景中，该任务称作是流程的“子任务”。
The task is said to be a “child task” of the process in this scenario.
在编写测试时，我发现了另一个重要的子任务。
As I wrote tests, I discovered another important decomposed task. Here is the entire list.
如图1 所示，流程中的前三个子任务分别是
The first three sub-tasks in the process, as listed in Figure 1
甚至在主要任务中，也要留意将需要大多数工作的子任务。
Even within the major tasks, look at the subtasks that are going to require the most work.
一个任务的取消操作也可以传递给所有的子任务。
每个内部节点必须等待(依赖于)其两个(或多个)子任务。
Each internal node must wait (depend on) its two (or more) child tasks.
实际上，这还牵涉到在他周围等待他人的来完成他们的子任务。
In practice, that may involve a lot of waiting around for others to complete their subtasks.
这些需求依次定义了工作目标以及子任务职责所处的工作模式。
These needs, in turn, define the goals of the effort and the manner in which responsibilities for subtasks are allocated.
作业调度器生成多个线程，每个线程包含执行不同子任务的代码。
The job dispatcher spawns multiple threads, each containing the code for a different subtask.
为了方便起见，我们将整个开发工作划分为多个增量型的子任务。
For convenience, we subdivide the overall development effort into a number of incremental sub-tasks. In this installment we provide a detailed walkthrough of the following subtasks.
MyTasks小部件可以查看有关挂起的子任务的任务状态。
The MyTasks widget can view task status on pending subtasks.
在这些线程中，半数线程会用几乎整个生命周期来等待子任务的完成。
And, of those, half would spend almost their entire lives waiting for subtasks to complete.
可以使用可选的完成功能提前完成任务，即使子任务还没有全部完成。
An optional completion function is available to preemptively complete the task, even if all of the subtasks are not yet completed.
子任务完成或满足完成条件之后，需要把结果聚合为人工任务的输出。
Once the subtasks have completed or the completion condition has been met, the results need to be aggregated into the output of the human task.
线程在作业调度器上调度，所以理论上讲，该机器不应该用于执行任何子任务。
Threads are scheduled on the job dispatcher, so ideally this machine should not be used to execute any subtasks.
剖析我们的用例，您可以看到它们现在全都由少数公共子任务组成。
Deconstructing our use cases, you can see that they are now all composed of a few common sub-tasks.
不管在整个任务构想中该子任务是如何小或者如何不显著，只要行动。
No matter how small or how insignificant in the overall picture, just get moving.
最后一个任务组被定义为set，所以用户可以用任何顺序随意地完成子任务。
The last task group is defined as a set, so the user is free to complete the subtasks in any order.
您可以创建子任务以将工作委托给另一个用户、查看子任务，以及查看子任务的状态。
You can create a subtask to refer work to another user, view subtasks, and view their status.
您可以向该子任务状态添加升级，以确保完成任务的该部分，以便总体任务能够继续。
You can add escalations to the subtask state to ensure that this portion of the task is completed so that the overall task can proceed.
根任务组的种类属于choice，这意味着用户能够选择任何子任务组并完成它。
The root task group is of the choice kind, which means the user can select any subtask group and complete it.
TaskInformation小部件已经过了增强，可以在特别场景中利用子任务。
The task Information widget has been enhanced to exploit subtasks for ad-hoc scenarios.
清单3中的备忘单内容定义了包含两个子任务组的根任务组，每一个子任务组包含两个任务。
The cheat sheet content in Listing 3 defines a root task group containing two subtask groups, each containing two tasks.
应用推荐