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

Tasklist uses process variables instead of task variables

    XMLWordPrintable

Details

    • Bug Report
    • Resolution: Cannot Reproduce
    • L3 - Default
    • None
    • None
    • tasklist
    • None

    Description

      The current tasklist implementation uses the processInstance.getVariables() to fill forms. This is not consistent with engine API - we should use task.getVariables() which delegates to processInstance automatically.

      See tasks.js:

      EngineApi.getProcessInstance().variables(

      { id : task.processInstanceId }

      ).$then(function (result) {

      uses

      this.processInstance = $resource(Uri.appUri("engine://engine/:engine/process-instance/:id/:operation"),

      { id: "@id" }

      , {
      variables : { method: 'GET', params : { operation: "variables" }}
      });

      Get Task Variables is currently missing the REST API.

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            depends on

            Feature Request - A new feature of the product, which has yet to be developed. CAM-640 Using the REST Api, I can GET, modify and DELETE variables of a Task

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed
            is duplicated by

            Bug Report - A problem which impairs or prevents the functions of the product. CAM-1565 Tasklist incorrectly uses process variables when displaying task form

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed
            mentioned in

            Page Loading...

            Page Loading...

            Activity

              People

                meyer Daniel Meyer
                ruecker Bernd Ruecker
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce