L3 - Default What is the desired functionality that you are missing?
Today, as an Optimize user I can filter process instances by string variables only using "is" or "is not".
As an Optimize user, I would like to be able to filter process instances by string variables using "contains" and "not contains" as well.
Which problem are you going to solve with this functionality?
Efficiently filter instances where text is longer and full match does not make sense.
Examples include specific IDs or ErrorCodes within longer texts.
Context: OPT-3974 asks for Wildcards. Might make sense to combine the tickets and do only one thing in the end and combine the solutions.
This is the controller panel for Smart Panels app
1.
|
String variable filters can have "contains" operators for process reports |
|
Done | Unassigned |
2.
|
I can use the new "contains"/"not contains" operator for string variable in reports |
|
Done | Unassigned |
3.
|
I can use "String contains" in dashboard filters |
|
Done | Unassigned |
4.
|
Document String Variable Contains filter |
|
Done | Unassigned |
5.
|
String variable filters can have "contains" operators for decision reports and dashboard filters |
|
Done | Unassigned |