Unsupported Features: ServiceNow

Here's a breakdown of what Unito's ServiceNow integration can't do yet.

In this article:

• Unsupported ServiceNow fields
• Other ServiceNow limitations
• Other ServiceNow considerations

Unsupported ServiceNow fields

All ServiceNow fields are supported.

Other ServiceNow limitations

• User fields: If user-type fields in your ServiceNow tables don't have public or visible display names, you won't be able to sync display names. Instead, you'll get a long string of alphanumeric characters.

• Rich text: Rich text isn't supported by default, but you can enable it in your flow's advanced options by adding this code snippet: 

  { "translateAllRichTextFields": true }

• Webhook support: Not currently available with this integration.
• Closed records: These aren't supported.

Other ServiceNow considerations

Required fields

Always make sure the ServiceNow fields you set as required for creating new records are mapped in Unito.

Due to a limitation with ServiceNow's API, fields that you mark as required for creating new records don't have to be included in a Unito flow. This means you could potentially create a Unito flow that doesn't sync required ServiceNow fields, meaning a ServiceNow user may need to manually fill out those fields before new work items can be created.

"User needs to change password on login"

If this option is checked in your user profile in ServiceNow, you won't be able to authorize Unito and start building a flow.