General ServiceNow platform and AI fundamentals
What this domain tests
The General ServiceNow platform and AI fundamentals domain checks whether you can explain how the platform stores and exposes data and where AI capabilities fit, without confusing configuration with code.
Core platform rules
- An instance contains applications; applications contain modules and tables. Tables inherit fields through extension, so Incident extends Task and carries Task fields.
- Records are rows in tables; fields are columns. The sys_id is the unique 32-character identifier; display values are not keys.
- Access is layered: roles and groups grant access; ACLs enforce record- and field-level read/write/create/delete; UI policies change form behavior; client scripts run in the browser; business rules run on the server.
- Prefer configuration over customization; scoped applications isolate custom code and support source control.
AI fundamentals
ServiceNow AI includes Predictive Intelligence (classification, regression, similarity, clustering), AI Search, Virtual Agent, and Now Assist generative AI. Generative skills such as case summarization and knowledge article generation use LLMs grounded with instance data and must respect ACLs. Predictive models train on historical records and need clean, representative data.
Worked example
A request asks for a new VIP checkbox on Incident that must appear only for the service desk. The correct design is a field on the Incident table, added to the form, with form-level control through a UI policy or role-based ACL. If the requirement is that the field must never be editable through the API, a UI policy is insufficient because it is client-side; use an ACL or data policy on the server.
Traps
- Treating a UI policy as security.
- Hardcoding sys_ids instead of using dynamic filters or display values.
- Assuming generative AI ignores ACLs; grounding must be verified.
- Confusing table extension with table duplication.