Welcome to part 16 of the Builder series.
In this video, we’ll show you how to add menus and modules to the application navigator to give users quick access to information and functionality.
This video is a continuation of the Builder series and uses the Safety application created earlier.
The Safety department technicians have been using the Safety app for some time...
... and realize that a list with all the safety issues isn’t the best place to start.
As records accumulate, the closed issues are getting in the way...
... and the technicians would like to see a few pre-filtered lists to help them navigate.
Luke, our safety manager, suggests adding two new options to the Classic UI application navigator:
One, a list of just the “open” issues...
... and the other for issues “assigned to me,” which means assigned to the logged-in user.
Although these are no-code configurations, to complete them, we need either the admin role...
... or the delegated developer role with granted access to All File Types.
We’ll begin by going into Studio and collapsing this side menu.
That allows us to easily drill into Navigation and open the application menu for Safety.
At the bottom of the page, we can see the three modules associated with this menu.
They were created automatically by Guided App Creator when this app was first created.
These define how the three options show up here.
We’ll create two more for Luke.
Let’s start with the list of open issues.
The title will appear on the menu.
Rather than typing “Open Issues,” we already have a separator that groups these together as “Issues”....
... so we’ll just use the word “Open” here.
It would be redundant to include the word “Issues” on each module we add to this menu section.
Next is the order.
Looking at the Application Menu record, we see 1, 2, 3 for the order of existing modules...
... so 4 makes sense here.
The Visibility section is where we could apply roles to specify who can access the module on the application navigator...
... but the parent application menu is already handling that, so we’ll leave it blank.
In the Link Type section, we want to create a list of records…
... on the Issue table.
And we asked Luke what he meant by “Open issues” because we don’t have a state value of Open.
He said, “Anything that’s not complete,” so we’ll apply the filter, State is not Complete.
We submit that to save it.
On our main browser tab, we do a quick refresh to test our results...
... and we now see Safety > Issue > Open in the application navigator.
This list brings up all the issues that are not complete...
... as validated by the breadcrumbs beside the show/hide filter icon.
Now let’s take care of Luke’s other request, to show all the issues assigned to the logged-in user.
Again, we start from the application menu record in Studio and click New on the related list of modules.
We’ll title this one “Assigned to me.”
Give it the order value of 5 to follow our new Open module.
Select the Issue table again.
And this time the filter will be “Assigned to is (dynamic) me,”...
... so it uses a dynamic value of the user who’s logged in at the moment.
We submit that...
... do another refresh on the main browser tab...
... and there’s our new module.
When we click it, we have a list of issues assigned to the system administrator.
If Luke uses the same module, he’ll get a list of issues assigned to him.
Very handy.
If needed, we can also create modules accessing records on other tables, reports, dashboards, or even a specific URL.
There are several options to make it easy for your users to navigate through the system.
For more information, see our product documentation, knowledge base, or podcast.
Or ask a question in the ServiceNow Community.