Specifying a View for a Module

Sue Frost · ‎05-13-2019

We are working in the Application Portfolio Management scoped application.

We have the Business Applications module which displays / uses the Business Application view:

We've now built a new module and view to display each Application Owner's list of applications with a subset of fields:

However, we are unable to reliably have the correct views used in from the correct modules.

We found some documentation that suggests that if the module doesn't specify a view, the alphabetically-first view is used. That's not the case here. Regardless of what we call our views (we originally had used 'Application Owner' and changed it to 'Owner Application'. We've cleared the cache and done everything we can think of, including validating that there are no other copies of the views.

According to my read of the product documentation, we should be able to specify which view to use in the module screen.

What are we doing wrong?

Sue Frost · ‎05-16-2019

I wound up going to ServiceNow and got an explanation:

So, the issue is with users ability to change views using "view_changer" role.

- As an "admin" or "view_changer", you will have an ability to change views, that creates the following user preferences on user's name:
cmdb_ci_business_app.view
cmdb_ci_business_app_list.view

- Until the above user preferences are created, your module views are honored. Once they are created when you start changing views (say business_applications to owner_application), the 2nd module records would start showing (owner_application), or vice versa.

- If you create a module an want to force users to view that view only in list/form, this can be done for end users who cannot change views (without view_changer) role.

- For ITIL users or agent_admin or project_manager, they contain view_changer role, and they can change views that sets the above user preference, and your module views are no longer honored.
https://ecodevchild3.service-now.com/sys_user_role_contains_list.do?sysparm_query=contains%3D8a454be...

- You can fix one view for any module for a particular table by using "sysparm_view_forced" parameter, but this will make all other modules/records to show that fixed view, but I believe this might not help your business requirement to use multiple modules.

In a nutshell, you can set a default view but if the user overrides it (and sets their preferences), then they're on their own.

View solution in original post

Michael Fry1 · ‎05-13-2019

View names shouldn't have a space and should be lower case. Check under System UI > Views - for the correct view name.

Sue Frost · ‎05-14-2019

Thanks Michael,

Our view name is correct. The title does have a space.

Michael Fry1 · ‎05-14-2019

The name is the view name, not the Title.

Sue Frost · ‎05-14-2019

I'm confused.

Our view NAME as per the screen print is "owner_application".