Recognize (connector) result mapping

[nikku]

Is your feature request related to a problem? Please describe.

Within Camunda Connectors there exists a dedicated pattern to map data back into a process through a result mapping:

This is not recognized during variable resolution, and hence not suggested in other places.

Cf. example moderation.bpmn, used along side latest C8 build-in connectors).

Describe the solution you'd like

• Result variable and result expression are accounted for by the variable resolver

Describe alternatives you've considered

The behavior is provided as an extension.

Additional context

The following shows the definition of the two fields result variable and expression. Whereas the zeebe:taskHeader resultVariable defines the value that the response is written to (if provided) the zeebe:taskHeader resultExpression defines the variables that are being created (mapped) from the response:

    {
      "label": "Result Variable",
      "description": "Name of variable to store the response in",
      "group": "output",
      "type": "String",
      "binding": {
        "type": "zeebe:taskHeader",
        "key": "resultVariable"
      }
    },
    {
      "label": "Result Expression",
      "description": "Expression to map the response into process variables",
      "group": "output",
      "type": "Text",
      "feel": "required",
      "binding": {
        "type": "zeebe:taskHeader",
        "key": "resultExpression"
      }
    },

[nikku]

Moved to camunda/camunda-modeler#3511.