Same Results, Different Starts

In some cases employees start requesting, in other accountancy start confirming. Yes, business processes in the world are not started from the same occasion. Rather multiple starting occasion (we call "Trigger") should be prepared in most of business processes.

Theme of seventh installment in the BPMN lecture series is "Multiple Triggers."

-BPMN lecture series Before-

• Split Conditions are a Basic Concept in BPMN
• BPMN Splits for flexible flow conditions
• Automatically Sending Template Emails in the Middle of a Workflow
• How to Design Primary Workflows With Many Baby Workflows
• Eternal Looping 
• Never Use Your Own Rules When Designing Workflow Diagrams (interrupting flows that include concurrent processing)

<Tasks>
1a. Task, 1b. Task, 1c. Task, 2. Task

[BPMN Sample <Multiple Start>:"1a. Task" screen]

<Items>

• Title

-Process Data-

• Data Input (string: text box 3 lines)
• Correspondence (discussion)

In Workflow above, someone in Accountancy or Development or Sales has processed [1x. Task], it goes to [2. Task] of Accountancy.
Truly Multiple Trigger is settled. But it seems strange to you as there is "join sign" (we call it Join Gate) without "Split."

There also are some cases not started by human.
Automatically a duty be allocated to someone in certain time.
Data transfer from external device (like sensors) make duty.

In Workflow below, for example, Accountancy proceeds [1a. Task] every Monday morning. (There's a possibility of proceeding at other timing by his own judgment.)
And [2. Task] will be directly allocate by Message Start Event in some case.

By the way, when the first task is input work by human, data transfer from external device may be supposed for simplification and labor saving. If you can trust your external devices, the first task by human could be omitted in Workflow.


<Tasks>
1a. Task, 1b. Task, 1c. Task, 2. Task

• BPMN Sample <Multiple Start>
• BPMN Sample <Varied Multiple Start>