M3CloudSlam

Solutions · Infor M3 release readiness

Know what the next Infor release changes for you, before it lands

Every April and October, Infor updates M3 Cloud Edition. Feature toggles expire, and once expired they can’t be switched off. M3CloudSlam shows what each toggle changes in your processes, and checks your own data for the situations it affects.

Become a founding customerAbout Release Toggle Impact
Release Toggle Impact · October release · your PRDPreview
  • Replenishment deliveries get a priorityExpires April 2027
    Affects youOccurs in 120 of your 124 open replenishment deliveries
  • Changed rounding on purchase order linesExpires April 2027
    Not met by your data on 7 OctoberNo purchase order lines in this situation
  • New check when releasing kits for pickingExpires October 2027
    Can't tell yetDepends on a setting that can't be read yet

Example toggles and figures.

Twice a year, the same race against the expiry date

Around 70 to 80 feature toggles expire in a typical release. Most don’t touch the way you use M3. The work is finding the few that do, in time.

  1. 1 · April or OctoberA release arrivesNew feature toggles, and expiry dates for older ones.
  2. 2 · Until the expiryYou decideWhile a toggle is optional, you choose when to switch the new behaviour on, test it and prepare your users.
  3. 3 · At the expiryIt is on for goodThe new behaviour is on for everyone, and an expired toggle can't be switched off again.

Sound familiar?

  • Reading release notes to guess which toggles matter for you.
  • Retesting everything, because nobody can say what will change.
  • Finding out after the expiry, when the new behaviour can no longer be switched off.

Release Toggle Impact Preview

For every toggle: what it changes, and whether it happens to you

What it changesEach toggle in plain words: which check, default or step behaves differently.
Where it actsThe place in the process flow where the new behaviour starts, and what it leads to further on.
Whether it happens to youA read-only check of your own M3 data for the situations the toggle changes.

Three honest verdicts

Affects youThe situation the toggle changes occurs in your data. You see where, and how often.
Not met by your data on 7 OctoberNo occurrence in your data on that date. The date is part of the answer: your data keeps changing, so check again before the expiry.
Can't tell yetWhen the answer depends on something M3CloudSlam can't read, it says so instead of guessing.
One toggle, worked through
The toggle
Replenishment deliveries get a priority
What changes
New replenishment deliveries carry a priority, so the order in which they are picked changes.
Where
Delivery flow, from creation to released for picking
In your data
120 of your 124 open replenishment deliveries are in this situation
Verdict
Affects you: tell the warehouse before the expiry, and test picking with the new priorities

Example figures.

Your release, from first look to go-live

Release Toggle Impact finds what changes. The rest of M3CloudSlam helps you test it and explain it.

Before the release

While you test

  • PredictorPreviewThe expected outcome for each test, step by step
  • Flow ViewerAvailableThe flow your test should follow

After the release

Coming next Roadmap

Release Verifier

Twice a year, every M3 customer works out by hand what a release changes for them. The verifier turns that into one repeatable loop: affected flows found, tests generated from the knowledge graph and run in your test environment, and a verdict per flow.

Fix AdvisorFor M3 on-premise: what an Infor fix changes in M3's behaviour, and which of your processes it touches, before you apply it.
See the full roadmap →
Release Verifier · verdict per flow
Customer order allocationSafeNo changed path is used here
Replenishment deliveriesChangedDeliveries will carry a priority; picking order changes
Supplier invoice matchingNeeds a decisionAn expiring toggle is still off here

Example verdicts.

Questions about M3 releases

When does Infor release updates for M3 Cloud Edition?+

Twice a year, in April and October. Each release brings new feature toggles and the expiry of older ones.

What is a feature toggle in M3?+

A switch that comes with a release, so you can choose when to adopt new or changed behaviour. Each toggle has an expiry. After that, the new behaviour is standard for everyone.

How many toggles expire in a release?+

Around 70 to 80 in a typical release in recent years. Most of them don't touch the way your company uses M3; the work is finding the ones that do.

Can an expired toggle be switched off again?+

No. Once a toggle expires, its new behaviour is on and stays on. That is why the analysis has to happen before the expiry, not after it.

Does M3CloudSlam change anything in M3?+

No. Release Toggle Impact reads your configuration and data, read-only, through the connection you set up between M3CloudSlam and your M3 environments.

Is Release Toggle Impact available today?+

It is in preview: founding customers use it on their own M3 now, together with our team, while we finish it.

What about M3 on-premise?+

The toggle cycle belongs to M3 Cloud Edition, so Release Toggle Impact is for cloud customers. For on-premise, an analysis of what an Infor fix changes in M3's behaviour is on our roadmap.

Be ready for the April 2027 release

We are onboarding a small group of founding customers. You get the newest features first, a direct line to the team, and founding pricing.

Become a founding customer
  • Preview features firstPredictor, Debugger, Release Toggle Impact and Value Provenance
  • Shape the roadmapYour M3 questions decide what we build next
  • Founding pricing, locked inYour rate stays as the product grows