Possible bugs with Activiti-REST

[pietro_b]

Hello,
I am using activiti-rest to embed workflows in a PHP application.
I've encountered a couple of weird issues

1) Querying for process instances using the "processInstanceBusinessKeyLike" parameter has no effect. Note that "processInstanceBusinessKey" works as intended (this happens with both 5.16.3/4 and 5.17.0)

This bug (which I encountered in 5.16.3) is what made me upgrade to 5.17.0: and here I've met the second issue:

2) I load process definitions with POST -> repository/deployments, and then update the category of the newly loaded process definitions with the PUT -> repository/process-definitions/{processDefinitionId} method.
What happens next is this: the method GET -> repository/process-definitions/{processDefinitionId}, called on a freshly modified processDefinitionId, always returns the OLD category, whereas the GET -> repository/process-definitions, which returns a list, correctly reports the modified category, for the same id!

Obviously some cache is at play here, but I haven't been able to figure out which one.
Many thanks!

[pietro_b]

About #1, I made a typo: the invoked method is GET -> runtime/tasks, to query for tasks by 'processInstanceBusinessKeyLike'

[jbarrez]

1) processInstanceBusinessKeyLike seems only to be supported on tasks. (ok now read your second post). We have a unit test for that that verifies it works. What exactly do you mean with 'no effect' ?

2) I checked the code, but it is removed from any cache we have. Do you happen to run multiple nodes?

[pietro_b]

Hi! By "no effect", I mean that it always return the whole result set, regardless of what I put in the processInstanceBusinessKeyLike parameter.
I don't run multiple nodes, just a vanilla installation of activiti-rest running on a pgsql database.