Task 4 requires both A and B as inputs in a single input criterion.
Task 4要求同时将A和B用作单个输入条件的输入。
Task 4 requires creating deployable packages for the following applications
任务4需要为以下应用程序创建可部署包
Task 4: Create a Web service to expose functionality provided by the generated J2C bean.
任务4：创建一个Web服务来揭示由产生的J2Cbean指定的功能。
For a single parallel execution of Task 2 and Task 3, we obtain two executions of Task 4.
对于Task2和Task3的单次并行执行，我们将执行Task 4两次。
Thus, we explicitly added the situation to the model when Task 3 and Task 4 execute in parallel.
因此，我们在模型中显式添加了Task3和Task 4并行执行的情况。
This means Task 4 in the anti-pattern cannot execute, although the task has all its inputs connected.
这意味着，虽然反模式中的任务Task 4 的所有输入都已经连接了，但该任务仍然无法执行。
In any execution of the process, both inputs will never be produced and thus, Task 4 cannot execute.
在此流程的任意执行过程中，将永远不会产生这两个输入，因而无法执行Task 4。
If an input is not required, but optional, two possible solutions would correct the input behavior of Task 4.
如果某个输入不是必需的，而是可选的，那么有两种可能的解决方案可以用来修正Task 4的输入行为。
Both solutions enable Task 4 to execute correctly and independently of the branching decision in the decision gateway.
两种解决方案都能使Task 4在不依赖于decision网关中的分支决策的情况下正确地执行。
The pattern in Figure 20 shows the first solution, where the minimum multiplicity of item D as input of Task 4 is set to zero.
图20中的模式显示的是第一种解决方案，在其中，项目D被作为Task 4的输入，它的最小增殖次数被设置为零。
Task 4: Devise a strategy for a patient to decide whether to take an offered kidney, or to even participate in a kidney exchange.
任务4：为病人设计一种对策以决定是否要接受一个提供给你的肾，或者甚至去参与肾交换计划。
This use of the stop node is correct, because task 4 is the last executing task of this process and no other activities execute in parallel.
在此处使用停止节点是正确的，因为Task 4是该流程执行的最后一个任务，而且没有与之并行执行的活动。
Using a stop node instead would not be a correct solution, because it would immediately end the whole process and prevent execution of Task 4.
此处如果换成停止节点将是一个错误的解决方案，因为它会立即终止整个流程，Task 4将不会执行。
The pattern in Figure 21 shows the second solution by defining several input and output criteria for Task 4 that correctly match the alternative branches.
图21的模式显示了第二种解决方案，它为Task 4定义了几个输入和输出条件，这些条件可与可选分支正确匹配。
For the first two choices, a single sequential execution path results, while the choice of Task 3 and Task 4 results in both branches executing in parallel.
对于前两个选择，将只导致一条后续执行路径，而同时选择Task3和Task 4将导致并行执行这两个分支。
The simulation in Business Modeler 6.0.2 currently shows that two as and two Cs leave the join in the pattern in Figure 13, which causes Task 4 to execute twice.
目前在Business Modeler6.0.2中进行的模拟表明，各有两个a和c离开了图13所示的模式中的join，这使Task 4被执行了两次。
The anti-pattern in Figure 19 shows a process model with alternative branches where item D, which is only produced by the lower branch, bypasses the merge to enter Task 4 directly.
图19 中的反模式显示了一个含有可选分支的流程模型，其中的项目D 只能由下面的那条分支生成，它绕过merge，直接进入Task 4 。
When you design activities for reuse, such a duplication is a strong limitation, because any reusing process must provide two as and two Cs as input to task 4, or the task cannot execute.
当您设计可供重用的活动时，这种复制会成为严重的限制，因为任何重用过程都必须提供两个a和两个C作为Task 4的输入，否则任务就无法执行。
Task 4 has an input criterion requiring only business items A and B for the upper branch, while for the lower branch it has a separate criterion that includes business items A, B, and D.
Task 4有一个输入条件，只需将业务项A和B 提供给上面的分支，而它针对下面分支的则是一个单独的条件，其中包含业务项 A、B 和D。
The uncontrolled iteration of Task 4 and Task 5 becomes evident during a simulation, because for each execution of the fork with its two outgoing branches, the corresponding merge executes twice.
在模拟期间，Task 4和Task5的无控制迭代将显现出来，因为每次执行fork将得到两个传出分支，因此其相应的merge将执行两次。
If users start working on tasks in their group task list, it might result in conflict 4 - many people will start working on the same task.
如果用户开始执行在他们组任务列表中的任务，最终可能会引起冲突4——可能有多人开始执行相同的任务。
For these automatic deletion options, you can also specify whether a task is only deleted automatically if it completed successfully (Figure 4).
对于这些自动删除选项，还可以指定是否只删除成功完成的任务(图4)。
Tables 2, 3 and 4 show which defaults apply for which human task or business process authorization role.
表2、3和4显示了哪个缺省值适用于哪个人工任务或业务流程授权角色。
In the integrated portal environment, one can both access a task list (see Figure 4) and work on tasks.
在集成门户环境中，既可以访问任务列表(请参阅图4)，也可以处理各项任务。
Listing 4 shows a snippet of code to perform the task.
清单4显示了执行此任务的代码片段。
RMC creates and manages the HTML behind the scenes that provides the well-formatted and hyperlinked documentation that you saw in Figure 4 (showing a preview of page documenting a task).
RMC在后台创建和管理HTML——它提供了格式良好的，带有超链接的文档，如你在图4中所见（显示了一个任务的文档的预览）。
For example, the task in Listing 4 would begin to execute the four rules identified by their names for the project named BANK.
例如，清单4中的任务将开始执行项目BANK中的4个规则(以名称标识的)。
Refer to Listing 4 to see an example of the task created.
参考清单4中创建任务的例子。
In addition, you can define a default activity administrator on process level (see Figure 4, second human task specification).
另外，您还可以在流程级别定义缺省活动管理员(参见图4，第二个人工任务规范)。
Listing 4: Locating the right module for a task.
清单4：为任务定位适当的模块。
应用推荐