Evaluate removing FlowNodeEventDto

XMLWordPrintable

      Context:

      After merging userTask and events lists in our process instance data, the benefit of mapping engine data first to a FlowNodeEventDto and then to a FlowNodeInstaneDto is not clear. We should evaluate if this is still necessary and if not, remove the extra mapping step and the FlowNodeEventDto class.

       

      AT:

      • If possible, remove FlowNodeEventDto

        This is the controller panel for Smart Panels app

              Assignee:
              Unassigned
              Reporter:
              Helene Waechtler
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: