
We were wrong, ServiceNow Brazil doc links can be pinned
A correction. We said no version-pinned Brazil documentation link existed. One does, and this is the URL form that produces it.
ServiceNow / Product coverage
Source-linked reporting organized by product, platform, and the topics that connect them.

A correction. We said no version-pinned Brazil documentation link existed. One does, and this is the URL form that produces it.

Most of ServiceNow's Brazil deprecation list is a planning signal. One line is a live change to how catalog role ACL grants work on upgrade.

ServiceNow's Brazil release notes are live and dated, with a documented September 24 Early Availability date and roughly 90 product areas changed.

Input Modification ships with Brazil and reaches personal developer instances on September 24. The Troubleshooting Agent needs Otto and Now Assist for Platform.

Lux goes GA in Q4 2026, it is built on LIT, Base UI and Tailwind CSS, and ServiceNow says Workspaces and Angular Service Portals have no deprecation plan.

Otto for Creator's September release makes Build Agent self-upgrading from the Store, and the exceptions decide which of your instances actually drift.

ServiceNow's reworked AI Agent Studio goes from Advisor opportunity to running agent on one screen. These are the review questions to ask before the click.

An accurate CMDB is a precondition, not a benefit. Discovery repays the spend only where change, triage, licence position or security response consume the data.

The choice between a configured integration and a script gets settled by who is free that week, and your entitlement decides more of it than anyone admits.

A customer portal collects a page from every team that asks. Decide who owns the scope, where the logic lives and what anonymous visitors see.

Domain separation partitions ServiceNow data for a handful of real reasons and constrains the platform for years. Scoped apps and access control usually fit better.

Agents are absorbing the configuration work, and the premium is moving to judgement, boundaries and saying no.

ServiceNow supports only the current and previous release family, so falling two behind turns your upgrade into one ServiceNow schedules for you.

Building on ServiceNow App Engine looks close to free because the platform is already paid for. The costs that decide it arrive in year two.

Most teams buying ServiceNow need ticket capture, routing, knowledge and reporting. A real CMDB, cross-team SLAs and non-IT workflow are what justify the platform.

ServiceNow captures changes as you make them and Power Platform packages what already exists. Standardise the rules around both instead of merging them.

The scripts and business rules inside your instance outlive whoever wrote them. Record why the logic exists, keep it in one place, and fail loudly.

Phase one lands or stalls on four calls made before build: real scope, named data owners, whether the CMDB is in, and a counted integration list.

ServiceNow's ITSM products are applications on a platform. App Engine lets you build your own there, inheriting the workflow, approvals and catalog you already run.