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

Allow Tasklist variables to be saved to engine variables before completion



    • Feature Request
    • Resolution: Won't Fix
    • L3 - Default
    • None
    • 7.16.0-alpha2
    • tasklist


      User Story (Required on creation):

      As a Tasklist user, I want the ability to store my modified state of the Tasklist form to local variables (not only to browser local storage). If another users views the form, they are able to view the current state and variables in the form.

      Functional Requirements (Required before implementation):

      • I can configure the behavior of the Save¬†button in Tasklist to either save to local storage (default) or to local task variables
      • The form data is correctly loaded based on that configuration

      Technical Requirements (Required before implementation):

      • Users can configure the behavior of the Save button in Tasklist form via Tasklist configuration
      • Default behavior remains as-is, saving to the browser's local storage
      • The execution of the Save button respects that configuration
      • Procedure to load data into the form can handle configuration changes (from local storage to local variables and back)

      Limitations of Scope (Optional):

      Hints (Optional):

      Currently the Save button in Tasklist forms provides the ability to save the state of the form to local storage. This is only useful when only one person needs access to the task but not ideal for task collaboration spanning multiple users.

      The requirement is to have another mechanism that can populate the task form fields as local task variables. As of now, the form fields get populated into the process instance only when you complete the task.


        This is the controller panel for Smart Panels app




              Unassigned Unassigned
              shan-96 Shantanu Patil
              0 Vote for this issue
              5 Start watching this issue