In this section, you’ll learn how to create your first BPMN 2.0 process with the Camunda Modeler and how to execute automated steps. Start by opening the Camunda Modeler.
Double-click the start event. A text box opens. Name the start event Payment Retrieval Requested.
When editing labels, you can add line breaks using Shift + Enter.
Click the start event. From its context menu, select the activity shape (rounded rectangle). It is placed automatically on the canvas; drag it to your preferred position. Name it Charge Credit Card. Change the activity type to Service Task by clicking the activity shape and using the wrench button.Add an end event named Payment Received.
There are different ways to execute service tasks with ASEE Flow. In this guide, we’ll use the external task pattern. Open the properties panel in the Camunda Modeler and click the service task you just created. Change the Implementation to External and use charge-card as the Topic.
Because we’re modeling an executable process, we should give it an ID and set the isExecutable property to true. On the right-hand side of the canvas you find the properties panel. When you click empty space on the canvas, the panel displays the properties of the process itself.First, configure an ID for the process. Type payment-retrieval in the Id field. The ID is used by the process engine as an identifier for the executable process; it’s best practice to set it to a human-readable name.Second, type Payment Retrieval in the Name field.Finally, make sure the Executable checkbox is checked. If you don’t check this box, the process definition is ignored by the process engine.
When you’re done, save your changes by clicking File > Save File As…. In the dialog, navigate to a folder of your choice and save the diagram as something like payment.bpmn.
After modeling the process, we want to execute some business logic. ASEE Flow lets you implement your business logic in different languages — choose whichever suits your project best. In this quick start, we’ll show you how to use ready-to-go task clients in:
ASEE Flow Run secures the engine REST API by default — the distribution bundles WebAdmin. The workers below connect to /engine-rest without credentials, so against a default Run distribution they receive 401.For this local quick start, open the REST API by setting aseeflow.webadmin.disable-rest-security=true on the Run distribution (or the environment variable ASEEFLOW_WEBADMIN_DISABLE_REST_SECURITY=true). For a secured deployment, authenticate the worker to match your configured authentication mode instead. See WebAdmin security for the trade-offs of disabling REST security.
If you prefer a different programming language, you can also use the REST API to access API operations over HTTP.
Start by creating a new Maven project in your IDE — a simple project (you can skip archetype selection).
Configure the Maven coordinates and, since we’re setting up a JAR project, set Packaging to jar.
You can also create the project directly from the pom.xml shown below.
Next, create an ExternalTaskClient that subscribes to the charge-card topic. When the process engine encounters a service task configured to be externally handled, it creates an external task instance that our handler reacts to. We use long polling in the client to make communication more efficient.Create a package, for example org.camunda.bpm.getstarted.chargecard, and add a Java class such as ChargeCardWorker:
package org.camunda.bpm.getstarted.chargecard;import java.util.logging.Logger;import java.awt.Desktop;import java.net.URI;import org.camunda.bpm.client.ExternalTaskClient;public class ChargeCardWorker { private final static Logger LOGGER = Logger.getLogger(ChargeCardWorker.class.getName()); public static void main(String[] args) { ExternalTaskClient client = ExternalTaskClient.create() .baseUrl("http://localhost:8080/engine-rest") .asyncResponseTimeout(10000) // long polling timeout .build(); // subscribe to an external task topic as specified in the process client.subscribe("charge-card") .lockDuration(1000) // the default lock duration is 20 seconds, but you can override this .handler((externalTask, externalTaskService) -> { // Put your business logic here // Get a process variable String item = externalTask.getVariable("item"); Integer amount = externalTask.getVariable("amount"); LOGGER.info("Charging credit card with an amount of '" + amount + "'€ for the item '" + item + "'..."); // Complete the task externalTaskService.complete(externalTask); }) .open(); }}
Run the Java application by right-clicking the ChargeCardWorker class and choosing Run as Java. Keep the worker running throughout this quick start guide.
Create an ExternalTaskClient that subscribes to the charge-card topic. Create a JavaScript file such as worker.js:
import { Client, logger } from 'camunda-external-task-client-js';// configuration for the Client:// - 'baseUrl': url to the Process Engine// - 'logger': utility to automatically log important events// - 'asyncResponseTimeout': long polling timeout (then a new request will be issued)const config = { baseUrl: 'http://localhost:8080/engine-rest', use: logger, asyncResponseTimeout: 10000 };// create a Client instance with custom configurationconst client = new Client(config);// subscribe to the topic: 'charge-card'client.subscribe('charge-card', async function({ task, taskService }) { // Put your business logic here // Get a process variable const amount = task.variables.get('amount'); const item = task.variables.get('item'); console.log(`Charging credit card with an amount of ${amount}€ for the item '${item}'...`); // Complete the task await taskService.complete(task);});
