ServiceNow Certified Implementation Specialist - IT Service Management CIS-ITSM Exam Questions

The baseline Create Incident Catalog Item is part of ServiceNow’s guided catalog structure, and when a customer needs to add or modify input fields, the recommended approach is to use Catalog Builder. Catalog Builder is designed for quickly configuring and extending catalog items like “Create Incident” without requiring deep technical changes, allowing administrators to add variables, adjust layouts, and update input fields in a guided, low-code environment. This ensures consistency and supports easy maintenance of catalog items compared to more advanced tools like Form Designer or Item Designer, which are used for different configuration purposes.

(Reference: ServiceNow Service Catalog documentation – Catalog Builder and catalog item configuration guidelines)

In ServiceNow Major Incident Management (MIM), the process adds a separate set of MIM-specific states on top of the standard Incident lifecycle to manage the major incident workflow. These states are Proposed, Accepted, Rejected, and Cancelled, which are used to control whether an incident qualifies as a major incident and whether it is officially declared and managed under the MIM process. This extra state model ensures proper governance and approval before an incident is escalated to a major incident. 

In the Now Platform, these UI layouts (such as Default, Major Incidents, Self Service, and Mobile) are called Views. Views define how the same record is displayed differently depending on the user’s persona, device, or process requirements. For example, an incident record can appear in a simplified layout for mobile users, a detailed layout for agents, or a specialized layout for major incidents, all controlled through different views of the same form.

In this ServiceNow configuration, incidents are stored in the sn_task_incident table, which is part of the scoped ITSM data model used in certain implementations where Incident extends from a scoped task structure rather than the traditional global incident table. This allows better modularity and separation within the ServiceNow data architecture, especially in newer or scoped application setups.

In ServiceNow, configuration settings specific to the Incident application (such as incident behavior, default values, and process-related settings) are managed under Incident Properties. These properties control how incidents are created, processed, and displayed within the ITSM module, allowing administrators to tailor incident management functionality without modifying the underlying code.