Application Repository and Store

Application Repository and Store in ServiceNow – Complete Guide for CAD Exam

Introduction

Understanding the Application Repository and Store is a critical component of the ServiceNow Certified Application Developer (CAD) exam. This topic covers how applications are managed, distributed, and installed within the ServiceNow ecosystem. Whether you are building custom applications or leveraging existing ones, knowing how the repository and store function is essential for both real-world development and exam success.

Why Is the Application Repository and Store Important?

The Application Repository and Store serve as the central mechanisms for application lifecycle management in ServiceNow. Their importance includes:

• Centralized Application Management: They provide a single location to publish, version, install, and update applications across multiple ServiceNow instances.
• Collaboration and Distribution: Developers can share applications across teams, organizations, and the broader ServiceNow community through the ServiceNow Store.
• Version Control: The repository maintains different versions of applications, enabling rollbacks, upgrades, and controlled deployments.
• Governance and Compliance: Organizations can control which applications are available, ensuring only approved and tested applications are deployed to production environments.
• Ecosystem Growth: The ServiceNow Store allows third-party vendors and ServiceNow partners to offer certified applications, expanding the platform's capabilities.

What Is the Application Repository?

The Application Repository is a centralized storage location hosted by ServiceNow where all custom and shared applications are stored. Think of it as a private or organizational library of applications that can be installed on any instance connected to the repository.

Key characteristics of the Application Repository:

• It is hosted on the ServiceNow infrastructure, not on individual instances.
• Every application developed in ServiceNow Studio or through the Application Engine can be published to the Application Repository.
• Applications in the repository can be installed, updated, or uninstalled on target instances.
• The repository supports versioning, meaning you can publish multiple versions of an application and manage which version is installed on a given instance.
• Access to the repository is controlled through ServiceNow credentials and entitlements.
• It stores applications as scoped applications, which ensures encapsulation and prevents conflicts between applications.

What Is the ServiceNow Store?

The ServiceNow Store is the marketplace for ServiceNow applications. It functions similarly to an app store (like Google Play or the Apple App Store) but specifically for the ServiceNow platform.

Key characteristics of the ServiceNow Store:

• It is accessible at store.servicenow.com.
• It contains applications developed by ServiceNow, technology partners, and third-party vendors.
• Applications listed on the Store go through a certification and review process by ServiceNow to ensure quality, security, and compatibility.
• Organizations can browse, request, and install Store applications directly onto their instances.
• Store apps can be free or paid, depending on the vendor and the application's functionality.
• A system administrator typically manages Store application installations and updates.
• The Store integrates with the Application Repository — once an application is obtained from the Store, it appears in the instance's available applications for installation.

How Does the Application Repository and Store Work?

Here is a step-by-step breakdown of how these systems work together:

1. Application Development
A developer creates a custom application using ServiceNow Studio or the App Engine Studio. The application is developed within a scoped application environment, which isolates its resources (tables, scripts, UI components) from the global scope and other applications.

2. Publishing to the Application Repository
Once the application is ready, the developer publishes it to the Application Repository. During this process:
• A version number is assigned (e.g., 1.0.0, 1.1.0).
• The application is packaged with all its artifacts (tables, business rules, UI pages, etc.).
• The published application is stored in the repository and becomes available for installation on other instances.

3. Installing from the Repository
On a target instance (e.g., a test, staging, or production instance), a system administrator can navigate to System Applications > All Available Applications > All to view applications available in the repository. From there, they can:
• Install the application for the first time.
• Update to a newer version if one has been published.
• Uninstall the application if it is no longer needed.

4. Obtaining Applications from the ServiceNow Store
For Store applications:
• An administrator visits store.servicenow.com and browses or searches for the desired application.
• They request the application, which may require approval or purchase.
• Once approved, the application becomes available in the instance's Application Repository for installation.
• The administrator then installs it from System Applications > All Available Applications > All.

5. Updating Applications
When a new version of an application is published (either custom or from the Store), the target instance will show an update available indicator. The administrator can then choose to update, ensuring the latest features, bug fixes, and security patches are applied.

Key Concepts to Remember

• Scoped Applications: Applications published to the repository are scoped, meaning they have their own namespace and do not interfere with other applications or the global scope.
• Application Scope: Each application has a unique scope identifier (e.g., x_mycompany_myapp) that prefixes all its artifacts.
• Publishing vs. Deploying: Publishing sends the application to the repository; deploying (installing) brings it from the repository to an instance.
• Team Development and the Repository: In team development scenarios, the repository serves as the central source from which all instances pull the application. This is different from update sets, which are used for moving individual configurations.
• Update Sets vs. Application Repository: Scoped applications should be moved between instances using the Application Repository (publish and install), not through update sets. Update sets are primarily used for global scope changes.
• Dependencies: Applications can have dependencies on other applications or plugins. The platform checks for these dependencies during installation.
• Entitlements: Access to certain Store applications may require specific licensing or entitlements from ServiceNow.

Application Repository Navigation in ServiceNow

• System Applications > Studio: Used to develop and publish applications.
• System Applications > All Available Applications > All: Shows all applications available for installation from both the repository and the Store.
• System Applications > All Available Applications > Installed: Shows currently installed applications on the instance.

Exam Tips: Answering Questions on Application Repository and Store

The CAD exam may test your knowledge of the Application Repository and Store in various ways. Here are tips to help you answer confidently:

1. Know the Difference Between the Repository and the Store
The Application Repository is the backend storage for all published applications (custom and Store). The ServiceNow Store is the public-facing marketplace. Exam questions may try to confuse the two — remember that the Store is for discovery and acquisition, while the Repository is for storage, versioning, and deployment.

2. Understand How Applications Are Moved Between Instances
A very common exam topic: Scoped applications are moved between instances by publishing to the Application Repository and then installing on the target instance. They are not moved via update sets. If an exam question asks about the best way to move a scoped application from development to production, the answer involves the Application Repository.

3. Remember the Role of ServiceNow Studio
Applications are developed and published using ServiceNow Studio. Know that Studio is the primary IDE for scoped application development and that publishing is done from within Studio.

4. Version Management
Be prepared for questions about versioning. When you publish an application, you assign a version number. Instances can install specific versions, and updates are managed through version comparisons.

5. Watch for Keywords in Questions
Look for keywords like publish, install, update, scoped application, Application Repository, and ServiceNow Store. These keywords often indicate the correct answer path.

6. Scoped vs. Global
The Application Repository deals with scoped applications. Global scope changes are typically managed with update sets. If a question mentions a scoped application, think repository. If it mentions global configurations, think update sets.

7. Installation and Dependencies
Know that when you install an application from the repository, ServiceNow checks for plugin dependencies and application dependencies. If a required dependency is not met, the installation may fail or prompt for the dependency to be activated first.

8. Access and Permissions
System administrators typically manage application installations. Developers publish applications, but the installation on target instances is an admin function. Exam questions may test role-based responsibilities.

9. Eliminate Clearly Wrong Answers
If an answer choice suggests using XML exports, manual file transfers, or email to move a scoped application between instances, it is almost certainly incorrect. The Application Repository is the standard and recommended approach.

10. Practice Scenario-Based Questions
Many CAD exam questions are scenario-based. For example: "A developer has completed a custom scoped application in a development instance and needs to deploy it to a test instance. What should they do?" The correct answer will involve publishing the application to the Application Repository from Studio and then installing it on the test instance.

Summary

The Application Repository and ServiceNow Store are foundational to how applications are managed, distributed, and maintained across ServiceNow instances. The repository acts as the centralized storage and versioning system for all scoped applications, while the Store is the marketplace for discovering and obtaining certified third-party and ServiceNow-built applications. For the CAD exam, focus on understanding the publish-install workflow, the distinction between scoped applications and global configurations, and the roles involved in application lifecycle management. Mastering these concepts will help you confidently answer related exam questions and build robust application management practices in your ServiceNow career.