When you make a API GET, you might want to filter on a nested entity. When you do this with the camunda engine, you are just unable to. In my opinion it seems only logical to be able to use the filter, but it stays empty.
Solution:
Make it available. Doesn't seem like an out of the box enhancement, more of a design flaw honestly.
Page 1 / 1
closed it because it was supposed to be an idea
Hi,
Can you explain bit more by filter based on a nested entity ?
you should be able to do something like below using workflows. Filter is on StateCode nested entity
Hi @kamnlk, This is not really a filter, this is a parameter that is passed.
The filter which I mean is the one exactly below the Statecode parameter.
In this case this would suffice. But if we want to filter on “state_Code = ‘AR’ OR State_Code = 'WA’” that would only be possible through the filter option. But in this case the filter stays empty.
@JoDe
I see your point, But you could use Reference_StateCodes entity set to directly call in the nested entity and use the filter in there instead,