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.
Topic coverage
DevOps / ALM
Source-linked reporting and practical patterns organized around a shared enterprise applications question.
Latest reading
Brazil stops catalog roles granting access through ACLs
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 arrive with a date
ServiceNow's Brazil release notes are live and dated, with a documented September 24 Early Availability date and roughly 90 product areas changed.
ServiceNow adds two flow debugging tools, one you can test
Input Modification ships with Brazil and reaches personal developer instances on September 24. The Troubleshooting Agent needs Otto and Now Assist for Platform.
ServiceNow's Build Agent now upgrades itself from the Store
Otto for Creator's September release makes Build Agent self-upgrading from the Store, and the exceptions decide which of your instances actually drift.
Power Platform CLI now reaches the whole tenant
Microsoft put more than 200 auto-generated API commands into the Power Platform CLI preview. Governance and licensing are now a script away.
Analysis and architecture
Why Salesforce Release Updates break things, and who owns them
Seasonal releases mostly add capability. Release Updates change platform behaviour your configuration already depends on, and enforcement arrives either way.
The Power Platform setting most admins have never set
Release waves are gone, so the release channel on each environment now decides when your users meet change. Most estates have never deliberately set it.
Six release cycles and the dates you cannot move
Winter '27 lands October 12, the Release Planner retires November 15, Brazil is arriving and 2026R2 is already live. Six vendors, one team calendar.
Release Radar: BTP updates and the notice you are owed
SAP publishes BTP's update cadence but not a platform-wide retirement notice period. The number you can hold SAP to sits in the contract.
Your NetSuite Release Preview window is shorter than you think
Oracle publishes no global NetSuite release dates, and a Release Preview account takes 5 to 7 days to build and is purged after 14 days without a login.
Salesforce seasonal releases and your sandbox preview window
Winter '27 is generally available October 12, 2026. If your test sandbox was never on a preview instance, refreshing it is the only way onto one.
ServiceNow family releases and the upgrade you owe
ServiceNow supports only the current and previous release family, so falling two behind turns your upgrade into one ServiceNow schedules for you.
There is no 2026 release wave 2 for Dynamics 365
Microsoft is retiring the twice-yearly release wave model. Release plans stop publishing in September 2026 and the Release Planner retires by November 15.
Workday R1, R2 and the weekly updates in between
Workday ships two feature releases a year plus weekly service updates, and nearly all of it arrives disabled, so the real risk is what nobody turns on.
Update sets and solutions will never share one pipeline
ServiceNow captures changes as you make them and Power Platform packages what already exists. Standardise the rules around both instead of merging them.
The ownership debt hiding in your Power Automate flows
Power Automate flows belong to whoever built them, and that single fact quietly creates most of the ownership debt in a mature Power Platform tenant.
SAP clean core, and when to rebuild, extend, or patch
A framework for deciding what SAP work gets rebuilt clean, what becomes a BTP side-by-side extension, and what temporary fix quietly becomes permanent.
Related guides
A Salesforce sandbox estate you can test a release in
Preview status belongs to the instance rather than a setting, so the sandbox you test a seasonal release in has to be planned months before the notes land.
A lifecycle for Workday Extend apps that outlives the builder
Build where the work persists, rehearse the promotion, version every build, and decide who can switch the app off before anyone needs to.
Writing ServiceNow and Power Platform code people can maintain
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.
What breaks in week two after a ServiceNow go-live
Hypercare catches the loud failures. Notification rules that never fire, one-person assignment groups and SLA clocks on the wrong schedule wait for week two.
How many Power Platform environments you actually need
A working rule for deciding which Power Platform solutions get their own dev, test, and production environments, and who approves promotion between them.
Build a Power Platform ALM pipeline makers actually use
A pipeline survives when the build takes under two minutes, test data looks real, and a maker can roll back without opening a ticket.
A release checklist for shared Power Platform solutions
The questions a platform team should ask before a shared Power Platform solution reaches other makers, and where to keep the answers for the next owner.