Remove standard actions/functions for specific Process Service cds

[Kronprinz03]

In generated process services, actions like suspend, resume, cancel, and getInstancesByBusinessKey are also added, although they are generic and not bound to a specific process.

Consider removing those actions from generated process service to remove redundancy, developers can still use the generic process service for those actions.

[schubertha]

Fully agree, I would refrain from adding them.

I understand it's convenient to add the generic functions to the generated service but since there is no inheritance in CDS services, it's not something we can realize without without the downside that the code goes out of sync when new methods are added etc.

We could, if you like, offer in import option that is off by default and if you really like to, you can get current behavior. Then it's configurable but not on by default.

@tilwbr WDYT?

[tilwbr]

@schubertha Thanks for the input.

I am not sure if another option for the import is really necessary, from my point of view it makes the plugin still more complicated to use. I would still prefer the default case to be the current behavior, as you need to connect to only one service to access all functions/actions available.

If the plugin gets updated, with new actions defined in the generic process service, and the user does not want to re-import their processes to get those actions also in the specific process service, it is still possible to connect to the generic process service, which would be the case by default proposed by you. So adding new actions to the generic process service that would also be available in the specific, does not force the developer to reimport.

Let me know what you think 🙂