清单12处理可分配任务实例。
清单15任务实例创建处理器。
可以自动地删除业务过程实例和人工任务实例。
The automatic deletion of business process instances and human tasks instances can be modeled.
BPC提供用来查询和删除过程和任务实例的函数。
BPC provides functions to query and delete process and task instances.
长时间运行的业务流程和任务实例存储在数据库中。
Long-running business process and task instances are stored in a database.
人工任务：HumanTasks显示人工任务实例。
清单8自定义任务实例的Hibernate映射文件。
任务实例的完成伴随有一个变迁(一般是回到任务节点)。
Task instance completion is accompanied by a transition (typically back to task node).
这就要求修改jBPM提供的任务和任务实例类。
This required modifications to both task and task-instance classes provided by jBPM.
类似，一个任务实例——任务的运行时表示——就会被创建。
Similarly a task-instance – run time representation of a task is created.
流程定义描述流程实例的方式类似任务描述任务实例的方式。
A process definition describes a process instance in a manner similar to the way a task describes a task instance.
您可以从模板创建并启动一个流程或任务实例并对其加以利用。
From a template, you can create and start a process or task instance and work with it.
这个处理器首先记录上报计数器，接着完成此节点关联的任务实例。
This handler first pegs the escalation counter and then completes a task instance, associated with this node.
BPCExplorer在它自己的事务中删除每个过程或任务实例。
The BPC Explorer deletes each process or task instance in its own transaction.
originator %与作为任务实例发起者的人员的用户ID绑定。
HTM: task.originator % is bound to the user ID of the person who is acting as the originator of the task instance.
接着，任务实例可以被终结，这意味着任务实例内标志为完成。
Then, task instances can be ended, which means that the task instance is marked as completed.
活动任务实例的数量(模拟处于活动状态时任务上面的框中的数字)增加。
The number of active task instances (the number in the box above the task when the simulation is active) increases.
另外，如果两个线程同时删除过程或任务实例，会导致在日志中记录错误消息。
Also, if the process or task instances are deleted by two threads simultaneously, this results in error messages in the logs.
第2部分介绍清理已完成的过程和任务实例以保持最佳BPEDB大小的方法。
Part 2 describes the cleaning options for completed process and task instances to maintain an optimal BPEDB size.
MyTasks——此小部件显示当前登录用户拥有的所有任务实例的列表。
My Tasks - This widget displays a list of all task instances for which the currently logged in user is the task owner.
任务实例生命周期是简单的：创建之后，任务实例可以随意地开始。
The task instance lifecycle is straightforward: After creation, task instances can optionally be started.
业务过程和人工任务实例完成之后，实例可能留在数据库中，也可能自动地删除。
Once business process and human task instances are completed, the instances may be kept in the database or deleted automatically.
根据这个过滤器定义，只显示completed值为False的人工任务实例。
According to this filter specification, only the human task instances that have a Completed value of False will be displayed.
任务实例的一个作用就是支持用户交互——把数据显示给用户并从用户那里收集数据。
A role of task instance is to support user interaction - presenting data to the user and collecting data from a user.
在创建任务实例(作为在任务创建过程中的第一个角色)前，将对其解析以检查授权。
It is resolved to check authorization before task instance creation (as a first role during task creation).
由于会在数据库系统产生很重的负载，同时用多个线程清理过程或任务实例是没有意义的。
Due to the heavy load on the database system, it does not make sense to have several threads cleaning the process or task instances at the same time.
任务实例创建动作处理器(清单15)，它保存流程实例上下文的任务实例id。
Task instance creation action handler (Listing 15), storing an id of a task instance in process instance context.
这里，在得到某个用户的任务实例并将其转变成可分配任务实例之后，我们将试着预留它15。
Here, after getting task instance for a given user and converting it to assignable task instance we are trying to reserve it 15.
owner %解析到声明了任务实例的人员的用户ID，因此成为该任务的所有者。
HTM: task.owner % resolves to the user ID of the person who has claimed the task instance, and is thus its owner.
它们被放在任务实例的客户属性中，在进行补充数据清理时用于引用补充数据行(任务完成时)。
They are placed in the task instance's custom properties to be used to reference the supplemental data row when a cleanup of the supplemental data is done (when the task is completed).
应用推荐