ServiceNow problems new hires hit in the first 90 days
The first challenge on a ServiceNow project is finding out why something happens: which business rule, client script, UI policy or flow changed a field. Debugging tools such as script tracer and session debug are where most tickets start.
- Business rules: before versus after versus async, current.update() in a before rule causing recursion, and order values clashing.
- Client side: client scripts versus UI policies, g_form behaviour, and GlideAjax calls returning null.
- Server scripts: GlideRecord queries inside loops, missing setLimit, and GlideAggregate for counts.
- ACLs: users who cannot see a field or record because of table, field or script conditions, and roles that are not inherited as expected.
- Flow Designer and IntegrationHub: flows that never trigger, wrong run-as user, and errors hidden in execution details.
- Update sets and scoped apps: changes captured in the wrong update set, missing dependencies, and collisions when committing to test.
ITSM, CMDB and upgrades
Much ServiceNow work sits in ITSM: incident assignment rules, SLA definitions, change approval workflows and catalog items with variables and variable sets. Job Support helps you trace an SLA that paused wrongly or a catalog item that creates the wrong tasks.
Upgrades bring skipped records to review and ATF tests to update. Sessions help you understand what a skipped record means for a customised object and how to decide whether to keep or revert it.
What a ServiceNow support session looks like
Rahul joins a ServiceNow practice at a large Indian IT services firm, supporting a US retailer. His story is to auto-assign incidents by location, but assignments keep reverting. In a Job Support session he uses the script tracer output to find an older after business rule overwriting assignment_group, reorders the logic, and writes an ATF test for it.
During the client's Teams refinement call, the live transcript helps him capture acceptance criteria accurately before he estimates.
Using ServiceNow job support responsibly
Instances contain employee and customer records, so share configuration, not data.
- Never share instance admin, SSO or integration account credentials.
- Remove names, emails and incident details from screenshots and scripts.
- Follow your employer's and client's rules on sharing scripts and update sets.
- Build and test in development or test instances, then promote through the approved process.
ServiceNow job support pricing and how to start
Job Support costs $5 per hour with taxes included. Each hour includes 200 AI credits plus support, and hours and credits never expire. Pay by Stripe or bank transfer. Refunds apply only if the tool does not work.
Start with the free plan: 5 live Copilot minutes and 100 AI credits, no card. Install the desktop app on Windows or macOS.