- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
01-05-2023 10:53 PM - edited 01-05-2023 11:22 PM
Hi All,
Hope you are doing great.
In this article I will try to provide my personal inputs on Configuration vs Customization as its always being a query in all developers mind.
Lets first try to understand what exactly it means to have Customization and Configuration :
Customization in ServiceNow :
- Customization in ServiceNow refers to the process of modifying the platform to suit the specific needs and requirements of an organization.
- This can include creating custom applications, modifying existing applications, and configuring the platform to support specific business processes and workflows.
- Customization allows organizations to tailor ServiceNow to their unique needs, helping them to improve their efficiency and productivity.
Configuration in ServiceNow :
- In ServiceNow, configuration refers to the process of setting up and customizing the platform to support an organization's specific business processes and workflows.
- This can include configuring the platform's user interface, creating custom applications and workflows, and integrating ServiceNow with other IT systems and tools.
- Configuration allows organizations to tailor ServiceNow to their specific needs, helping them to improve their efficiency and productivity.
- Some common tasks involved in configuring ServiceNow include setting up users and groups, defining roles and access controls, and configuring integrations with other IT systems.
Configuration vs Customization :
- It is difficult to say which option is better between customization and configuration in ServiceNow, as it ultimately depends on the specific needs and requirements of an organization.
- Customization refers to the process of modifying ServiceNow to suit the unique needs of an organization, while configuration involves setting up and configuring the platform to support specific business processes and workflows.
- It is important for developer to carefully consider their specific needs and requirements when deciding between customization and configuration in ServiceNow.
- Customization can provide a more tailored and personalized solution, but it may require more time and resources to implement.
- Configuration, on the other hand, can be a faster and more cost-effective option, but it may not provide the same level of flexibility and adaptability.
- Ultimately, the best option will depend on the specific goals and objectives of the organization.
Disadvantage of Configuration :
- Limited flexibility and adaptability: Configuration may not provide the same level of flexibility and adaptability as customization. This means that we may be limited in their ability to modify and adapt the platform to support changing business needs and requirements.
- Potential for increased costs: In some cases, configuring ServiceNow to support specific business processes and workflows may require additional integrations with other IT systems and tools. This can lead to increased costs and complexity, especially for larger organizations.
- Lack of personalized solutions: Configuration may not provide the same level of personalized solutions as customization. This means that companies may have to settle for a "one-size-fits-all" approach, rather than being able to tailor the platform to their unique needs and requirements.
Disadvantage of Customization :
- Increased costs and complexity: Customizing ServiceNow can be a time-consuming and complex process. This can lead to increased costs, both in terms of the time and resources required to implement customizations, as well as the ongoing maintenance and support of the customized platform.
- Risk of technical issues and downtime: Customization can involve making significant changes to the ServiceNow platform, which can increase the risk of technical issues and downtime. This can impact an organization's ability to effectively use the platform, and may require additional resources to troubleshoot and resolve any issues that arise.
- Lack of standardization: Customization can result in a lack of standardization across different ServiceNow implementations, which can make it more difficult to share best practices and expertise, and to ensure compatibility with future versions of the platform.
Please be sure to bookmark this article as well as mark it as Helpful if you thought it was helpful.
Regards,
Amit Gujarathi
- 17,713 Views

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Oh how I wish the world agreed on what these terms meant. I suggest reading a blog article I did in 2021 on this topic for a different approach.
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
It could well be that I just lack the background for a sound initial understanding, but these two definitions sound very much the same to me - including language that is verbatim between the two:
Customization in ServiceNow :
- Customization in ServiceNow refers to the process of modifying the platform to suit the specific needs and requirements of an organization.
- This can include creating custom applications, modifying existing applications, and configuring the platform to support specific business processes and workflows.
- Customization allows organizations to tailor ServiceNow to their unique needs, helping them to improve their efficiency and productivity.
Configuration in ServiceNow :
- In ServiceNow, configuration refers to the process of setting up and customizing the platform to support an organization's specific business processes and workflows.
- This can include configuring the platform's user interface, creating custom applications and workflows, and integrating ServiceNow with other IT systems and tools.
- Configuration allows organizations to tailor ServiceNow to their specific needs, helping them to improve their efficiency and productivity.
- Some common tasks involved in configuring ServiceNow include setting up users and groups, defining roles and access controls, and configuring integrations with other IT systems.
Can someone explain the difference beyond the distinction?
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
I think there are only very slight differences in interpretation between the two:
My view is as follows (however, I am sure others will disagree):
A) Configuration is BAU - using standard SN Features without midifcation. Configuration should be encouraged.
B) Customization is generally considered bad and to be avoided if possible. For example, Customization might mean adding fields to tables (so that you now have skipped tables) or changing the default business rules of out-of-the-box ServiceNow - so that they work slightly differently.
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Is creating a custom field on a table a customization?
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
I hear what people are saying and I think there is still considerable confusion regarding Configuration v Customization. Things have come on a lot since Chuck's 2021 Blog on the developer site. There is some nice content on Now Create, covering this topic. Business Smart Customization and What are the best practices for customization. There is also a KB on Now Support, Customizations v Configurations FAQ.
All projects will be different, but one thing I always used to remind my customers, as an EM, was that if custom tables are created, based on your requirements, there may be licensing implications that should be discussed with your Account Executive.
Excessive customization can lead to technical debt, the need to re-implement and a gap in the expected value, not to mention the challenges when upgrading.