ActiveVOS Designer BPEL for People User’s Guide
The following illustration shows what happens when a BPEL process executes a People activity.
When a BPEL process executes a People activity, the task defined by the activity is routed to the Inboxes of all potential owners and administrators defined by the task. Each user signs into his or her Inbox, and can claim a task to work on, making it unavailable for other users.
When the task owner completes the task, by submitting the required information into a form, the output data is sent back to the process so that the next activity can execute.
Typically a BPEL process containing a People activity is an asynchronous, long-running process. Since the People activity effectively "invokes" a person, the expected response time is high. For this reason, when you design a BPEL process containing a People activity, it is advisable to make the process asynchronous, in order to avoid probable Web service communication timeouts.
Copyright (c) 2004-2009 Active Endpoints, Inc.