ServiceNow Development & Administration (CSA / CAD)

• ServiceNow architecture: Tables, Records, Fields, Dictionary overrides, and Form design
• User administration: Groups, Roles (admin, itil, approver_user), and Access Control Lists (ACLs)
• ITSM workflows: Incident triage, Problem root-cause investigation, Change advisory board (CAB) approvals, and Service Catalog creation

• Automating multi-system approvals and tasks using Flow Designer and IntegrationHub spokes
• Client-Side Scripting: Client Scripts (onLoad, onChange, onSubmit), UI Policies, and UI Actions
• Server-Side Scripting: Business Rules (before, after, async), GlideRecord queries, GlideSystem, and Script Includes

• Configuration Management Database (CMDB): Identification and Reconciliation Engine (IRE) and CI relationships
• REST API integrations: Scripted REST APIs and consuming third-party webhooks (Jira, Slack)
• Update Sets, Application Repository deployment, and Certified System Administrator (CSA) certification practice

Q1: What is the difference between a synchronous (before/after) Business Rule and an Async Business Rule in ServiceNow?

Before/After Business Rules run synchronously within the same user transaction thread—meaning the user's screen waits until the script finishes executing, which can degrade user performance if external API calls or heavy loops are performed. Async Business Rules run in the background via the ServiceNow scheduler queue after the database change has been committed, freeing up the user interface immediately for better performance.