Details

    • Type: Sub-task
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2.4.0, 2.4.0-alpha1
    • Component/s: backend
    • Labels:
      None

      Description

      Context:
      Until now, the configuration field is completely handled by the front-end. However, since the refactoring of the report update in the front-end it is necessary that the back-end can represent the configuration field as well. Two reason: One using the rest api the configuration field can't be set on report creation, so the back-end needs to know which fields can be set and what are the default values. Second, it is necessary to migrate the configuration field as well.

      AT:

      • the configuration field in the single process report, single decision report and combined process report is filled with the default values.
      • when I update a report, the configuration field is still affected by the upgrade
      • the rest-api documentation contains a description how the configuration field looks like

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              sebastian.stamm Sebastian Stamm
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: