WPS: when do you choose long running or micro flows?

    Long-running processes involve services that do not respond immediately, run over a period of time and can involve people.

WPS: Difference between Inline and stand-alone human tasks?

Difference between Inline and stand-alone human tasks:

You can implement a human task as part of the logic of a business process, or independently of other processes.

If the task is implemented within a business process, it is called an inline task. Otherwise, it is referred to as a stand-alone task.

Inline task:

An inline 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 run human interaction. Although information from the process can also be modeled into the input for a human task, the main reason to use an inline human tasks is because they have direct access to the process context without the need to explicitly model the required information into the input message.

You want to define authorization rights on specific activities

The standard method of creating an inline task is to drop a human task activity on to the canvas in the business process editor.

Stand-alone task:

A stand-alone task exists independently of a business process, and implements human interaction as a service that can be wired to any other component 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:

• The task provides just another service
• You intend to replace the stand-alone task later on and don't want to change the component to which it is wired.
• Create a stand-alone task using the New human task wizard and then wiring the task to a business process using the assembly editor.
  Changing a stand-alone task to an inline task :
• If you would like to take an existing stand-alone task that is invoked by an invoke activity in a business process, and transform it into an inline task that is implemented by a human task activity, proceed as follows:
• In the assembly editor, delete the existing interface between the human task component and the business process.
• Delete the component as well.
• In the business process component, right-click the invoke activity that originally connected to the human task component, and select Change type > Human task.
• In the Details tab of the human task, select New.
• Select the interface that was used between the original business process component and the human task component.
• Define the settings for the human task. From the main menu, click Project > Clean.