Configure optional modifications and streamline some of the data specifically for the Tenable Vulnerabilities import integration in the ServiceNow Tenable Vulnerability Integration.
The business rules, client scripts, and UI actions that the system creates automatically to perform custom transitions exist only while the state flow records that use them are present.
Several types of components are installed with Customer Service CTI Demo Data.Business rules are added with activation of Customer Service CTI Demo Data.
Configuration Compliance automate calculating initial values for the fields on test results. The condition for each calculator is evaluated in order, and the first matching calculator is used.
The transaction log records browser activity for an instance. To aid in debugging of system issues, you can filter transaction logs by application scope, limiting transactions that appear to only those transactions originating in specific scopes.
Detailed field definitions, validation rules, filtering logic, and technical specifications for group ownership in Business Impact Analysis (BIA) records.
Edit the decision table that classifies imported FHIR Organizations as internal or external business locations, so that the classification matches how your organization defines internal and external entities.
Security Incident Response Health dashboard feature provides a centralized view of critical aspects related to incident response process implementation, issues/errors encountered, and performance metrics.
Configure the Priority defaulting for procurement cases decision table to automatically assign priority levels to procurement cases based on conditions you define.
To enable high-level planning on a table that is not a planning item in Strategic Planning Workspace, populate global rank for existing records of this table.
By default in the 2011 SLA engine, the SLA processing is performed by the Run SLAs business rule. This business rule runs synchronously and is the suggested configuration.
Using an agent or building an integration?
The same documentation is available through the public REST API.
GET /api/docs/search?q=GlideRecord&limit=20
GET /api/docs/document?path=…
GET /api/docs/:id?revision=…
Search returns document paths, IDs, snippets, and an index revision. Read by path for a stable reference; numeric IDs should be used with the returned revision. Document bodies are Markdown.