Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-8716

Bpmn Model API should support external tasks

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: L3 - Default L3 - Default
    • 7.9.0, 7.9.0-alpha2
    • None
    • engine
    • None

      For spike and testing, I got used to model my test processes via the Bpmn-Model Api.
      Now I am testing external task behavior, but it seems I cannot make a service task external using the fluent builder.

      Feature request: allow ServiceTaskBuilder to accept st like camundaExternalTask("topic") analogue to camundaDelegateExpression. "topic" ideally should also be parsed asexpression if used.

        This is the controller panel for Smart Panels app

            [CAM-8716] Bpmn Model API should support external tasks

            I believe this already exists with #camundaType and #camundaTopic. So you can do it already, although we could add another convenience method to save the call for type.

            Thorben Lindhauer added a comment - I believe this already exists with #camundaType and #camundaTopic . So you can do it already, although we could add another convenience method to save the call for type.

            Could you give an example, how I can use the camundaType/camundaTopic workaround?

            Jan Galinski added a comment - Could you give an example, how I can use the camundaType/camundaTopic workaround?

            Thorben Lindhauer added a comment - Like here: https://github.com/camunda/camunda-bpmn-model/blob/7.8.0/src/test/java/org/camunda/bpm/model/bpmn/builder/ProcessBuilderTest.java#L501-L502 Use "external" for the type argument and the actual topic.

            By the way, the rule of thumb for the fluent builder API is that the method names correspond to the extension attributes in the XML, i.e. camunda:delegateExpression becomes the fluent method #camundaDelegateExpression, etc.

            Thorben Lindhauer added a comment - By the way, the rule of thumb for the fluent builder API is that the method names correspond to the extension attributes in the XML, i.e. camunda:delegateExpression becomes the fluent method #camundaDelegateExpression , etc.

            "topic" ideally should also be parsed asexpression if used.

            Therefore, I created a follow-up feature request CAM-8720

            Roman Smirnov added a comment - "topic" ideally should also be parsed asexpression if used. Therefore, I created a follow-up feature request CAM-8720

            Cool, thanks!

            Jan Galinski added a comment - Cool, thanks!

              svetlana.dorokhova Svetlana Dorokhova
              jan.galinski@holisticon.de Jan Galinski
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: