
Dynamics 365 Field Service agent will apply its own schedules
Microsoft's Field Service scheduling agent is moving to recurring runs that write optimised bookings onto the board with no dispatcher starting them.
Topic coverage
Source-linked reporting and practical patterns organized around a shared enterprise applications question.

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

An SAP column names ITOCHU applying AI to general ledger posting for raw-material trades. No result, scale or date has been published yet.

SAP says two Joule smart glasses pilots at EssilorLuxottica were built in two weeks. The shop-floor one recognises customers, and consent goes unmentioned.

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

Microsoft published real traffic and server load figures behind Copilot Studio agent flows. The load drop matters more than the 72% cost headline.

San Juan Regional's bed-assignment and EVS response times dropped sharply one month after go-live. The third metric in the same release barely moved.

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.

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.

SAP put drones and humanoids on Joule at its first Embodied AI Jam. Our read: every use case rests on an equipment or routing record a person keeps accurate.

SAP's Embodied AI Jam sent teams home with use cases and architectural proposals. Here is the five-part test that separates a robot demo from a process.

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

SAP's Embodied AI Jam listed warehouse automation without naming a system. Here is the task data, write-back, and exception path a floor team needs first.

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.

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.

A plugin can stop a bad save and a cloud flow cannot. That difference, plus who maintains it, settles most calls.

The two products share most of their design. The real choice is who owns the thing in two years, which budget pays, and who gets paged at 2am.

Most integrations handle success and failure and nothing between them. The partial load, the business rejection and the empty run are the ones that hurt.

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.

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.

Routing rules pile up one exception at a time until nobody can explain why a lead landed where it did. Here is how to find the rule that actually ran.

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.

A queue between Power Automate and Oracle Fusion guarantees delivery. Someone still has to decide what a duplicate, stale request, or rejected record means.

A flow that stops is visible in run history. A flow that half-finishes leaves two systems disagreeing, so design the handlers, retries and owner first.

Model queues on kinds of work, pin down the order your assignment rules evaluate in, and give every request that matches nothing a queue someone opens daily.

Capacity, priority and presence decide how Omni-Channel behaves at peak. Set them from real numbers, then test with two agents and one saturated queue.

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.

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.