Features by Examples

Service Task

In Process definition (.bpmn file), use implementation attribute to define name of JavaScript/TypeScript Method to perform the Task:

![Using Modeler](./images/bb-service.PNG)

<servicetask id="serviceTask" name="Service Task" implementation="service1">


class AppServices {

async service1(item,input) {
await delay(3000 -(seq * 100) , 'test');
item.log("SERVICE 1" + item.token.currentNode.id);


Script Task

![Using Modeler](images/bb-script.PNG)

<scripttask id="Activity_06typtl" name="script" scriptformat="JavaScript">

this.log('testing from <testing> the inside: '+data.loopKey);

Conditional Flow

![Using Modeler](images/bb-conditional-flow.PNG)



<conditionexpression xsi:type="bpmn:tFormalExpression" language="JavaScript">


Form Input Fields

![Using Modeler](images/bb-form.PNG)

<usertask id="task_Buy" name="Buy">
<formfield id="needsRepairs" label="Repairs Required?" type="boolean"></formfield>
<formfield id="needsCleaning" label="Cleaning Required?" type="boolean"></formfield>



Multiple Start Event

![Image description](examples/invoice-start.png)

When a definition/process has multiple start node, you need to specify the start node when starting the process:

From the Web UI:

![Image description](examples/invoice-start-prompt.png)

From API:

response = await api.engine.start('invoice',
{ reminderCounter: 0, caseId: caseId}, user, {startNodeId:'StartEvent_AP'});

Business Rule Task

BPMN-Server supports Business Rules implemented through DMN-Engine
Business Rules can be defined as a Decision Table as in this example:

Vacation Decision Table

Decision Table is called through

    <bpmn2:businessRuleTask id="Task_1lcamp6" name="Vacation"  camunda:decisionRef="Vacation">

This will load the file ‘Vacation.json’ form the Processes folder as defined in configuration.js

Script Extensions

Scripts can be added to listen to two events:

  • Start before the Task is executed
  • End after the task is executed

![Using Modeler](images/bb-event-scripts.PNG)

In this example we are adding a script to bpmn:startEvent

<executionlistener event="start">
<script scriptformat="JavaScript">

console.log("This is the start event");

<executionlistener event="end">
<script scriptformat="JavaScript">

console.log("This is the end event");



Timer Event

![Using Modeler](images/bb-timer.PNG)

<intermediatecatchevent id="Event_timer">
<timereventdefinition id="TimerEventDefinition_07xu06a">
<timeduration xsi:type="bpmn:tExpression">PT2S</timeduration>
More on [timers](timers.md)

Multi-instances Tasks

![Using Modeler](images/bb-multi-instance.PNG)

<scripttask id="scriptTask" name="Script Task">
<multiinstanceloopcharacteristics issequential="true" camunda:collection="$(data.records)"></multiinstanceloopcharacteristics>
<script><![CDATA[this.log('testing from the inside: '+data.loopKey);]]></script>
For Multi-instance data handling [see](data.md)

Call Process

![Using Modeler](images/bb-call.PNG)

<callactivity id="activity_call" name="Call Task" calledelement="loop">


In the above example ‘loop’ is the name of process to be called.

Throwing and Cathcing Messages

In this example, we will demonstrate how can two seperate processes communicate through “Messages”

Using Modeler

1 Throw a message with data

When a process throw a message, bpmn-server checks if there is another process that can catch this message before dispatching it to AppDelegate.

    <bpmn2:intermediateThrowEvent id="throw_msg1" name="msg1">
      <bpmn2:messageEventDefinition id="messageEventDef1" messageRef="Msg1" />
        <camunda:script event="start"><![CDATA[
        input.caseId= data.caseId;
        this.messageMatchingKey={'data.caseId': data.caseId };

The above will through a messsage as follows:

  • Message Id: Msg1
  • Message Output: caseId: <someValue>

2 Catch a message with data

The second process defines a start event to catch the message Msg1

    <bpmn2:startEvent id="StartEvent_1w66wpl" name="msg1">
      <bpmn2:messageEventDefinition id="messageEventDef4" messageRef="Msg1" />

Therefore, the system will create a new instance of the second process and assign the Message output data, namely, the caseId

3 Throw a message with data and a Key

In addition, the second process sends a confirmation message Confirm1 to the first process

    <bpmn2:intermediateThrowEvent id="throw_confirm1" name="confirm1">
      <bpmn2:messageEventDefinition id="messageEventDef2" messageRef="Confirm1" />
        <camunda:script event="transformOutput"><![CDATA[

        this.context.messageMatchingKey={'data.caseId': this.token.data.caseId };


Howerver, the challenge here is that make sure the message is sent to the specific instance, that is where the Matching key is used

  • Message Id: Confirm1
  • Message Output: confirm: true
  • Message Matching Keyt: ‘data.caseId’: this.token.data.caseId
Image description

Input and Output Data Handling

this for details


Event Based Gateway

Boundary Events

UserTask Assignment