Details
-
Sub-task
-
Resolution: Fixed
-
L3 - Default
-
None
-
Not defined
Description
Context:
The new FlowNode start/EndDate filter should be added to the Report FlowNode Filter menu in the UI as a "FlowNode Date" filter option which can be either start or end date, similar to instance date filters. Additionally, the existing instance date filter option in the menu should be renamed to "Instance date" (note that the filterType "start/EndDate" will be renamed with the follow up OPT-5425)
Filter structure see[ notes on confluence|https://confluence.camunda.com/pages/viewpage.action?pageId=98620466&src=jira]
Please also note the comments below for details on the text on the instanceLevel filter modal.
AT:
- New FlowNode Date filters are added to flownode filter menu
- on instance Level, this includes a flowNodeSelection. On viewlevel, there is no flowNode selection and the flowNodeIds field is null (see UX designs and confluence notes)
- Instance date filter menu option is renamed in UI (note: we do not yet rename the "type" of "start/endDate" filter data itself, this will happen in a separate follow up)
UX Concept:
• A date can be set for a single Flow Node only
• Multiple applications of the filter can create combinations linked with AND
• In User Task view Filter may display no results depending on the selected Flow Node
Design -> https://zpl.io/bLJBJ4m
Filter menu -> https://zpl.io/bW8Oo4e