Managing Applications · Topic 1 of 2
Downloading and Installing Applications
Install ServiceNow applications for the CAD exam: publish to the application repository, install from the Store, versions, upgrades, demo data and roles.
- 4 min
- Publish from Studio to the application repository; install on each target instance.
- A published version is fixed; changes need a new, higher version.
- Installing from the application repository needs the admin role.
What it is
A scoped application is built on a development instance, but it is used on test and production instances. To get it there, the developer publishes a version, and an administrator on each target instance installs that version.
Applications come from two places. Your own company's applications come from the application repository. Applications made by ServiceNow and partners come from the ServiceNow Store. Both are installed the same way on the instance.
How it works
Publishing a version
In Studio, the developer publishes the application to the application repository. Publishing asks for a version number and a description. Each new release needs a version higher than the one already published.
A published version is a fixed snapshot of the application files at that moment. Changes made afterwards on the development instance reach other instances only when a new version is published and installed.
Only files that belong to the application scope are packaged. A file created while the application picker was set to Global is not part of the scoped application, so it is missing on every instance that installs it.
Where applications come from
| Source | What it holds | Who can see it |
|---|---|---|
| Application repository | Applications your company published from its own instances | Instances of your company |
| ServiceNow Store | Applications built by ServiceNow and partners, certified for sale or free use | Any customer, once the app is entitled to the instance |
| Update set | The application exported as an update set XML file | Any instance you load it into |
The application repository is the normal route between your own instances. The Store is the route to other companies. An update set export is the fallback when the repository is not an option.
Installing on an instance
Installing needs the admin role on the target instance. Applications are installed from System Applications > All Available Applications > All, where you filter, pick the application and choose Install.
Before the install runs, a review step lists the version and any dependencies, such as plugins or other applications, that will be installed with it. You can also choose whether to load demo data. For Store applications, demo data that is skipped at install cannot be loaded later.
Store applications must first be entitled to the instance from the ServiceNow Store. After that, they appear in the same list and install like company applications.
Upgrading
When a newer version is published to the repository, it becomes available on the target instances. The admin selects the new version from the same list and installs it, which upgrades the application in place. Until then, the instance keeps running the version it has.
Repository or Git
| Need | Use |
|---|---|
| Share code between developers during development | Git source control |
| Move a finished release to test and production | Application repository |
| Give the application to other companies | ServiceNow Store |
How the exam asks about this
- "A fix was made on the development instance after version 1.2 was installed in production. Production does not show it." The version is a snapshot; publish a new version and install it.
- "Which role is needed to install an application from the application repository?" The admin role on the target instance.
- "A script include works on the development instance but is missing after install." It was created with the application picker on Global, so it was not packaged.
What to remember for the exam
- Publish from Studio to the application repository; install on each target instance.
- A published version is fixed; changes need a new, higher version.
- Installing from the application repository needs the admin role.
- Installs show dependencies and offer optional demo data.
- Store applications must be entitled to the instance before they can be installed.
- Only files in the application scope are packaged.
Always check the application picker before creating a file. A file saved in Global looks fine on the development instance but never ships with the application.
Common mistakes
Editing the installed application on production. The fix exists only on that instance, not in the application source, so it is missing from every later version. Make the change on the development instance and publish a new version.
Treating the Store and the repository as the same thing. The repository holds your company's own applications. The Store holds certified ServiceNow and partner applications that need an entitlement.
Expecting publishing to update target instances. Publishing only makes the version available. Nothing changes on a target instance until an admin installs or upgrades it there.
Check yourself
How do changes made after a release reach production?
Publish a new, higher version to the application repository and install it on production; the old version is a fixed snapshot.
What must happen before a Store application can be installed?
It must be entitled to the instance from the ServiceNow Store; then an admin installs it from the list of available applications.
Why can a file be missing after an application is installed elsewhere?
It was created with the application picker on Global, so it is not part of the scoped application package.
Topic 1 of 2 in Managing Applications
Test yourself on Managing Applications
The full ServiceNow CAD 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.