List of icons available in the work flow definition. There are 13 types in 3 systems of Icons to define business flow (BPMN elements) such as Events, Tasks, Gateways. Drag & Drop these icons into each swimlane, connect them with arrow-lines.
Available BPMN Icons
Like other BPMS, all BPMN 2.0 objects are not available in Questetra BPM Suite. You can define workflows with core icons in BPMN (subset of BPMN).
Icon
categories | Icon | BPMN name | Uses in Questetra BPM Suite |
|---|
| Task |  | ★Task | - Working processes (Tasks) to configure a business process (Workflow).
- Workflow is composed of more than one Task.
- One "Input form" is defined for each Task.
- Each process (operation) flows through business process and arrives at one or more "Tasks".
- （A Process that has become in charge of a user is specially called "My Tasks / Offered Tasks".）
|
| Swimlane |  | ★Swimlane | - Tasks with the same allocation rules are grouped.
- Who deals with the internally positioned Tasks is defined.
- It is also possible to define "someone in an organization".
|
| Swimlane |  | Team Swimlane
※Questetra's unique extention | - Tasks that multiple users handle simultaneously are grouped.
- For example, the feedback task “to advise” and the incompletely defined task “for initial setting”.
- Also available to tasks which is difficult to define procedures (ad-hoc tasks, etc.)
|
| Start Event |  | ★Start Event | - The Task connected from Start Event is the first Task in the Workflow.
- A user launches the first Task manually.
|
| Start Event |  | Timer Start Event | - A process, which repeatedly starts every day, week, month or year, is automatically launched.
- For example, monthly application and daily report.
|
| Start Event |  | Message Start Event | - Starts a Process upon receiving a message (HTTP request) from outside of Questetra BPM Suite.
- It is possible to store the received HTTP request data into the process data.
|
| Intermediate Event |  | Message Throwing Intermediate Event (Email) | - Send an email automatically when process arrives.
- This icon is positioned in the midle of the way of the process model.
- Can embed process data in the message.
|
| Intermediate Event |  | Message Throwing Intermediate Event (HTTP) | - Send a HTTP Request automatically when process arrives.
- This icon is positioned in the midle of the way of the process model.
- Can embed process data in the message.
|
| Intermediate Event |  | Message Catching Intermediate Event | - Stands by for receiving external message (HTTP Request) when process arrives.
- This icon is positioned in the midle of the way of the process model.
- Can store the received data into the process data.
|
| End Event |  | ★End Event | - The ending point of a process.
|
| End Event |  | Terminate End Event | - Terminates all other ongoing processes when either of separated processes arrives.
- The process ends even if there are unfinished Tasks left.
|
| Gateway |  | Exclusive Gateway
(XOR) | - Moves to only one destination that satisfies the specified condition first.
- Never be concurrent processing.
|
| Gateway |  | Inclusive Gateway
(OR) | - Moves to all destinations that satisfy the specified condition.
- May be concurrent processing.
|
| Gateway |  | Parallel Gateway
(AND) | - Moves to all destinations.
- Always be concurrent processing.
|
| Gateway |  | Join Gateway | - Joins multiple flows to one flow.
- When a process is separated, first arriving process waits for late process.
|
※ ★ mark represents the icon frequently used. In Questetra BPM Suite, those icons are classified into “Basic” icons.
※BPMN: Business Process Model and Notation (BPMN 1.x: Business Process Modeling Notation)
Sample
