CIS-ITSM: Certified Implementation Specialist - IT Service ManagementDemo

A record producer is a Service Catalog item type that provides an alternative way for users to create records, such as incidents, through the catalog. Requested items are generated by requests, categories organize catalog content, and execution plans define fulfillment.

A Service Catalog can include content items, which provide informational or navigational content within the catalog. Requested items are generated request records, categories group catalog entries, and execution plans define fulfillment activities.

The baseline Change - Normal implementation flow automatically invokes the Change - Implementation tasks subflow, which creates implementation and post-implementation tasks. Users can also manually add Change Tasks in any nonterminal change state; Closed and Canceled changes are excluded. The selected category does not automatically generate Change Tasks.

In the Quebec Problem Management state model, completing the required fields automatically advances a Problem task record from New to Assess.

The Re-analyze action reopens a problem for further investigation and changes its state to Root Cause Analysis. ServiceNow: Investigate root cause of a problem

Model State Transition Conditions control whether a change request can proceed through a defined change-model state transition. They can require that specified field values are populated before the transition from New to Assess is allowed.

The Default Variables Editor is the formatter specifically applicable to record producers. It displays the values of the questions (variables) defined for a record producer on records generated from that producer.

CI Class Manager centrally displays the complete CMDB class hierarchy in a tree view and provides access to CI table definitions, fields, relationships, and associated metadata.

A Portfolio Manager manages and assesses service performance across the Service Portfolio hierarchy, which consists of the Service Portfolio, its Services, and their Service Offerings.

A Portfolio Manager is the operational role responsible for overall portfolio administration, including creating and maintaining portfolio records and related portfolio structures.

ServiceNow Change Management detects scheduling conflicts when a CI is already scheduled by another active change at the same time, when the CI falls in a blackout window, or when the change is outside an applicable maintenance window. Company holiday schedules and assignee shift schedules are not standard conflict types.

A service is associated with a leaf taxonomy node. Non-leaf nodes organize child nodes, whereas leaf nodes display and manage their associated services.

A survey can have trigger conditions that determine when it is sent and to whom. Its survey definition also includes an Anonymize responses setting, which stores responses without the submitting user name.

In the default ServiceNow Problem Management state model, the transition from New to Assess requires the State and Assigned to fields. The State field is managed by the state model, while Assigned to establishes the responsible problem analyst; Configuration item and short description are not the default shared prerequisites for this transition.

A Flow Action consists of inputs that provide data, action steps that perform the work, and outputs that return results.

Flow Designer supports importing a copy of a predefined stage set from the Stage Sets table; changes to that copy do not change the original. It also supports adding and configuring stages in subflows, as well as flows.

By default, ServiceNow treats an inbound email with no identifiable watermark or reference number as a new message and attempts to create an incident from it.

Agent Assist displays results from configured contextual-search sources, including Knowledge and related ITSM or CSM records such as Problems, Changes, and Cases. SQL queries and Runbook Actions are not supported Agent Assist search-result source types. The standard ITSM set also includes Incidents, which is required to make five but is not present in the supplied choices. ServiceNow Agent Assist documentation

ServiceNow’s default Knowledge - Approval Retire workflow requests a knowledge base manager’s approval before retiring an article. If any manager rejects the request, the workflow is canceled and the article remains published.

ServiceNow User Criteria records control access to Service Catalog items and categories. Applying a user criterion through the Available For or Not Available For related lists determines which users may access a particular item.

The default ServiceNow Change Task Type values include Planning, Implementation, Testing, and Review. Therefore, among the listed values, Planning, Testing, and Review are the available default types.

The baseline release record supports the release types Major, Minor, Upgrade, Emergency, Maintenance, and Patch. ServiceNow distinguishes major, minor, and patch application versions as release-version categories; the other choices contain change types or unrelated lifecycle labels.

The incident_manager role is assigned incident-administration responsibilities, including managing Incident Management properties. ServiceNow’s current role documentation also identifies Incident Manager as managing incident properties, while its newer granular Incident Admin role is named sn_incident_admin, not incident_admin.

Major Incident Management uses its own lifecycle state in addition to the incident’s normal state: Proposed, Accepted, Rejected, and Canceled (spelled “Cancelled” in the listed choice). A candidate begins as Proposed, becomes Accepted when promoted, is Rejected when declined, and becomes Canceled when demoted or canceled.