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

Refactor DateFilterDataDto structure or flowNode, instance and variable date filters

    XMLWordPrintable

Details

    • Task
    • Resolution: Unresolved
    • L3 - Default
    • None
    • None
    • backend

    Description

      Context:

      As discussed in a recent Backend Senate, the current DateFilterDataDto structure is not optimal, mainly because we end up with several fields which are unused for most use cases (eg "end" field for rolling and relative filters "include/excludeUndefined" fields for non variable filters). We should improve the existing structure by ensuring we have separate DTOs which include only the fields relevant for their use cases (they will probably still either share a common abstract parent or interface). 

      AT:

      • DateFilterDataDto structure is split to avoid unused fields 

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            mentioned in

            Page Loading...

            Activity

              People

                Unassigned Unassigned
                helene.waechtler Helene Waechtler
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:

                  Salesforce