Application and Module Configuration in ServiceNow is a fundamental aspect of customizing the platform to meet organizational needs. Applications in ServiceNow represent logical groupings of related functionality, appearing as menu items in the Application Navigator (left sidebar). Each application…Application and Module Configuration in ServiceNow is a fundamental aspect of customizing the platform to meet organizational needs. Applications in ServiceNow represent logical groupings of related functionality, appearing as menu items in the Application Navigator (left sidebar). Each application contains modules, which are individual menu options that provide access to specific features, lists, records, or pages.
To configure applications, administrators navigate to System Definition > Applications. Here, you can create new applications, modify existing ones, set display order, assign roles for access control, and determine visibility settings. Applications can be categorized and organized to streamline user navigation based on departmental or functional requirements.
Modules are configured through System Definition > Modules. Each module belongs to a parent application and can be configured with several key properties: Title (display name), Application (parent application), Order (position within the application), Roles (access permissions), and Link Type (determines what the module displays). Common link types include List of Records, URL, Content Page, Script, and Separator.
The Link Type configuration is crucial as it defines module behavior. A List of Records type displays filtered table data, while URL types can link to external sites or internal pages. Script-based modules execute server-side code to determine dynamic content or redirects.
Role-based access control ensures modules appear only to authorized users. By assigning specific roles to modules, administrators can create tailored navigation experiences for different user groups such as IT staff, managers, or end users.
Application menus can also be customized using Application Menus (sys_app_application table) to create hierarchical navigation structures. Administrators can duplicate existing applications, create application templates, and use update sets to migrate configurations between instances.
Effective application and module configuration improves user experience, reduces clutter, and ensures users can efficiently access the tools and information relevant to their responsibilities within the ServiceNow platform.
Application and Module Configuration in ServiceNow
Why Application and Module Configuration is Important
Application and Module Configuration is a fundamental concept for ServiceNow administrators because it determines how users navigate the platform. The Application Navigator (left sidebar) is the primary way users access different areas of ServiceNow. Properly configured applications and modules ensure efficient workflows, improved user experience, and appropriate access control based on roles.
What is Application and Module Configuration?
In ServiceNow, an Application is a container that groups related modules together in the Application Navigator. Think of it as a folder or category. A Module is a link within an application that takes users to a specific destination, such as a list of records, a form, a homepage, or an external URL.
Key Tables: - sys_app_application - stores application records - sys_app_module - stores module records
How Application Configuration Works
Applications have several key properties: - Title: The display name shown in the navigator - Order: Determines the position in the navigator (lower numbers appear higher) - Roles: Controls which users can see the application - Active: Determines if the application is visible - Hint: Tooltip text displayed on hover
How Module Configuration Works
Modules offer various link types: - List of Records: Opens a filtered or unfiltered list from a table - Form: Opens a new or existing record - URL (from arguments): Links to internal ServiceNow pages - Separator: Creates a visual divider between modules - Content Page: Links to a UI page or content page
Module Properties Include: - Title: Display name in the navigator - Application: The parent application - Order: Position within the application - Roles: Access control for the module - Filter: Pre-defined conditions for list modules - Arguments: Additional parameters for URLs
Creating Applications and Modules
To create a new application: 1. Navigate to System Definition > Applications 2. Click New 3. Fill in required fields (Title, Order) 4. Assign appropriate roles 5. Save the record
To create a new module: 1. Navigate to System Definition > Modules 2. Click New 3. Select the parent Application 4. Choose the Link Type 5. Configure the destination (table, URL, etc.) 6. Set Order and Roles 7. Save the record
Exam Tips: Answering Questions on Application and Module Configuration
Key Points to Remember:
1. Order Field: Remember that lower order numbers appear higher in the navigator. This applies to both applications and modules.
2. Role-Based Visibility: If no roles are specified on an application or module, it is visible to ALL users. Adding roles restricts visibility to users with those specific roles.
3. Link Types: Know the different module link types and when to use each. List of Records is most common for showing filtered data.
4. Table Names: Remember sys_app_application for applications and sys_app_module for modules.
5. Navigation Paths: Applications are managed at System Definition > Applications and modules at System Definition > Modules.
6. Filters vs Arguments: Filters are used for List modules to pre-filter records. Arguments are used for URL-type modules to pass parameters.
7. Inheritance: Modules inherit some properties from their parent application but can override role settings.
Common Exam Scenarios: - Questions about making a module visible only to specific users (answer involves adding roles) - Questions about changing the order of applications or modules in the navigator - Questions asking which link type to use for specific requirements - Questions about where to configure applications and modules in the platform