Synced Objects
ServiceNow supports the following Synced Objects:- Files: Syncs knowledge base articles from ServiceNow.
- Tickets: Syncs tickets from ServiceNow.
- Permissions: Syncs knowledge base and article read and contribute permissions.
Files
Send a request to Enable Sync to start a file sync of knowledge base articles from ServiceNow.Example
string
A ServiceNow Knowledge Base ID to limit the Sync scope to articles within a specific knowledge base.If not specified, the Sync will ingest articles from all available knowledge bases.
Permissions
Knowledge base article syncs include a Permissions sync that maps ServiceNow access controls into the Permissions API. Permissions are indexed automatically as files are processed. The following ServiceNow access controls are supported:- Knowledge base and article user criteria (can read, cannot read, can contribute, cannot contribute)
- Legacy article roles (
roles,author,manager) - Ownership groups when
glide.knowman.ownership_group.enabledistrue - Article-level user criteria when
glide.knowman.apply_article_read_criteriaistrue - Group, role, department, location, and company memberships resolved from
sys_user
sys_user.email). Pass this value as the user when calling Check Access, Batch Check Access, or List Objects. If email is empty, user_name is used when it is formatted as an email address. Users without a resolvable email are omitted from the permission model.
Required access: The connected ServiceNow account must have read access to:
- Knowledge base permission M2M tables (
kb_uc_can_read_mtom,kb_uc_cannot_read_mtom,kb_uc_can_contribute_mtom,kb_uc_cannot_contribute_mtom) user_criteriaand its membership tablessys_user,sys_user_grmember,sys_user_has_role, and related group, role, department, location, and company tables- The
glide.knowman.apply_article_read_criteriaandglide.knowman.ownership_group.enabledsystem properties
Tickets
Send a request to Enable Sync to start a ticket sync.Example