BPMN Node Reference

Basic Buttons or Symbols Description Properties Incoming Edge Count Outgoing Edge Count
Pool - The container for the workflow process. - Name
- Folder Type
- Organization		 0 0
Swim Lane - Contains nodes assigned to a specific group/user in the workflow. - Assignee
- Auto Assign to User		 0 0
Sequence Edge - Connects nodes in a workflow process - Name
- Sort Order
- Task Note Required
- Assign Next User		 0 0
Start Event - The default starting point of a workflow. Each workflow must have one and only one of these. - Name 0 1
Signal Start Event - Used for Re-Activate events. A workflow can have any number of these. - Name
- Re-Activate to last completed task		 0 1
End Event - The end of a workflow process. All paths must end with one of these. A workflow must have at least one of these.   1 0
User Task - A task in the workflow that requires manual input from the user to complete. - Name
- Days to Complete
- Day Type
- Days to Complete Field Path
- Holdable
- Hold Instructions
- Terminatable
- Cancellable
- Instructions
- Document Signature
- Launch Initiating Document
- Show Icon if Folder Has Documents
- Complete through API Services
- Open Task Default Behavior (View/Work Task)
- View Instructions
- Alert When Complete
- User Interface Key
- Work Task Default Action
- Custom Properties		 1+ 1
Script Task - A task in the workflow that is completed automatically by the system. These tasks execute some script code to perform system operations. - Name
- Seconds to Complete
- Script
- Script Language
- Alert When Complete		 1+ 1
Call Activity - Inserts another BPMN workflow process in place into the current process. - Name
- External Process		 1+ 1
Exclusive Gateway - Marks a decision point in the workflow. These can be data or user driven. - Name 1 2+
Parallel Gateway - Marks the beginning of a parallel sequence in the workflow. These can be data or user driven. Must always be used as a set, a parallel sequence must have an end. - Name 1 2+
Event Based Gateway - Represents a hold task in the system. Can have multiple incoming sequence edges and must have outgoing sequence edges followed by an intermediate catch event. Must include at least one conditional take off hold catch event and a timer catch event. - Name
- Allow Dynamic Hold Time
- Dynamic Hold Time Required
- Hold Instructions
- Hold Reason Type
- Hold Reason List		 1 2+

Catch Events

Catch Events are types of events that connect to Event Gateways. Catch Events must be set up to receive information from the Event Gateway and deliver the correct next task to the defined user or group.

Catch Events must be uniquely named within the system. Catch Events must have a matching QEvent record of type “ProcessIntermediate”??

Catch Events Description      
Message Intermediate Throw Event - Sends a configured email message. - Name
- Sender
- Recipients
- CCs
- Subject
- Message		 1+ 1
Conditional Intermediate Catch Event - Used in conjunction with an event based gateway. Executes when some condition in the workflow is met. - Name
- Take Off Hold Event
- Document Event		 1 1
Timer Intermediate Catch Event - Used in conjunction with an event based gateway. Executes when a certain number of days has elapsed since the hold start date. - Name
- Days to Hold
- Day Type		 1 1
Signal Intermediate Catch Event - Used in conjunction with an event based gateway. Executes in response to a signal intermediate throw event or external event with the same name. - Name 1 1
Signal Intermediate Throw Event - Fires a corresponding signal intermediate catch event with the same name. - Name 1+ 1