-
Sub-task
-
Resolution: Fixed
-
L3 - Default
-
None
-
Not defined
Context:
See parent ticket. We need to add a new Filter type to BE: FlowNode Start/EndDate filters which filter given reports by the start/endDate of flowNodes. In userTask reports this filter should only be applied to userTasks. Note that, similar to assignee filters, this filter type will not work on viewLevel for incident reports, we can only do the instance filtering for viewLevel filters here.
Structure: see follow up notes on confluence
Example (fixed date):
[{
"type": "flowNodeStartDate" // or "flowNodeEndDate"
"filterLevel": "view",
"appliedTo": ["3fhi5r8ri83", ...] // or ["all"]
"data":
{
"flowNodeIds" : null, // or ["userTask1", ...] for instanceLevel
"type" : "fixed", // fixed, rolling or relative filter data fields here
"start": "2017-11-11T11:11:11",
"end" : "2017-11-11T11:11:11",
"includeUndefined": true // optional
"excludeUndefined": false // optional
}
}, ...]
Note that the flowNodeIds selection for viewlevel will not be available in the UI and always stay null, so in the BE this filter will always be applied to all flowNodes in the model.
Reference for rolling and relative date data here
AT:
- A new viewLevel FlowNode Start/EndDate filter structure is added to BE
- on userTask reports, the filter is only applied to userTasks
- Filter definition is added to Confluence