Ignoring Principal Class filter in the cmdb_ci list view for a certain role

[Mike50]

Hello Community!

As far as I know, 'Principle Class' filter makes some of the CI classes (those not marked as principle) invisible for the regular end users.

Only admin Users would see CIs associated with non-principal classes in the cmdb_ci list view.

Is there a way to make those CIs associated with non-principal classes visible in the cmdb_ci list view for a particular Group of Users, e.g. based on Role?

Please, advise.

Thank you in advance!

[-O-]

When you say "list view", do you mean the reference field pick list?

As in the pop up window that shows when someone presses the magnifying glass icon next to the Configuration item field on - say - Incident form?

[Mike50]

No, I do not mean the reference pick list.

I meant the basic list view that is displayed when navigating to cmdb_ci.list.

[-O- · Accepted solution]

But in lists no mandatory Principal Class filter is applied.

So if a user does not want to filter CIs to Principal classes, that user can just type cmdb_ci.LIST into the navigator filter and the user will be able to view all CIs.

The way this works is that there is an OOB global filter named "Principal Class" that one "can" apply to any CI list, but it is optional:

The only place where principal class filters are applied automatically is on Configuration item field on table Task, in the reference qualifier, if the current task type is listed in property com.snc.task.principal_class_filter.

It seems to me you are trying to solve a non-existent problem :-).

If a user, no matter the roles it has, wants to view all CIs, it can - the user just has to remove all filters from the list.

One situation where this might be a problem is if the users are clicking on a module in the navigator where the Principal Class filter is a mandatory filter - but this would be a custom module so you should be able to modify it as needed.

But that would only be valid for that specific module and any favorites that might have been created based on it.

User can still type cmdb_ci.LIST and they will be presented with the full list of CIs.

One more thing that could prevent users from viewing all CIs are possible non OOB ACLs applied to specific classes.

But that is a whole different problem, nothing to do with Principal Classes.

[Mike50]

Thank you for the explanation, it helped.

Problem was real, but it turned out to be caused by the custom 'query' BR.

One should not come across the same issue when dealing with ootb setup.

Cheers!