Show number of consumers for public server action in Service Studio

On our radar

It would be nice to see if an action is consumed by other modules when it is marked as public. This could be displayed as a count in brackets next to the action name. 

Yes, you can see this by using right-click->find usages in all modules, but if you have to do this for 50-odd actions it becomes time-consuming.

The benefit is that, at a glance, you are able to see if an action is used by other components in your ecosystem.

This will obviously impact the load time of an espace in Service Studio, so the benefit might not outweigh the performance hit...

Created on 3 Jul
Comments (4)

Hi Hanno,

What are you trying to achieve? Is it to know the impact of changing an action how many affected modules are we talking?


In short, yes.

It will also aid in scoping work when a change request affects an action in that you would be better able to gauge the possible touch points and effort that will be required to effect the change.

We also had duplication of logic where actions in different espaces were performing the same function. So we had a function f1 in espace A doing the same as function f2 in espace B, but both f1 and f2 were referenced across other espaces. We would opt to remove f1 or f2 based on the lesser number of references and thus have fewer reference updates to do.

Changed the category to Backend and the status to

On our radar

I see your point. Actually this idea falls on a recurrent feedback that we have been receiving that is to have a big picture of where "my" module is located on overall factory landscape, this will give a sense of external modules that are referencing my module?

I will consider this idea as in radar, but the final solution may not be a count next to each action, but a more broader solution that will fit the entities, structure, actions, etc.

Another reason is that if an action is marked as public, you don't know if it is used locally in the espace. Usually, unused actions are underlined with a yellow squiggly line, but unused public methods are not.

This will help in removing deprecated/unused logic.