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

Use id as default name of elements created with the Model API

    Details

      Description

      I currently try to to minimize code required to write good BPMN processes using the model API. One flaw is nugging me - if you do not provide "names" for elements, you end up with blank boxes in the graphical BPMN model:

      ```
      flow.startEvent()
      .serviceTask("retrievePayment").camundaClass(RetrievePaymentAdapter.class) //
      .receiveTask("waitForPayment").message("PaymentReceived") //
      ```

      I have to hand in a name additionally to see something on the graphical model:
      ```
      flow.startEvent()
      .serviceTask("retrievePayment").name("Retrieve payment").camundaClass(RetrievePaymentAdapter.class) //
      .receiveTask("waitForPayment").name("Wait for payment").message("PaymentReceived") //
      ```

      This is unnecessary verbose. If I want to have names that are different from ids it is OK, but we should offer the shortcut, that the id is also used as name whenever no name is given. I do not see use cases for an empty name anyway.

        Activity

        ruecker Bernd Rücker created issue -
        ruecker Bernd Rücker made changes -
        Field Original Value New Value
        Attachment screenshot-1.png [ 24478 ]
        ruecker Bernd Rücker made changes -
        Description I currently try to to minimize code required to write good BPMN processes using the model API. One flaw is nugging me - if you do not provide "names" for elements, you end up with blank boxes in the graphical BPMN model:

        ```
            flow.startEvent()
                  .serviceTask("retrievePayment").camundaClass(RetrievePaymentAdapter.class) //
                  .receiveTask("waitForPayment").message("PaymentReceived") //
        ```
        I have to hand in a name additionally to see something on the graphical model:
        ```
            flow.startEvent()
                  .serviceTask("retrievePayment").name("Retrieve payment").camundaClass(RetrievePaymentAdapter.class) //
                  .receiveTask("waitForPayment").name("Wait for payment").message("PaymentReceived") //
        ```

        This is unnecessary verbose. If I want to have names that are different from ids it is OK, but we should offer the shortcut, that the id is also used as name whenever no name is given. I do not see use cases for an empty name anyway.
        I currently try to to minimize code required to write good BPMN processes using the model API. One flaw is nugging me - if you do not provide "names" for elements, you end up with blank boxes in the graphical BPMN model:

        ```
            flow.startEvent()
                  .serviceTask("retrievePayment").camundaClass(RetrievePaymentAdapter.class) //
                  .receiveTask("waitForPayment").message("PaymentReceived") //
        ```

        !screenshot-1.png!

        I have to hand in a name additionally to see something on the graphical model:
        ```
            flow.startEvent()
                  .serviceTask("retrievePayment").name("Retrieve payment").camundaClass(RetrievePaymentAdapter.class) //
                  .receiveTask("waitForPayment").name("Wait for payment").message("PaymentReceived") //
        ```

        This is unnecessary verbose. If I want to have names that are different from ids it is OK, but we should offer the shortcut, that the id is also used as name whenever no name is given. I do not see use cases for an empty name anyway.
        thorben.lindhauer Thorben Lindhauer made changes -
        Labels EasyPick
        meyer Daniel Meyer made changes -
        Link This issue is related to SUPPORT-3599 [ SUPPORT-3599 ]
        meyer Daniel Meyer made changes -
        Fix Version/s 7.8.0 [ 14894 ]
        thorben.lindhauer Thorben Lindhauer made changes -
        Labels EasyPick EasyPick SUPPORT
        thorben.lindhauer Thorben Lindhauer made changes -
        Link This issue is depended on by SUPPORT-3599 [ SUPPORT-3599 ]
        thorben.lindhauer Thorben Lindhauer made changes -
        Link This issue is related to SUPPORT-3599 [ SUPPORT-3599 ]
        svetlana.dorokhova Svetlana Dorokhova made changes -
        Assignee Anna Pazola [ anna.pazola ]
        anna.pazola Anna Pazola made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        anna.pazola Anna Pazola made changes -
        Status In Progress [ 3 ] Resolved [ 5 ]
        Original Estimate 0 minutes [ 0 ]
        Remaining Estimate 0 minutes [ 0 ]
        Assignee Anna Pazola [ anna.pazola ] Smirnov Roman [ roman.smirnov ]
        Resolution Fixed [ 1 ]
        roman.smirnov Smirnov Roman made changes -
        Assignee Smirnov Roman [ roman.smirnov ] Tassilo Weidner [ tassilo.weidner ]
        tassilo.weidner Tassilo Weidner made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Assignee Tassilo Weidner [ tassilo.weidner ]
        yana.vasileva Yana Vasileva made changes -
        Fix Version/s 7.8.0-alpha6 [ 15101 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            ruecker Bernd Rücker
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development