Process Developer

Back Next

Empty

BPMN Implementation: Abstract task, Start/End/None throw event

The empty activity is a "no op" instruction in the business process. This activity is useful for synchronization of concurrent activities. For example, you can use an empty activity to show how links are affected, whether or not a fault is caught, and at what scope level it is caught.

Required Properties	Optional Properties
none	Name. See Selecting Activity Labels
	Join Condition. See Creating a Join Condition for an Incoming Link
	Suppress Join Failure. See Process Properties
	Comment. See Adding Comments to a Process
	Documentation. See Adding Documentation to a Process
	Setting Visual Properties and Using Your Own Library of Images
	Execution State. See Viewing the Execution State of an Activity or Link
	Extension Attributes and Extension Elements. See Declaring Extension Elements and Attributes.

To build an empty activity:

Drag an Abstract task
(or Start/End/None throw event) to the Process Editor canvas.

You can add a background color to the abstract task, but not the throw event.

Add the activity to an appropriate container or link another activity to it.

The following illustration shows an example of using the empty activity, implemented as an abstract task.

XML Syntax

<empty standard-attributes>
     standard-elements
</empty>

BPMN Tasks and Events

Download Guide

Watch

Comments

Cloud Application Integration Homepage

0 COMMENTS

We’d like to hear from you! Log in to comment.

Rename Saved Search

Table of Contents

Process Developer

Process Developer

Empty

Empty