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

Script Format required

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Won't Do
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • camunda modeler, engine
    • None

      User Story (Required on creation):

      As a user, I can see an error message when trying to deploy a process model with a script task that has no script format defined.

      Functional Requirements (Required before implementation):

      Technical Requirements (Required before implementation):

      Limitations of Scope (Optional):

      Hints (Optional):

      Original description

      Sometimes, during development, when using some script in the model, we forget to define the Script Format. As Camunda Modeler does not criticize this, the process is implanted and we only discover it during the test. I thought it would be useful to create a poka yoke to alert (or even prevent deployment) when the script isn't populated in Modeler.

        This is the controller panel for Smart Panels app

            [CAM-13605] Script Format required

            Tassilo Weidner added a comment -

            Hi rodrigocarlstrom,

            Thank you for your feature request.

            Could you please reformat your ticket description that it follows our feature request template?

            h4. User Story (Required on creation): 
h4. Functional Requirements (Required before implementation): 
h4. Technical Requirements (Required before implementation): 
h4. Limitations of Scope (Optional): 
h4. Hints (Optional):

            Best,
            Tassilo

            Tassilo Weidner added a comment - Hi rodrigocarlstrom , Thank you for your feature request. Could you please reformat your ticket description that it follows our feature request template? h4. User Story (Required on creation): h4. Functional Requirements (Required before implementation): h4. Technical Requirements (Required before implementation): h4. Limitations of Scope (Optional): h4. Hints (Optional): Best, Tassilo

            Tassilo Weidner added a comment -

            Hi rodrigocarlstrom,

            Thanks for making us aware of this.

            While I generally agree that this is something that the engine could reject upon deployment, we will not add this feature request to the backlog. Introducing a stricter validation has already led to a couple of issues for customers in the past with older models that could be deployed on previous versions but failed to do so on newer ones. With regards to behavioral compatibility, this can quickly lead to more issues than it solves. Weighing that in, we will not realize that feature request. I will close the request due to this reasoning.

            This does not mean that the request is not valid, and I would like to emphasize that part. It simply has proven to cause more problems than it solves in the past. This is why we will not follow that request.

            I hope that this is a reasonable explanation.

            If you like, you could raise another feature request in the issue tracker of Camunda Modeler [1] to add validation there.

            Best,
            Tassilo

            [1] https://github.com/camunda/camunda-modeler/issues

            Tassilo Weidner added a comment - Hi rodrigocarlstrom , Thanks for making us aware of this. While I generally agree that this is something that the engine could reject upon deployment, we will not add this feature request to the backlog. Introducing a stricter validation has already led to a couple of issues for customers in the past with older models that could be deployed on previous versions but failed to do so on newer ones. With regards to behavioral compatibility, this can quickly lead to more issues than it solves. Weighing that in, we will not realize that feature request. I will close the request due to this reasoning. This does not mean that the request is not valid, and I would like to emphasize that part. It simply has proven to cause more problems than it solves in the past. This is why we will not follow that request. I hope that this is a reasonable explanation. If you like, you could raise another feature request in the issue tracker of Camunda Modeler [1] to add validation there. Best, Tassilo [1] https://github.com/camunda/camunda-modeler/issues

              tassilo.weidner Tassilo Weidner
              rodrigocarlstrom Rodrigo Carlstrom
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: