Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-2283

Reports for multiple process and decision definition versions

    XMLWordPrintable

Details

    • Feature Request
    • Status: Done
    • L3 - Default
    • Resolution: Done
    • None
    • 2.6.0
    • None

    Description

      AT:

      • As a User I can create reports across multiple process & decision definition versions (e.g. by selecting multiple versions in the version dropdown of the definition selection).
      • As a User I can select "latest" as a version for a report so that if a new version has been deployed to the process engine, this will be automatically considered in the report I built.
      • As a User I am informed about potential inconsistencies with the report data in case when selecting multiple versions - similar to version "all". These inconsistencies can occur when a new definition adds or removes flow nodes.

      Hint: We should consider showing the VersionTag of the process / decision definition, too as for the User this can be relevant information about which version(s) he/she has to select in the dropdown for creating the report he/she needs.

      Wireframe / Behavior
      zpl.io/ankAk8x

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          1.
          Import version tags for definitions and returns them in the definition REST endpoints Sub-task Done Unassigned
          2.
          Allow to set the process/decision definition version to latest Feature Part Done Unassigned
          3.
          I can select multiple versions of a process/decision Feature Part Done Unassigned
          4.
          Simplify definition retrieval endpoints and add latest version to it Sub-task Done Unassigned
          5.
          Using the rest-api allow to evaluate a report based on multiple definition versions Sub-task Done Unassigned
          6.
          The process variable endpoints take multiple versions and tenants Sub-task Done Unassigned
          7.
          New endpoint for decision variable names Sub-task Done Unassigned
          8.
          I can get correlation results for all or the latest version Feature Part Done Unassigned
          9.
          Fix e2e Tests Sub-task Done Unassigned
          10.
          Version Popover has wrong size in Internet Explorer and Edge Sub-task Done Unassigned
          11.
          Store previous selection of explicit versions Sub-task Done Unassigned
          12.
          create reusable Badge component Sub-task Done Unassigned
          13.
          Tab order of radio buttons broken Bug Part Done Unassigned
          14.
          Make Analysis remember selection when changing version Sub-task Done Unassigned
          15.
          Have a way to label checkboxes and radio buttons Sub-task Done Unassigned
          16.
          Add Documentation for new Version selection Sub-task Done Unassigned
          17.
          Make Popover default sizing small Sub-task Done Unassigned
          18.
          Use multiple versions and tenants for the process variable endpoints Sub-task Done Unassigned
          19.
          Add shadow to pop over Sub-task Done Unassigned
          20.
          Use new endpoint for decision variable names Sub-task Done Unassigned
          21.
          Decision Variable name endpoints return too many values Bug Part Done Unassigned
          22.
          Migration of report definition version Sub-task Done Unassigned
          23.
          The available definition version API returns version specific tenants Sub-task Done Unassigned
          24.
          The definition selection shows tenants for the selected versions that don't belong to those versions Bug Part Done Unassigned
          25.
          Remove deprecated `tenants` property on definitionVersionsWithTenants Sub-task Done Unassigned

          Activity

            People

              Unassigned Unassigned
              felix.mueller Felix Mueller
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Salesforce