-
Feature Request
-
Resolution: Won't Do
-
L3 - Default
-
None
-
None
-
3
-
Not defined
Context:
Current, adding multiple duration filters will filter instances based on ORING all the existing filters. It is also useful to filter durations based on AND. For example, if we want to filter instances where flownode 'approveInvoice' took more 4 days AND 'InvoiceApproved' took less than 2 day.
Design -> zpl.io/290AyjY
This is the controller panel for Smart Panels app
[OPT-3601] OR/AND switch for flowNode duration filter
Mentioned Roles |
Mentioned Groups |
Summary | Original: Add the ability to add OR for duration filters | New: OR/AND switch for flowNode duration filter |
Description |
Original:
Context:
Current, adding multiple duration filters will filter instances based on ANDING all the existing filters. It is also useful to filter durations based on OR. For example, if we want to filter instances where flownode 'approveInvoice' took more 4 days or 'InvoiceApproved' took less than 2 day. Note: This might not be very useful for the case of instance duration filter. |
New:
Context:
Current, adding multiple duration filters will filter instances based on ORING all the existing filters. It is also useful to filter durations based on AND. For example, if we want to filter instances where flownode 'approveInvoice' took more 4 days AND 'InvoiceApproved' took less than 2 day. |
Mentioned Roles |
Mentioned Groups |
Attachment | Original: image-2020-04-29-12-30-23-192.png [ 33648 ] |
Labels | Original: needs_testing product_design | New: needs_testing potential_for_3.2 product_design |
Description |
Original:
Context:
Current, adding multiple duration filters will filter instances based on ORING all the existing filters. It is also useful to filter durations based on AND. For example, if we want to filter instances where flownode 'approveInvoice' took more 4 days AND 'InvoiceApproved' took less than 2 day. |
New:
Context:
Current, adding multiple duration filters will filter instances based on ORING all the existing filters. It is also useful to filter durations based on AND. For example, if we want to filter instances where flownode 'approveInvoice' took more 4 days AND 'InvoiceApproved' took less than 2 day. Design -> zpl.io/290AyjY |
Mentioned Roles |