> For the complete documentation index, see [llms.txt](https://docs.sharelogic.com/unifi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharelogic.com/unifi/install/servicenow-compatibility.md).

# ServiceNow Compatibility

## Introduction

As of August 2026, ServiceNow is shipping weekly security hot fixes on top of quarterly patches and family upgrades. In an effort to help ensure weekly releases do not negatively affect our customers, we have introduced a new weekly testing schedule to align as best we can with that cadence.

This page records what we tested and when.

A result here means we ran our standard checks on the builds we could obtain that week. We do not test every Unifi × ServiceNow pairing. It is not a guarantee for every customer configuration, and we encourage customers to perform their own testing regardless of the results shown here.

## What “tested” means

We install the latest weekly ServiceNow security patch as soon as we can — or as soon as it is applied to our instances. At this time, it is not always clear whether these changes can be scheduled in advance.

Each week we target two pairings:

* **Backstop** — last supported Unifi release on the latest available patch of the previous ServiceNow family (N-1)
* **Current** — current Unifi release on the latest available patch of the current ServiceNow family (N)

When we have Early Availability access, we also test an **upcoming** Unifi release on the next ServiceNow family (N+1) so we can catch family-level issues before GA. When that family is released, it becomes current; current becomes backstop; the old backstop leaves the weekly schedule.

On those builds we run our standard Unifi checks: install or upgrade of the relevant Unifi store build and matching Global Utility, followed by a standard set of tests covering various integration methods, attachment handling, configuration and diagnostics.

Other combinations are not on the weekly schedule. We investigate those when a customer reports a specific pairing.

That is not a substitute for your own testing. Your integration implementations, installed plugins and modules, and custom configuration all affect how Unifi behaves. We cannot test those outcomes.

We only email customers if testing finds an issue that could affect integrations. Otherwise the result is recorded here.

## Supported families

| Role     | ServiceNow                        | Unifi                | When                    |
| -------- | --------------------------------- | -------------------- | ----------------------- |
| Backstop | N-1, latest patch / weekly hotfix | Last supported Unifi | Ongoing                 |
| Current  | N, latest patch / weekly hotfix   | Current Unifi        | Ongoing                 |
| Preview  | N+1 Early Availability            | Upcoming Unifi       | Until that family is GA |

{% hint style="warning" %}
We do not weekly-test every Unifi × ServiceNow pairing. The backstop and current tracks are the combinations we stand behind for N and N-1. Preview is only to catch family-level breaks before GA. Anything else is investigated when it comes up.
{% endhint %}

## If a weekly release causes a problem

1. Run **Diagnostic** on the platform and the affected integration.
2. Check this page and the latest Unifi release notes.
3. Confirm you are on a supported Unifi + Global Utility pair for that family.
4. Raise a ticket with us (and with ServiceNow if it looks like a platform change). Include family, patch/hot-fix string, Unifi version, and any diagnostic failures.

We will fix Unifi when the break is in our code. When ServiceNow changes a platform API or security constraint, we depend on their fix or a documented workaround.

## Weekly test log

### Week 37 - 14 September, 2026

* Australia patch6 / Unifi 4.5.1 <mark style="color:$success;">**Pass**</mark>

### Week 36 - 7 September, 2026

* Australia patch5w36 / Unifi 4.5.1 <mark style="color:$success;">**Pass**</mark>
* Australia patch2 hotfix3a / Unifi 4.5.1 <mark style="color:$danger;">**Fail**</mark>

Customer reported issue with patch2 hotfix3a.

### Week 35 - 31 August, 2026

* Australia patch5w35 / Unifi 4.5.1 <mark style="color:$danger;">**Fail**</mark>
* Zurich patch12w35 / Unifi 4.5.1 <mark style="color:$danger;">**Fail**</mark>

We discovered that inbound attachment processing was broken with the week 35 patch - cause unknown.