
SAP extends the Joule promo for Build, not for ABAP AI
SAP extended the free Build features to December 31, but ABAP AI still goes commercial on October 1. Two deadlines now, and SAP's pricing wording conflicts.
Topic coverage
Source-linked reporting and practical patterns organized around a shared enterprise applications question.

SAP extended the free Build features to December 31, but ABAP AI still goes commercial on October 1. Two deadlines now, and SAP's pricing wording conflicts.

Power Pages site owners can now be reassigned without a support case, and Microsoft's own documentation says the transfer cannot be automatically undone.

Microsoft now hosts Copilot-generated code inside the tenant boundary, and the admin center inventory matters more than the hosting does.

Salesforce's newsroom post lists six trusted capabilities behind its agent platform. Trusted agency and trusted actions are the two an architect has to test.

The named plaintiffs moved on September 14, 2026 to certify a class against Workday itself, and the briefing runs to a March 9, 2027 hearing.

Work IQ public preview opens September 30 with governed actions that write changes back to source records inside the permissions your users already hold.

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.

The no-cost period for Joule for Developers ends September 30 and ABAP AI moves to commercial licensing on October 1. Find out who is using it first.

Microsoft's Field Service scheduling agent is moving to recurring runs that write optimised bookings onto the board with no dispatcher starting them.

Argano's fourteenth acquisition since April 2025 brings 300-plus Oracle PLM and supply chain staff. Value undisclosed, and your escalation path may move.

Microsoft's updated Power Platform bounty schedule pays double for critical cross-tenant flaws and names Dataverse twice. Here is what an admin should check.

Salesforce says requests stalled on an internal login service. Authentication is the dependency most continuity plans never wrote down.

SAP's new accruals agent drafts journal entries and shows the policy rule and the math behind each one, but an accountant still decides what posts.

Salesforce says TSA's Ace agent resolves 96% of roughly 100,000 monthly traveler conversations without escalation. That rate deserves a second look.

Salesforce bills agent work in Agentic Work Units, and one business outcome can consume wildly different numbers of them. Your renewal needs a forecast.

SAP now plans AI token spend inside its normal finance cycle after employee and agent usage became a triple-digit-million-dollar risk.

Three quarters of CIOs told diginomica they can't see every AI tool in their systems. ServiceNow's shift zero pitch depends on data they don't have.

Workday shares jumped on a report that take-private financing is coming together. Nothing is signed, and here is what a tenant owner should ask anyway.

Dynamics 365 Activate profiles a company's whole Salesforce data set before migration starts, already at billions of records. That access needs scrutiny.

Siemens is routing 2,500 monthly leads across 132 countries through two Agentforce agents, and the real test is quality control at that scale.

ServiceNow will run Experian's risk and identity agents on live loan and claims decisions, but Experian built and controls them.

Procurement's confidence in working with the rest of the business fell 16 points in a year. A new SAP tool answers a narrower question.

Siebel CRM took 63 patches in Oracle's latest Critical Patch Update, a sign the platform isn't as dead as budget plans assume.

Sana's HR award points to 300-plus skills reaching into Gmail, Slack, and Salesforce, and the checks a security lead needs before turning one on.

Salesforce put a number on Claudeforce at Dreamforce 2026, 37 sales skills running through an MCP server in Claude, and that number is a permissions question first.

Salesforce framed AIforce at Dreamforce 2026 as AI replacing the CRM interface. For the admin who built what's underneath it, the question is where that logic goes next.

The autonomous security specialists ServiceNow previewed in June reach general availability today, and the checklist for trusting them is still thin.

Raleigh's CIO says ServiceNow AI saved a month of time. The number only means something once you know whose month, measured how.

Oracle September update shipped 673 patches, but the number that matters is how many are reachable without a login, and Oracle already named where that risk concentrates.

Oracle's September update fixed 240-plus flaws needing no login at all. That says less about Oracle's code than what stays reachable from the open internet.

Salesforce's job-ready Agentforce agents each own one function. When orchestration passes work between them, your team must define what crosses and who owns it.

SAP's September 10 services update counts Joule users and success plans. After go-live, the number an architecture team needs is in its own support queue.

Salesforce's new long-horizon runtime lets Agentforce agents pursue goals for weeks. These are the run-level controls the post leaves for you to ask about.

ServiceNow's AI Gateway enforces policy as an agent invokes an MCP tool. Here is which rules belong at that layer and which still belong to the record.

Microsoft's PPCC 2026 preview asks attendees to bring one process. The stage agent will work either way. What decides the pilot is who owns that process.

Core, Advanced, and Max bundle Slack, Tableau Next, and Flex Credits into every Agentforce seat, so the tier choice now belongs in architecture review.

Eleven straight years as a Gartner Leader says Workday will keep investing in HCM. It says nothing about your pay rules, your ledger, or your integrations.

Core, Advanced, and Max bundle Agentforce into every seat, so the purchase request that used to trigger a governance review never gets filed.

Microsoft's AI at Work roadmap, Message Center, and Learn each answer a different planning question. Here is which channel each decision belongs to.

Microsoft's PPCC 2026 procurement example sends only higher-risk exceptions to a person. Most approval steps in a live tenant would fail that test.

Salesforce says Winter ’27 agents run whole workflows across channels. A run that lasts days outlives your change window, so someone must own it.

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.

Microsoft's PPCC 2026 preview runs a procurement request through Copilot, an agent, a workflow, and a reviewer. We'd ask which Dataverse row holds the trace.

Salesforce's Core, Advanced, and Max editions carry clear seat prices. The Flex Credit pool, bundled overlap, and migration labour decide the real bill.

Workday names a city live in five months and a state that took thirty. The gap is pay rules and fund accounting, and you can count both before you plan.

Salesforce's Winter '27 post rests autonomous workflows on governed CRM data. Here is what governed has to mean before an agent runs a case end to end.

Salesforce says Winter ’27 agents carry a case across voice, Slack, and email. Closed now means every channel is settled, and your status field can't say that.

Workday's Q2 release says more than 5,500 customers use at least one organic agent. The count says the switch is on. It says nothing about the work.

Salesforce’s Winter ’27 post is dated August 31 and goes live October 12. Here is how to turn its fifteen items into owners, sandbox dates, and a freeze.

Microsoft's always-on AI at Work roadmap removes the wave date that used to force a review. Someone in your tenant now has to own that date.

Workday says AI drove a quarter of new ACV. The condition rules and approval chains already in your tenant are what make those agents safe to switch on.

Microsoft's August 25 post keeps public roadmap items and tenant change notices in separate channels. Someone on your team has to join them.

Workday's fiscal 2027 Q2 release reports a $27.4 billion subscription backlog and AI in a quarter of new ACV. Here is how to write that into a plan.

Workday's fiscal 2027 second-quarter release lists a run of product changes under the revenue line. Here is how a tenant owner should sort them.

Microsoft retires Release Planner on November 15, 2026. What admins and architects should export, rebookmark, and reschedule before that date.

Workday may close the gap you are about to fill. Test whether the need is common, price the year of waiting, and name who removes your app later.

Seasonal releases mostly add capability. Release Updates change platform behaviour your configuration already depends on, and enforcement arrives either way.

Consumption pricing moves the spending decision into engineering. Attribute usage to owning teams and capture a baseline before the rate changes.

An agent that changes a worker record carries risks a service desk agent never does, and HR deployments need a governance bar set well above the usual checklist.

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.

Winter '27 lands October 12, the Release Planner retires November 15, Brazil is arriving and 2026R2 is already live. Six vendors, one team calendar.

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.

A group of companies almost always belongs in one Workday tenant. Here is when a second one is genuinely right, and what the single tenant costs you.

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.

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 supports only the current and previous release family, so falling two behind turns your upgrade into one ServiceNow schedules for you.

Microsoft is retiring the twice-yearly release wave model. Release plans stop publishing in September 2026 and the Release Planner retires by November 15.

Consumption pricing moves cost control from the contract to the code, and BTP spending drifts because nobody told the engineers they were spending it.

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.

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

You cannot decline a Fusion Cloud quarterly update forever, so the work is preparation. Who reads the readiness material, and what a regression pack should cover.

Automation pays off on work that is high volume, stable and unambiguous. Anything else buys a permanent maintenance bill for a task nobody struggled with.

Two analysts pull the same headline figure and get different answers because the filter, the date field and the definition were never written down or owned.

Once an app writes to a system of record and someone outside the team depends on it by a date, funding it is overdue, and the cost is speed.

Serving external customers from the ServiceNow incident table holds up until an outage, when the internal clock and the contract clock stop agreeing.

S/4HANA support packs arrive on a plan and BTP services do not. How to split the reading, triage notes, and keep a record that lasts.

A concrete method for sorting Power Platform's twice-yearly release waves and daily message center posts from noise into action.

Oracle says Ask Oracle respects your NetSuite permissions. Two months into rollout, here's the edge case worth testing yourself.

When ITSM and security both claim the CMDB, reconciliation becomes everyone's second job, and nobody notices a stale record until a remediation deadline depends on it.

An unused seat still gets billed. Cross usage logs against the assignment list, flag the quiet accounts, and reclaim seats before renewal locks the price in.

Fifty people can end up depending on a canvas app with no source control and one maker who understands it, long before anyone decides that on purpose.

Name the decision a person keeps, show the reviewer the source and the proposed change, give the queue an owner, and write the answer back to the record.

A ledger of what you skipped and a five-line summary do more for ServiceNow release review than reading the whole document ever will.

A release note is sixty decisions someone else already made. Three questions and a one-line record find the four that need an owner and a date.

A green run history hides the cleanup that follows a bad Power Automate run. Name the recovery owner and measure time to a resolved outcome.

Keeping SAP S/4HANA modifications out of the core only works when someone funds the BTP extension platform, the rewrites, and the retirements.

A modernization program that lists what it will build and never what it will switch off ends up paying for both. Put the retirements in the scope.

A catalog entry for a Power Platform flow should name who gets paged, what to check first, and who can switch it off. The design document stays where it is.

A Power BI tile earns its place by naming the decision it changes, the value that triggers it, and the person who acts. Everything else is a report.

Sales, finance, and operations each hold a correct definition of revenue. A semantic model picks one and hides the rest, so name a steward before it does.

Two correct figures for the same measure differ on timing, population or attribution. Find which one, write the definition down, then name an owner.

Route every step to a security group rather than a person, delete the approvals nobody has ever rejected, and let conditions skip the rest.

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.

Scope, identity and a realistic approval step decide whether a Fusion agent rollout stays reviewable. Capture the baseline and the off switch first.

A table permission granted for one page applies everywhere that table can be reached. Check the whole surface before a Power Pages site faces the internet.

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.

When finance is too small to split creating a vendor from paying one, pick the two conflicts that carry the money and mitigate them in writing.

Writing the two week handover runbook exposes every job only you can run, and the page telling your stand-in what not to attempt is the one that saves you.

People describe the documented path when their manager is in the room. The real process lives in the exceptions, and you have to go looking for it.

Most CABs read thirty changes aloud and approve them in forty minutes. Here is a method that puts the meeting's attention on the two that could hurt you.

A practical method for keeping ServiceNow access requests auditable long after the project that justified them ends.

Oracle and SAP both ship bundles where nearly every entry claims top severity. Here is the four-question order I actually use to triage them for real.

A practical method for catching Workday comp cycle configuration drift before go-live, built around an approval step that quietly survives the manager it was written for.

A full governance program takes years to fund. Material and vendor master ownership is where an S/4HANA team can start this quarter.

A working rule for deciding which Power Platform solutions get their own dev, test, and production environments, and who approves promotion between them.

Workday Extend apps read HCM data by default. Decide who reviews access, who tests against real data, and who owns the app before it ships.

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 migration statement of work only holds up if it names a discovery gate, a rehearsed change order, and a written data assumption.

A fifteen-minute conversation before the first screen is built, recorded on the Dataverse solution, does more than an approval form completed after go-live.

The four numbers a platform owner needs before a Power Platform, Dynamics 365, or Agentforce repackaging note gets forwarded to finance.

Power BI can only answer what the Dataverse model was built to hold. Write the leader's questions first, with the decision, grain, and freshness each needs.

Before a Copilot Studio or Agentforce pilot gets more users, check it has four named owners, a visible failure path, and a review date.

When a shared Power Automate flow fails, find the work that stopped, name one lead, and write the ServiceNow record before anyone resubmits a run.

Send the script early, load your own duplicates and odd legal entities, and ask to see a failure. A CRM demo only counts as evidence when you run it.

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.