Being self-taught ServiceNow developer, a lot of things I learned was from other people’s posts on ServiceNow community, knowledge sharing among colleagues, various blogs and chats, however still today the information on ServiceNow is limited. That leads to developers being not aware of existing features so they create their own custom solutions, they don’t know something that is possible and they tell stakeholders it cannot be done, they do things and write code in a super complicated way that could be done with a few lines of OOTB code.
That’s why I decided whenever I come up with something that is not well known by other ServiceNow professionals, I would like to document my findings and contribute to the community, so the information is available with a simple search engine search and users are enabled to get the most out of ServiceNow.
The goal of this blog is not to give blind copy-paste solutions to resolve your problems and incidents, but to share the knowledge that allows developers to understand the root cause of their problems and obtain an ability to develop a fix. Usually, quick fixes, while giving credit to inexperienced, create more issues with time.
*The views and opinions expressed in this blog are those of the author and do not necessarily reflect the official policy or position of any other organization, employer, or company. Assumptions made are not reflective of the position of any entity other than the author – and, since we are critically-thinking human beings, these views are always subject to change, revision, and rethinking at any time.