-
Bug Report
-
Resolution: Won't Do
-
L3 - Default
-
None
-
7.13.0
-
None
Description:
Camunda does not support case-insensitive search by processDefinitionNameLike using the POST /history/process-instance API.
POST /history/process-instance docs state:
| processDefinitionNameLike | Filter by process definition names that the parameter is a substring of. |
However, this is not working.
Steps to reproduce:
[1] Deploy a process definition with a process definition like 'MyProcess'
[2]Start a process instance and complete it
[3] use the POST /history/process-instance to search for a process instance using processDefinitionNameLike with a case insensitive string like 'my'.
Observed Behavior:
Process instance is not retrieved
Expected behavior:
Process instance is retieved.
This is the controller panel for Smart Panels app
[CAM-14056] CamunCase-insensitive search by processDefinitionNameLike using the POST /history/process-instance does not work
Hi wDman,
I am closing this for now due to inactivity.
Let me know if you would like to talk about this further and or would like to contribute.
We can simply reopen the ticket then.
Best,
Tobias
Hi wDman,
thanks for bringing this up.
The behavior you are experiencing is actually expected and not a bug.
The API and that specific parameter are not working case-insensitive and the description also doesn't claim it does.
If you have a look at variableNamesIgnoreCase in that same API, you can see that we provide explicit parameters for case-insensitive search where we see a certain value for a broader user base.
For the specific parameter you are mentioning here, we never had such a request before, therefore there is no such option yet.
We can turn this ticket into a feature request to make such an option available if you like.
A little disclaimer to be transparent: we will probably not work on such a feature in the near future without further indication of other users needing this feature as well.
You are always welcome to extend the REST API yourself and add that option.
If you think this makes sense for a broader user base, we invite you to add a pull request with the necessary changes and test coverage to our GitHub repository.
Let us know if you would like any pointers or help on that. Our Contribution Guide is always a good place to start.
Best,
Tobias