IBM BPM, V8.0.1, All platforms > Get started with IBM BPM > Key concepts > BPEL processes and human tasks > Human tasks overview > Stand-alone and inline tasks

Stand-alone tasks

Stand-alone tasks follow the service-oriented architecture (SOA) pattern and they are loosely coupled with the components that invoke them (to-do tasks), or the components that are invoked by them (invocation tasks). They can be wired to another component using the Service Component Architecture infrastructure.

Stand-alone tasks have an autonomy setting of either peer or child. Stand-alone tasks with peer autonomy communicate with their partner components exclusively by SCA means. That is, to-do tasks receive input messages and return output or fault messages, and invocation tasks send input messages and receive output or fault messages. No further information exchange or lifecycle control happens.

Because stand-alone tasks are modeled separately, they can be reused. Stand-alone tasks always emit their Common Event Infrastructure (CEI) and audit log events as human task events.

Stand-alone tasks are made available as SCA components in the following ways:

Stand-alone and inline tasks