We can implement human task two ways.

1. In-Line Human Task: Aninline task is defined within an implementation of a business process. It can either be implemented directly in the process using a human task activity, or as a property of an invoke, PICK, receive, event handler, or on message activity. When you are first planning your human task, you should MODEL it as an inline task if any of the following conditions are present:

• You need information from the process logic to EXECUTE human interaction
• You want to execute administrative tasks
• You want to define authorization rights on specific activities

2. Stand-alone Human Task: A stand-alone task exists independently of a business process, and implements human interaction as a service that can be used in many of the different components of the WebSphere Integration Developer family of TOOLS. When you are first planning your human task, you should model it as a stand-alone task if any of the following conditions are present:

• You do not need any information from the business process
• The task provides just another service

We can implement human task two ways.

1. In-Line Human Task: Aninline task is defined within an implementation of a business process. It can either be implemented directly in the process using a human task activity, or as a property of an invoke, pick, receive, event handler, or on message activity. When you are first planning your human task, you should model it as an inline task if any of the following conditions are present:

2. Stand-alone Human Task: A stand-alone task exists independently of a business process, and implements human interaction as a service that can be used in many of the different components of the WebSphere Integration Developer family of tools. When you are first planning your human task, you should model it as a stand-alone task if any of the following conditions are present: