Skip to content

Add simple search to process defintions#57

Open
aounhaider1 wants to merge 2 commits into
operaton:mainfrom
aounhaider1:search_processes
Open

Add simple search to process defintions#57
aounhaider1 wants to merge 2 commits into
operaton:mainfrom
aounhaider1:search_processes

Conversation

@aounhaider1
Copy link
Copy Markdown

@aounhaider1 aounhaider1 commented Apr 16, 2026

This PR adds a search functionality to process definitions. I have kept it simple and the input is searched against both name and the key.
Bildschirmfoto 2026-04-16 um 17 29 28

Closes #49

@lambdaschmied2
Copy link
Copy Markdown
Collaborator

Hi. Thanks for the contribution.

I'm a bit hesitant to approve this PR, as it isn't really the filtering / search we want at this point.

Is this something you need or is this what you interpreted from #49 ?

The filtering API for Operaton is something different than just filtering the loaded data based on a string.

@aounhaider1
Copy link
Copy Markdown
Author

Hi,
thanks for your input. Yes, I was under the impression that it was based on client-side filtering, but I looked it up and there are actually backend calls for it (though I'm not entirely sure why is it necessary).
Would you be open to merging a 'filtering-feature' similar to the legacy webapps? Or do you have something different in mind for it?

@lambdaschmied2
Copy link
Copy Markdown
Collaborator

Yes, it would need to work like in the legacy web apps.

@aounhaider1
Copy link
Copy Markdown
Author

I had a chance to look at this. I partially implemented the component but ran into an issue with the REST API. As I see it, we are using the REST endpoint provided by ProcessDefinitionRestService here which does not provide filtering statistics based on query. It allows querying on process definition level but we need the process statistics as well for the table.
HOW IT WORKED IN LEGACY APP:
The legacy app used the endpoint provided by ProcessDefinitionRestService.java defined in oepraton/webapps/assembly.
In my opinion there should be an endpoint in engine-rest to filter based on statistics. There are some other solutions for it but I think they would be rather 'hacks'. Let me know what you think.

@lambdaschmied2
Copy link
Copy Markdown
Collaborator

https://docs.operaton.org/reference/latest/rest-api/#tag/Process-Definition/operation/getProcessDefinitions

The currently used endpoint offers all the features we need. The frontend needs to pass the query params, as seen in the docs, to the backend and requires some UI.

See the task page filtering for an example.

@sonarqubecloud
Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add controls for filtering process definitions

2 participants