R2010: List of Task Icons (BPMN)

Categories	Icon	Name	Uses in Questetra BPM Suite
Task		★Task	Working processes (Tasks) to configure a Business Process (Workflow). Workflow is commonly composed of more than one Task. One “Input form” is defined for each Task. * A Process that has become in charge of a user is specially called “My Tasks”
		Service Task (PDF Generation)	Automatic processing step to configure a Business Process (Workflow). Generate a new PDF file automatically when a Process token incoming. Fills the template (PDF Form) with process data.	Ver 9.0 - (SaaS Edition)
		Service Task (Data Assignment)	Automatic processing step to configure a Business Process (Workflow). Compute a new data value when a Process token incoming.	Ver 9.0 -
		Service Task (Google Drive)	Automatic processing step to configure a Business Process (Workflow). Save File-type data automatically to Google Drive when a Process token incoming.	Ver 9.6 -
		Service Task (Choice Master Update)	Automatic processing steps that compose a Business Process (Workflow) Save choice settings of Select-type data as a shared process model file “Choice Master”	Ver 9.9 -
		Script Task	Automatic processing steps that compose a Business Process (Workflow) Advanced data processing using the ECMA Script	Ver 9.7 - (Beta)
		Receive Task (Webhook)	Automatic processing step to configure a Business Process (Workflow). Stand-by for receiving of a message from outside (HTTP request) Capable of storing Message body as Process data	Ver 11.6 -
Swimlane		★Swimlane	Tasks with the same allocation rules are grouped. Who deals with the internally positioned Tasks is defined. Capable of defining “someone in an organization”
		(Team Swimlane) * Questetra’s original extention	Tasks that multiple users handle simultaneously are grouped. e.g. 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	The Task connected from Start Event is the first Task in the Workflow. A user launches the first Task manually.
		Timer Start Event	A process, which repeatedly starts every day, week, month or year, is automatically launched. e.g. Monthly application and daily report.
		Message Start Event (email)	Starts a Process upon receiving an email from outside of Questetra BPM Suite. Capable of storing the From Address, Mail Subject, Mail Body and so on into the process data.	Ver 9.0 - (SaaS Edition)
		Message Start Event (HTTP)	Starts a Process upon receiving a message (HTTP request) from outside of Questetra BPM Suite. Capable of storing the received HTTP request data into the process data.
		Message Start Event (Webhook)	Starts a Process upon receiving a message (HTTP request) from outside of Questetra BPM Suite. Capable of storing the message body of the received HTTP request into the process data.	Ver 11.6 -
		Message Start Event (Form)	Publish ‘Entry Form’ to external, available to install in the blog or website. Auto-Start a Process by receiving data from Entry Form.	Ver 9.7 - (Beta)
Intermediate Event		Timer Intermediate Event	Retain a Task until specified time after a process token incoming. This icon is placed in the middle of the process model. ※ Specifying in “Date type (year, month, day)” or “Datetime type” Business data (Process data). ※ When specified with “Date type (year, month, day)”, retained until 00:00 of the appropriate day. ※ Not retain if it has past the specified time already when the process arrives. ※ Not retain if the Date/Datetime data is empty (null).
		Timer Intermediate Event (Boundary Type)	Terminate the Task at its Deadline so that the processing proceed forward Configure as an option of Deadline setting in Tasks Property	Ver 10.0 -
		Throwing Message Intermediate Event (email)	Send an Email automatically when process arrives. This icon is positioned in the midle of the way of the process model. Capable of embedding process data in the message.
		Throwing Message 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. Capable of embedding process data in the message.
		Catching Message Intermediate Event (HTTP)	Stands by for receiving external message (HTTP Request) when process arrives. This icon is placed in the middle of the process model. Capable of storing the received data into the process data.
		Intermediate Error Catch Event (Boundary Type)	Terminate the Task if there is no Operator (Candidate) , so that the processing proceed forward Configure as an option of Error handling setting in Tasks Property	Ver 10.0 -
End Event		★End Event	The ending point of a process.
		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.
		Inclusive Gateway (OR)	Moves to all destinations that satisfy the specified condition. May be concurrent processing.
		Parallel Gateway (AND)	Moves to all destinations. Always be concurrent processing.
		Join Gateway	Joins multiple flows to one flow. When a process is separated, first arriving process waits for late process.
Annotation		Text Annotation	Describe “Note or Remarks” on Workflow chart	Ver 10.3 -

※★ 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)

Maximum number of placeable Icons

• Swimlane: 50
• Event, Task, Gateway: (total)150