---
title: "List of Supported Elements — SpiffWorkflow 3.0.0 documentation"
description: "Spiff’s implementation of Service Tasks is abstract, so while they will be parsed, the library provides no built-in mechanism for executing them."
source_url: https://spiff.works/docs/spiffworkflow/bpmn/supported.html
---

☰ Menu

# List of Supported Elements[](#list-of-supported-elements "Link to this heading")

## Tasks[](#tasks "Link to this heading")

- User Task
- Manual Task
- Business Rule Task
- Script Task
- Service Task

Note

Spiff’s implementation of Service Tasks is abstract, so while they will be parsed, the
library provides no built-in mechanism for executing them.

## Gateways[](#gateways "Link to this heading")

- Parallel Gateway
- Exclusive Gateway
- Inclusive Gateway
- Event-Based Gateway

## Subrocesses and Call Activities[](#subrocesses-and-call-activities "Link to this heading")

- Subprocess
- Call Activity
- Transaction Subprocess
- Event Subprocess

## Events[](#events "Link to this heading")

- Cancel Event
- Escalation Event
- Error Event
- Message Event
- Signal Event
- Terminate Event
- Timer Event

## Data[](#data "Link to this heading")

- Data Object
- Data Store

Note

Spiff’s Data Store implementation is abstract; Spiff can parse a Data Store, but does not
provide any built-in mechanism for reading and writing to it.

## Loops[](#loops "Link to this heading")

- Loop Task
- Parallel MultiInstance Task
- Sequential MultiInstance Task

Note

Parallel MultiInstance tasks are *not* executed by SpiffWorkflow in parallel. SpiffWorkflow
merely indicates that parallel tasks become ready at the same time and that the workflow
engine may execute them in parallel.