Instance Configuration · Topic 1 of 2
Installing Applications and Plugins
ServiceNow CSA: how admins add features with Application Manager, the Store, plugins and scoped applications, including demo data and updates.
- 4 min
- Application Manager is the central place to install, update and review applications.
- Plugins are activated; Store applications are installed.
- The ServiceNow Store is the source of ServiceNow and partner applications.
What it is
An instance starts with a core set of features. Admins add more by activating plugins or installing applications. Both add tables, forms, roles, modules and logic to the instance.
A plugin is a bundle of functionality that ships with the platform and is switched on when needed. An application can be built by ServiceNow, by a partner, or by your own company. Store applications are obtained from the ServiceNow Store.
How it works
Application Manager
The admin works from System Applications > Application Manager. It lists what is installed, what is available to install, and which installed items have updates. From there the admin can install, update or open an application.
Only users with the admin role manage applications and plugins.
Plugins and Store applications
| Plugin | Store application | |
|---|---|---|
| Source | Ships with the platform | ServiceNow Store, from ServiceNow or partners |
| Action | Activate | Install |
| Typical use | Turn on a platform feature | Add a product or an integration |
| Updates | Come with platform releases | Offered in Application Manager when a new version exists |
Activating a plugin adds tables, records and logic to the instance. Treat activation as hard to undo, and do it on a development or test instance first.
Demo data
Some plugins offer to load demo data, which is sample records that show how the feature works. It helps for learning and testing. Do not load it on production, because it adds fake records to a live system.
Application scope
Applications are separated by scope. The default is the global scope. A scoped application has its own scope name, and its tables and scripts are protected from accidental changes by other applications.
Custom applications built by your company get a scope name that includes a company prefix. The Studio tool is used to develop them.
Cross scope access is controlled by the application's settings, so one application cannot freely read or change another application's tables unless it is allowed.
Updates and release management
Application Manager shows when a newer version is available. An admin should read the release notes, update on a lower instance, test, and then update production. Updating a customized application can conflict with local changes, which is why testing first matters.
Your own applications can be shared inside the company through the application repository rather than the public Store.
After installing
Installing an application usually adds new roles and modules. The admin then assigns the roles to the right users and checks that the new application menu appears for them. A user who has not been given the application's role usually cannot use it.
Check the application's documentation for required setup steps, such as properties or data to configure, before announcing it to users.
How the exam asks about this
- "An admin needs to review all installed applications and see which have updates." Application Manager.
- "A team wants to try a new feature with sample records first." Install it on a non production instance with demo data loaded.
- "A company builds an application and wants its tables protected from other applications." Create it as a scoped application.
What to remember for the exam
- Application Manager is the central place to install, update and review applications.
- Plugins are activated; Store applications are installed.
- The ServiceNow Store is the source of ServiceNow and partner applications.
- Demo data is sample data; do not load it on production.
- Scoped applications protect their tables and scripts; global is the default scope.
- Test installs and updates on a lower instance before production.
Activating a plugin or installing an application on production without testing is a common wrong answer. The correct answer starts on a development or test instance.
Common mistakes
Confusing plugins and applications. A plugin ships with the platform and is activated, while a Store application is downloaded and installed. The exam often uses the verbs to separate them.
Loading demo data on production. Demo data is meant for learning and testing, and it leaves sample records mixed with live data.
Thinking scope is the same as role. Roles decide what a user can do. Scope decides which application owns a table or script and which other applications may touch it.
Check yourself
Where does an admin review installed applications and available updates?
In Application Manager, under System Applications.
What is the difference between activating a plugin and installing a Store application?
A plugin ships with the platform and is activated; a Store application is obtained from the ServiceNow Store and installed.
Why should demo data not be loaded on production?
It adds sample records to a live system, so it is meant only for learning and testing.
Topic 1 of 2 in Instance Configuration
Test yourself on Instance Configuration
The full ServiceNow CSA question bank has 600 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by ServiceNow. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.