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

TaskSync based in Expression Language

XMLWordPrintable

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

      User Story (Required on creation):

      I can enable or disable the "Async Before/After" flag dynamically via expression.

      Functional Requirements (Required before implementation):

      In the BPMN XML, it is possible to define the following properties on flow nodes:

      • camunda:asyncBeforeExpression="${asyncBefore}"
      • camunda:asyncAfterExpression="${asyncAfter}"

      Technical Requirements (Required before implementation):

      • The feature is exposed in the Model API
      • The BPMN parser can handle the new properties
      • Documentation exists BPMN 2.0 reference

      Limitations of Scope (Optional):

      Hints (Optional):

      Original description

      I worked on a recent project in Brazil where we had to create your versions of the same process:
      my-process-sync
      my-process-async
      The only difference between them that one had synchronous tasks and the other asynchronous tasks, due to an omnichannel need of the customer's business.
      You think it would be useful if we could, instead of selecting the "Asynchronous Before" and "Asynchronous After" checkboxes, set an Expression Language so we could set this property dynamically based on variables.

        This is the controller panel for Smart Panels app

            [CAM-13606] TaskSync based in Expression Language

            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,

            I qualified your ticket according to our feature request template, and I generally see this in the scope of the product.

            Since our engineering team is limited regarding resources, I would like to ask you to contribute this feature to our codebase.
            You can raise a pull request on GitHub and receive feedback from the engineering team. If everything looks good, we will merge the pull request with our codebase.

            What do you think about this?

            Best,
            Tassilo

            Tassilo Weidner added a comment - Hi rodrigocarlstrom , I qualified your ticket according to our feature request template, and I generally see this in the scope of the product. Since our engineering team is limited regarding resources, I would like to ask you to contribute this feature to our codebase. You can raise a pull request on GitHub and receive feedback from the engineering team. If everything looks good, we will merge the pull request with our codebase. What do you think about this? Best, Tassilo

            Tobias Metzke-Bernstein added a comment -

            Hi rodrigocarlstrom,

            thanks for opening this request. I agree with Tassilo here that this makes sense as a product feature.
            However, we will not implement this in the near future as we consider this to impact a rather small user base.
            We will keep the ticket open and move it to our backlog.

            If you disagree with our reasoning, let us know.
            Also, if you would like to contribute this feature yourself, we are happy to take a pull request as Tassilo mentioned.
            If you need any assistance on that, we are happy to help.

            Best,
            Tobias

            Tobias Metzke-Bernstein added a comment - Hi rodrigocarlstrom , thanks for opening this request. I agree with Tassilo here that this makes sense as a product feature. However, we will not implement this in the near future as we consider this to impact a rather small user base. We will keep the ticket open and move it to our backlog. If you disagree with our reasoning, let us know. Also, if you would like to contribute this feature yourself, we are happy to take a pull request as Tassilo mentioned. If you need any assistance on that, we are happy to help. Best, Tobias

            Thorben Lindhauer added a comment -

            We are closing this ticket as part of our backlog grooming. Reasons:

            • We did not receive sufficient evidence that this ticket is important

            Thorben Lindhauer added a comment - We are closing this ticket as part of our backlog grooming. Reasons: We did not receive sufficient evidence that this ticket is important

              Unassigned Unassigned
              rodrigocarlstrom Rodrigo Carlstrom
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: