Workflow changes
Approvals and status flows behave differently after an update.
Keep pace with Infor CloudSuite updates
Qventis Core reads Infor CloudSuite screens in plain English, the way planners and finance teams use them. Release Intelligence follows the regular multi-tenant updates and traces each change to your order, supply and finance steps.
- Every regular update covered
- Traced to the process step
- Supply chain to finance
Infor CloudSuite coverageERP
| Area | Modules |
|---|---|
| Supply chain | Order management, Warehousing, Procurement |
| Manufacturing | Planning, Production, Quality |
| Finance | General ledger, Payables, Receivables |
How Infor CloudSuite releases move through Qventis One
- Release rhythm
- Regular multi-tenant updates through the year, often monthly
- What we read
- Release notes and update summaries, Feature lists by product, API and ION integration changes
- Process chains covered
- Order to cash, Procure to pay, Plan to produce, Record to report
- Sign-off
- Go or no-go per environment, by a named person
Release Intelligence reads Infor CloudSuite release content as soon as it is published, so impact is known before your test environment changes.
See Release Intelligence- Screen and workflow changes
- Planning and production logic changes
- Integration changes
- Deprecated features
The App Model maps every change to the modules, process steps and tests it touches, and scores it by transparent rules.
See the App Model- Order changes traced to O2C
- Production changes traced to plan to produce
- Finance changes traced to R2R
- Each impact points to the step's expected result
Qventis Core builds the test delta and runs it on your Infor CloudSuite screens in plain English, on your own runners with no model calls at run time.
See Qventis Core- Impacted, new and retiring tests listed per change
- Blockers and end-to-end chains run first
- Opt-in features tested before you switch them on
- A smoke pass over everything else
Quality View rolls every result up to readiness per environment, with evidence for each check and a named person who signs.
See Quality View- Accept, accept with actions or hold
- Evidence for every check
- Open actions tracked to closure
What we watch in Infor CloudSuite updates
Screen changes
Fields and actions move, and steps written against the old layout need review.
Integrations
Integrations stop posting when a document or field changes.
Your extensions
Extensions on a changed object behave differently.
Questions
Updates come often. Is that a problem?
No. Release Intelligence reads each update as it is published and runs only the test delta.
Do you cover our extensions?
Yes. Customization exposure flags every extension and integration on a changed object.
Bring your next Infor update
Bring one process and your test tenant. We trace the update to your steps and show the go or no-go.