Easwar Janakiram Kancherla’s Post

When I first started learning ServiceNow, I thought success came from memorizing every module, table, and feature. Turns out — that’s not how real ServiceNow developers think. The biggest shift in my journey wasn’t learning scripts or workflows — it was learning how to think. Once I stopped chasing perfection and started focusing on curiosity, problem-solving, and small wins, everything clicked. That mindset changed the way I learn, build, and grow in the ServiceNow ecosystem. In this new post, I share the 5 mindset shifts that helped me start thinking (and building) like a true ServiceNow developer — even as a beginner. Read it here: https://lnkd.in/erzGHa4Q #ServiceNow #ServiceNowDeveloper #DevMindset #TechBlog #CareerGrowth #LowCode

🚀 ServiceNow Developer Best Practices — Simplified for Real Impact! 🚀 Becoming a great ServiceNow developer isn’t just about building forms and flows — it’s about building them right 💪 Here are some simple but powerful habits every developer should follow 👇 🧩 1️⃣ Follow Naming Standards Think of your codebase as a neighborhood. If every house (script, flow, or field) had a random name, no one could find anything! ✅ Use prefixes like x_company_moduleName ✅ Keep naming clear: incident_autoAssignFlow > flow1 🧱 2️⃣ Don’t Hardcode — Use System Properties Hardcoding values = fixing one bulb by breaking another 💡 Instead, store reusable values (like URLs, emails, etc.) in System Properties. It makes upgrades and configuration changes a breeze! 🔐 3️⃣ Respect Roles and ACLs If everyone can edit everything, chaos will follow 😅 ✅ Limit access by role. ✅ Test ACLs using impersonation — it’s your safety net. ⚙️ 4️⃣ Automate Smartly with Flow Designer Flows should work like traffic lights 🚦— smooth, not blocking. ✅ Use subflows for reusable logic. ✅ Avoid excessive loops or unnecessary wait actions. 🧠 5️⃣ Think Upgrade-Safe Avoid customizing out-of-the-box (OOB) logic unless absolutely needed. Instead, extend or override using Script Includes or Custom UI Actions. That’s how you keep your instance upgrade-friendly. 🧩 6️⃣ Use Scoped Applications Don’t dump everything into the global space! Using scoped apps helps you organize and protect your configurations — like putting projects in separate folders. 🧾 7️⃣ Document Everything If you can’t explain it, you can’t maintain it. ✅ Add comments in scripts ✅ Describe flows clearly ✅ Maintain wiki notes for future devs ✨ Final Thought: Code for the next developer, not just for today’s task. Clean, safe, reusable configurations are the true sign of a ServiceNow professional 👏 #ServiceNow #ServiceNowDeveloper #NowPlatform #DigitalTransformation #Automation #LowCode #ServiceNowCommunity #WorkflowAutomation #ITSM #DeveloperBestPractices #CareerGrowth

<<< Now Experts Time - Evolving as a Developer - Key Focus Areas >>> I recognize the significance of developers in ServiceNow. Numerous videos are available to aid in the transformation into a developer. However, I am committed to clarifying the essential focus areas for developers and providing a step-by-step guide to transition into a developer role. I have created this document as a convenient checklist for you. I intend to produce videos and provide support to our community. Please subscribe and stay tuned for updates on the channel. I believe this will greatly benefit our community. 🔗 Channel: https://lnkd.in/epeNj6GK 🖇️ Blog: https://lnkd.in/e-g72jjG ServiceNow ServiceNow Community #Developer #Transformation #FocusAreas #StepByStep #NowExpertsTime

🎯 Exploring the Scripts – Background Module in ServiceNow! As part of my continuous learning journey in ServiceNow, I recently explored the “Scripts – Background” feature under the System Definition module — and it turned out to be a real game changer! 💻 This module allows running server-side scripts directly on the instance to query, analyze, or update records efficiently. To strengthen my understanding, I experimented with scripts on: 🟢 Incident – fetching and updating ticket data 🟠 Problem – identifying records in states like Assess or Closed 🔵 Change – reviewing and validating change request information Through this hands-on experience, I gained a deeper understanding of GlideRecord operations, and how background scripting helps administrators manage data securely and effectively. It’s exciting to see how small pieces of code can bring big automation and insights within ServiceNow! 🚀 #ServiceNow #LearningJourney #SystemDefinition #ScriptsBackground #GlideRecord #IncidentManagement #ProblemManagement #ChangeManagement #ITSM #ContinuousLearning

🚀 Mastering ServiceNow Script Includes 💡 If you're diving deep into ServiceNow development, one concept you must master is the Script Include 🔥 It’s the backbone of reusable, scalable, and clean code on the ServiceNow platform. Here’s a quick breakdown for fellow developers 👇 🧠 What is a Script Include? A Script Include is a reusable server-side script that lets you define logic once and use it across: 💼 Business Rules ⚙️ Workflows 🧩 Script Actions 💻 Client Scripts (via GlideAjax) ⚙️ Why Use Script Includes? ✅ Write once, use anywhere ✅ Keep your code clean & modular ✅ Handle complex server-side logic ✅ Reuse functions across the platform 💡 Best Practices 🔹 Use CamelCase for class names 🔹 Keep logic clean & reusable 🔹 Use AbstractAjaxProcessor for client-callable scripts 🔹 Log with gs.info() for debugging 🔹 Test via Scripts - Background before deployment 💬 What’s your go-to use case for Script Includes in ServiceNow? Drop your thoughts, tips, or examples below 👇 — let’s learn together! #ServiceNow #ServiceNowDeveloper #ServiceNowDevelopment #ScriptInclude #GlideAjax #ServiceNowScripting #JavaScript #TechCommunity #CodingTips #Developers #Automation #NowPlatform

As a developer in ServiceNow, there comes a time when copy/pasting code isn't worth it. As a senior dev, i was brought in to help someone complete a project. I'm working with another developer and we are consolidating 8 years worth of code spread out across 9+ workflows and many activities in each workflow. Overall there are about 37 different activities where code was literally just copied and pasted across each activity. Converting all of that code into a Script include is very rewarding. Why? Because you're breaking down code duplication. the same code 37 different times that took up 5k+ lines of code was condensed to roughly 700 lines of code. It allows you to see just how much code was duplicated, it gives a better understanding of how to create smaller chunks of code that can easily be reused, and overall, collect all similar code into a central place. It's like using the "cloud" for ordinary people. When asked to change code, it can be changed in 1 spot, not 37 spots and 9+ workflows. You no longer have to check out 9 workflows to make a spelling correction. Working with agile, an update to everything can now be a 3 point story, instead of a 13 or 21 point story. Testing: Yes, MUCH easier. Bring up a background Script and execute the code in the Script include. Adding something or making a change used to take 2-3 weeks to make the change and test the change. Now it's a matter of a day or 2, or maybe even just a few hours. See, Script includes, are a VERY powerful tool to understand. We have a general Script include that covers many of our everyday use, very common, very plain scripts, all consolidated into what we call "quickUtils". No more do we need to write a jillion GlideRecord queries. Now we can just call this quickUtils and pass in a few parameters. I highly encourage every developer to put everything you can in a Script includes. If you have any questions, please let me know. comment here or message me directly. ServiceNow, #ServiceNow, ServiceNow Community, #Developers, #CodeCreators

🚀 ServiceNow Scripts & Policies Explained with Personas If you’ve ever tried explaining ServiceNow scripting & policies to someone new, you know it can feel overwhelming. Here’s a simple persona-based breakdown to make it easier: 🔹 Client Script – The Form Helper Runs in the user’s browser (form level). Guides users in real-time—like validating input or auto-filling fields before the form is submitted. 🔹 Business Rule – The Silent Judge Works on the server, behind the scenes. Ensures processes run smoothly without the user noticing. Example: automatically assigning an incident to the right support group. 🔹 Script Include – The Toolbox Master Reusable server-side code that can be called from Client Scripts, Business Rules, or other Script Includes. Keeps development clean and consistent. 🔹 UI Policy – The Strict Parent Controls form behavior directly for the user. Makes fields visible, mandatory, or read-only right on the screen. 🔹 Data Policy – The Lawmaker Applies rules across all data entry points—whether through forms, imports, or integrations. Guarantees data integrity by enforcing things like mandatory or read-only fields everywhere. ✨ Each of these has its role, but together they keep workflows user-friendly, automated, and reliable. #ServiceNow #ITSM #ServiceNowScripts #TechExplained #ServiceNowPro

Day 51/90 – Learning ServiceNow Upgrading ServiceNow Instances – From Basics to Advanced An upgrade isn’t just a version change — it’s like renovating a house. You don’t just add new paint; you also check the wiring, plumbing, and ensure everything still works with the latest design. From planning, testing in lower environments, handling skipped records, to ensuring integrations stay intact, a smooth upgrade is all about preparation Real-world tip: Always treat non-prod upgrades as a dress rehearsal for production. #ServiceNow #Upgrade #TechnicalDocumentation #DayToDayWork