ServiceNow implementation and configuration
What this domain tests
Implementation and configuration tests delivery discipline: instance strategy, requirements, build, test, promotion, and governance of the configured platform.
Core rules
- Use a development, test, and production instance path; build in development, validate in test, promote to production.
- Capture global configuration in update sets; keep scoped applications in source control and use application repository or pipeline for deployment.
- Prefer configuration-forms, lists, business rules, flows, ACLs-over changing base-system code.
- Use Flow Designer for low-code automation; reserve Workflow Editor for legacy workflows that have not been migrated.
- Model tables and relationships before building forms; align service data with CSDM where the process depends on services.
- Integrations use REST or SOAP; IntegrationHub adds spokes and actions; a MID Server provides connectivity inside the firewall.
- Test with non-admin personas and the roles real users hold.
Worked example
The requirement is: closure notes must be mandatory when state is Closed, for both the form and API. A UI policy with mandatory=true only affects the form; it does not enforce API writes. Add a data policy or server-side business rule to enforce the mandatory value on the server, and keep a UI policy for the form experience. Test as an agent and as an API caller.
Traps
- Promoting an update set without its dependencies or required plugins.
- Using client scripts for security.
- Hardcoding record sys_ids in flows.
- Testing only as admin and missing role-based failures.