-
Task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
M
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
[OPT-5251] Evaluate removing FlowNodeEventDto
Status | Original: Open [ 1 ] | New: In Specification [ 10000 ] |
Labels | Original: current_release refactoring | New: next_release refactoring |
Labels | Original: next_release refactoring | New: refactoring |
Labels | Original: refactoring | New: potential_for_next_quarter refactoring |
Effort | Original: Not defined [ 11259 ] | New: S [ 11254 ] |
Labels | Original: potential_for_next_quarter refactoring | New: nice_to_have potential_for_next_quarter refactoring |
Status | Original: In Specification [ 10000 ] | New: Open [ 1 ] |
Labels | Original: nice_to_have potential_for_next_quarter refactoring | New: nice_to_have refactoring |
Labels | Original: nice_to_have refactoring | New: nice_to_have potential_for_next_quarter refactoring |