Camunda Modeler 1.11.0 Released

By
  • Blog
  • >
  • Camunda Modeler 1.11.0 Released
TOPICS

30 Day Free Trial

Bring together legacy systems, RPA bots, microservices and more with Camunda

Sign Up for Camunda Content

Get the latest on Camunda features, events, top trends, and more.

TRENDING CONTENT

We are happy to announce the release of Camunda Modeler version 1.11.0.

Thanks to a contribution by the community it ships with templating support for connectors.

Templating support for connectors

Connector Templating Support

Last year we introduced Element Templates that allow you to create pre-defined configurations for BPMN elements. With the latest version of the Camunda Modeler you can also create element templates for Camunda Connectors.

Let’s look at an example of a template that can be applied to a BPMN 2.0 task element:

{
  "name": "ConnectorGetTask",
  "id": "my.connector.http.get.Task",
  "appliesTo": [
    "bpmn:Task"
  ],
  "properties": [],
  "scopes": {
    "camunda:Connector": {
      "properties": [
        {
          "label": "ConnectorId",
          "type": "String",
          "value": "My Connector HTTP - GET",
          "binding": {
            "type": "property",
            "name": "connectorId"
          }
        },
        ...
      ]
    }
  }
}

Once you apply this template to a task a connector will be created and added to it. The connector’s properties can templated like any other property.

Feel free to check out the documentation of how to use connector templates.

What’s next?

Do you miss anything or spot a bug? Or do you have feedback on this release? Reach out to us via our forums or tweet us @CamundaBPM.

Try All Features of Camunda

Related Content

We're streamlining Camunda product APIs, working towards a single REST API for many components, simplifying the learning curve and making installation easier.
Learn about our approach to migration from Camunda 7 to Camunda 8, and how we can help you achieve it as quickly and effectively as possible.
We've been working hard to reduce the job activation latency in Zeebe. Read on to take a peek under the hood at how we went about it and then verified success.