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

Generated form field is treated a business key

    • Icon: Bug Report Bug Report
    • Resolution: Won't Fix
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • tasklist
    • None

      Environment (Required on creation):

      Camunda Run 7.17.3, Java 17.0.4, Chrome 104.0.5112.79

      Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):

      When creating a user task form using Generated form fields, it is rendered correctly at first glance. 

      Anyway, when using the browser dev tools, the form has one problem: This one field is the business key!

      The problem came up as the variables was (of course) not submitted.

      Steps to reproduce (Required on creation):

      Create a BPMN process. Add a user task and give it a generated form. Insert only one form field (configured like in screenshot above). Add another task after it (user task, external service task) that allows to read the variables.

      Observed Behavior (Required on creation):

      On generation of the given form, the one field should be rendered as number form field without the cam-business-key parameter on the input. 

      Expected behavior (Required on creation):

      Instead, it should have the cam-variable-name and cam-variable type on it.

      Root Cause (Required on prioritization):

      Bug in rendering of generated task forms.

      Solution Ideas (Optional):

       

      Hints (optional):

        This is the controller panel for Smart Panels app

            [CAM-14816] Generated form field is treated a business key

            Hi jonathan.lukas,
            Thanks for reaching out to us. I was able to reproduce the issue you describe. However, I think the root cause is in the Camunda Modeler.
            I re-created the BPMN model as you described it and noticed that the modeler generates an attribute on the camunda:formData element called businessKey="number". This causes the BPMN parser to flag the property as business key. Later the HTML engine creates the businessKey attribute based on this flag.

            I would like to ask you to raise this concern with the modeler team in their issue tracker. Feel free to link this CAM ticket and ping me in the ping me in the Modeler issue if input from the C7 team is needed.

            Best,
            Miklas

            Miklas Boskamp added a comment - Hi jonathan.lukas , Thanks for reaching out to us. I was able to reproduce the issue you describe. However, I think the root cause is in the Camunda Modeler. I re-created the BPMN model as you described it and noticed that the modeler generates an attribute on the camunda:formData element called businessKey="number" . This causes the BPMN parser to flag the property as business key . Later the HTML engine creates the businessKey attribute based on this flag. I would like to ask you to raise this concern with the modeler team in their issue tracker . Feel free to link this CAM ticket and ping me in the ping me in the Modeler issue if input from the C7 team is needed. Best, Miklas

            Hello miklas.boskamp ,

            thank you for investigating and sorry I did not do my homework on this.

            I created a Github issue as you said and linked this ticket there.

            Vice Versa: https://github.com/camunda/camunda-modeler/issues/3102

            Best,

            Jonathan

            Jonathan Lukas added a comment - Hello miklas.boskamp , thank you for investigating and sorry I did not do my homework on this. I created a Github issue as you said and linked this ticket there. Vice Versa: https://github.com/camunda/camunda-modeler/issues/3102 Best, Jonathan

            Miklas Boskamp added a comment - - edited

            jonathan.lukas, no worries. Thanks for creating the Modeler issue. Let's see what the team can find out. I will close this ticket for now. We can reopen it if there is any work necessary in the engine.

            Miklas Boskamp added a comment - - edited jonathan.lukas , no worries. Thanks for creating the Modeler issue. Let's see what the team can find out. I will close this ticket for now. We can reopen it if there is any work necessary in the engine.

              miklas.boskamp Miklas Boskamp
              jonathan.lukas Jonathan Lukas
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: