Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.

Define criticality for application services

Log in to subscribe to topics and get notified when content changes.

Define criticality for application services

For each application service, select a criticality level that reflects how important it is to your organization operations.

Before you begin

Determine how important the application service is to your organization.

Role required: sm_admin

About this task

Typically, you might assign high criticality to application services, which impact your customer base or sales revenue, while giving low criticality to internal application services causing minor inconvenience to organization employees. For example, you could set high criticality for an application service that supports sales functionality using the organization web site. An application service that provides internal printing for the organization employees could receive low criticality.

Criticality determines the prominence of an application service on the Event Management dashboard. You can also use a criticality value to define recovery strategies.
Figure 1. Example of an application service criticality on the Event Management dashboard

Example of an application service criticality on the Event Management dashboard

Procedure

  1. Navigate to Configuration > Application Services > Application Services.
  2. Alternatively, if Service Mapping is deployed, navigate to Service Mapping > Home. Then click Completed.
    The Home page displays only information on application services that Service Mapping can discover or already discovered. This page does not display information on application services that are created manually or using the API.
  3. Select the relevant application service.
  4. Click Additional Info.
  5. Select the appropriate option from the Business criticality list.
  6. Click Update.
Feedback