Introduction to ServiceNow Plugins & Core Concepts
Plugins in servicenow are like small software packages that help in instances with better features and functionalities. In this topic, we will be covering the plugin and the pre-installed plugins that ServiceNow offers.
It will also highlight the importance of the dependent plugin and the demo data in ServiceNow instances.
What is Plugin?
ServiceNow plugins are software components that provide additional features and functions within instances. The plugin’s usage and activation are based on application requirements and management needs, such as IT asset management, HR requests, and customer service.
For Example, think of ServiceNow as a smartphone, and the applications we install are the plugins. So, to better use the smartphone (ServiceNow), we need applications (plugins).
Let us understand how to check installed plugins in servicenow. To do so, in your ServiceNow Instance, move to Application Navigator → System definition → Click Plugins.
Once you click Plugins, an Application Manager window will open. To check the plugin details, use the Application Manager window.
Application Manager Interface
The application manager window consists mainly of 4 important areas that help you operate seamlessly.
- The Search Bar: It helps users identify plugins by name or ID. It helps filter plugins without scrolling through lists.
- The Three Main Tabs: They are used to identify the plugin status. It includes the segments, namely, Available for you, Updates, and installed plugins.
- The Left Pane: Includes filters that let users narrow down the results, making it easier to find plugins.
- The Top Bar: Options such as activity log, switch views (legacy to classic), request plugin, and open store (to buy/download third-party apps) are found here.
Predefined Plugins Installed in ServiceNow
Just as smartphones come with pre-installed applications such as a camera, calculator, and notepad, ServiceNow also includes core plugins. The pre-defined ServiceNow plugins are out-of-the-box features that activate when a ServiceNow instance is created. They are not to be installed as they are foundational.
Some of the major predefined plugins are:
| Plugin Name | Description | Real-World Use |
|---|---|---|
| Task [com.snc.task] | The “Mother” of all tickets. | Every Incident, Problem, or Change request is a “Task”. |
| System Import Sets | Allows data import. | Used to upload Excel sheets of users or assets into ServiceNow. |
| User Administration | Manages Users, Groups, Roles. | Essential for creating logins for employees. |
| Connect Support | Real-time messaging. | Used for chat functionality between agents. |
| Connect Core | Base chat architecture. | Backend support for messaging. |
Understanding the predefined plugins helps users identify the problem between system and custom functions. It helps with troubleshooting if any feature stops working.
Remember, it is difficult to uninstall plugin servicenow as these predefined plugins are in the core system.
Also, if you install new plugins, they depend on the predefined plugins. To identify these dependency plugins and assess their importance, let us proceed.
Importance of Dependency Plugins
ServiceNow Dependency plugins are helper plugins for the main/core plugins, providing additional functionality. For example, you install an HR service Delivery plugin in your ServiceNow instance. It might automatically install smaller plugins, such as HR core, HR integrations, and more.
Think of it this way: Imagine you buy a car (main plugin). You will need car seats, tyres, and an engine (dependency plugins). Without these, the car is useless.
These dependency servicenow plugins are important as they help users with:
- Troubleshooting: If any feature is not working, it is because the dependency plugin is not installed properly or is inactive. It is easier to identify the problem and resolve it.
- Licensing Costs: Sometimes, a free plugin may depend on a paid plugin. So you need to know this before installing to avoid extra cost.
- Impact Analysis: If you install one plugin, it may affect other parts of the system due to dependencies.
As we come to the end of this topic, let us discuss ServiceNow demo data and its importance.
Importance of Load Demo Data
Demo data are sample/fake records that ServiceNow installs with the plugins. These records populate the system with dummy information so the application does not look empty.
Users get an option to servicenow load demo data after plugin activation to either install the plugin with or without demo data. The major reasons to have demo data are:
- Visualization: It is not efficient to view reports with no data. The demo data populates the charts, so you can see how the report will look.
- Learning: It helps new users understand how to complete the forms and enter data in the reports.
- Client Demos: When showing the product to clients, an empty system can look unappealing. Demo data makes the products look alive and functional.
Demo data in ServiceNow is like the Lorem Ipsum text we use on websites to visualize the final look of the web page after the actual data is added. It makes it easier to test workflows before final reports.
What’s Next?
After understanding the core plugin concepts, we will highlight ways to manage and activate plugins in the next section, including deactivating and upgrading them.
Next Topic
