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

For a Human Task, I can map variables via camunda:inputOutput

XMLWordPrintable

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

      In User Tasks (BPMN) you can set input/output parameters. This can even be used by the modeler extension-elements.

      It would be logical that the same functionality is available for Human Tasks (CMMN).

      e.g. for a BPMN User Task, we use these input/output variables (defined in the modeler by an element-templates.json file for easy access to non-technical business users) to decide if we need to run some logic that is registered as a ProcessEngine Plugin TaskListener, or to customize the label on the submit button.

      <bpmn:userTask id="task_valideer_automatisch_advies" name="Valideer Automatisch Advies" camunda:modelerTemplate="com.skryv.SkryvDocUserTask">
      <bpmn:extensionElements>
        <camunda:inputOutput>
          <camunda:inputParameter name="submitText" />
          <camunda:inputParameter name="runCustomProcessEngineTaskListener">true</camunda:inputParameter>
        </camunda:inputOutput>
      </bpmn:extensionElements>
    </bpmn:userTask>

        This is the controller panel for Smart Panels app

            [CAM-8130] For a Human Task, I can map variables via camunda:inputOutput

            Dimitry Declercq created issue -
            Dimitry Declercq made changes -
            Link New: This issue is depended on by CAM-8131 [ CAM-8131 ]

            Matthijs added a comment -

            Hi Dimitry,
            Thanks for contacting us with this and our apologies for the delayed response

            A short question: was this issue meant to be raised in our support project?
            The difference between the Support project and the Camunda BPM project is that when raising issues in the Camunda BPM project, they are not subject to the agreed SLAs and they can be viewed by all users. In contrast, issues raised in the Support project can only be seen by your authorized support contacts and us. You can find more information in our documentation.
            If you intended to raise a support issue, please let us know and we'll raise a respective issue in the support project.

            Thank you and best regards,
            Mat

            Matthijs added a comment - Hi Dimitry, Thanks for contacting us with this and our apologies for the delayed response A short question: was this issue meant to be raised in our support project? The difference between the Support project and the Camunda BPM project is that when raising issues in the Camunda BPM project, they are not subject to the agreed SLAs and they can be viewed by all users. In contrast, issues raised in the Support project can only be seen by your authorized support contacts and us. You can find more information in our documentation . If you intended to raise a support issue, please let us know and we'll raise a respective issue in the support project. Thank you and best regards, Mat
            Thorben Lindhauer made changes -
            Workflow Original: camunda BPM [ 43786 ] New: Backup_camunda BPM [ 56299 ]

            Thorben Lindhauer added a comment -

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

            • We are not developing new features for CMMN

            Thorben Lindhauer added a comment - We are closing this ticket as part of our backlog grooming. Reasons: We are not developing new features for CMMN
            Thorben Lindhauer made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]

              Unassigned Unassigned
              dimitry.declercq@skryv.com Dimitry Declercq
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: