ServiceNow CAD Course Notes

Forms/views are presentation over table data; do not confuse hiding a field with deleting or securing it. Use UI Policies for simple field-state behavior, Client Scripts for browser events, asynchronous GlideAjax for server data, display Business Rules/g_scratchpad for data known at form display, and Record Producers for catalog-style intake that creates target-table records.

• Confusing UI Policy vs Client Script.

• Identify the layer first: presentation, server logic, authorization, cross-scope runtime, lifecycle, or integration.

Security questions are about the correct enforcement layer. ACLs authorize users to records/fields; application scope and Application Access govern cross-scope runtime operations; Restricted Caller Access can target one caller/resource; menu/module roles govern navigation visibility. Client hiding is never a substitute for authorization.

• Confusing Same ACL requirements vs multiple ACL alternatives.

• Identify the layer first: presentation, server logic, authorization, cross-scope runtime, lifecycle, or integration.

Choose automation by timing and transaction needs: Flow Designer for declarative processes; before/after/async/display Business Rules for database-timed server logic; Scheduled Script Executions for time-based work; Events for decoupled handlers; Script Includes for reusable server code; properties for configurable values; reports for analysis rather than stored chart data.

• Confusing Before vs after vs async vs display.

• Identify the layer first: presentation, server logic, authorization, cross-scope runtime, lifecycle, or integration.

Design record-centric applications around a sound data model, appropriate platform fit, application scope, navigation modules, and supported experiences. ServiceNow is strongest when structured records, workflow, security, reporting, notifications, and integrations are central to the business problem.

• Confusing Reference vs extension.

• Identify the layer first: presentation, server logic, authorization, cross-scope runtime, lifecycle, or integration.

Know the lifecycle boundary between Git source control, Application Repository distribution, Update Sets, and delegated development. Use one coherent promotion path, version what developers share, and grant only the development capabilities each delegated developer needs.

• Confusing Commit vs pull vs tag vs branch.

• Identify the layer first: presentation, server logic, authorization, cross-scope runtime, lifecycle, or integration.

Import Sets stage data; Transform Maps map and control target updates; coalesce identifies existing target records. REST/SOAP integrations require correct endpoint/authentication configuration, controlled credentials, error handling, and verification. Transport success is not the same as correct data.

• Confusing Import Set vs Transform Map.

• Identify the layer first: presentation, server logic, authorization, cross-scope runtime, lifecycle, or integration.