Dynamic binding to zeebe:taskDefinition:type

[jonas.ekstrom]

Using SaaS and a Camunda 8.6.0-alpha4 cluster.

Previously we have successfully used a Connector Template with a drop-down control to dynamically set different job types like this:

{
      "id": "method",
      "label": "Fund Account methods",
      "group": "service",
      "description": "Specify the Fund Account method to use.",
      "type": "Dropdown",
      "value": "get",
      "choices": [
        {
          "name": "Create Fund Account",
          "value": "create-fund-account"
        },
        {
          "name": "Activate Fund Account",
          "value": "activate-fund-account"
        }
      ],
      "binding": {
        "type": "zeebe:taskDefinition:type"
      }
    }

Since then, it has stopped working since no job type is binded to the task in runtime, and in the Connector Template editor, the “binding” value is highlighted as deprecated (“Value is deprecated”).

We have tried it in 8.6 self managed and it’s working there, but not in SaaS.

Could you clarify when this deprecation occurred, what the recommended approach for dynamic binding is now, and where we can find the relevant documentation for this change?

Screen dump:

[ev.bilske]

Hi @jonas.ekstrom , that sounds frustrating. Let’s see if I can help

It appears the deprecation occurred in 2023.

The recommended approach would be to replace the “binding” property with this:

"binding": {
    "type": "zeebe:taskDefinition",
    "property": "type"
  }

Could you please try that and let me know if it works? Thanks

[jonas.ekstrom]

Thanks a lot it works.