Week 1 of 8
The CloudSuite clock, and who owns testing
Welcome to The Sign-Off Table. For the next 8 weeks you will get one practical move a week for testing Infor CloudSuite, whether you are implementing it, moving from on-premises M3, LN or SyteLine, or already live. After that, a weekly roundup of new research, guides and templates.
We start with the calendar. Since April 2023, Infor has delivered multi-tenant feature releases twice a year, in April and October, and kept a monthly maintenance calendar for fixes, security and statutory updates. And Infor’s own implementation guide is plain about testing: the customer owns it.
This week: put Infor’s dates on your calendar and name the owner
- Find the Multi-Tenant Release Deployment Calendar for your region (Customer Experience Hub or Release Center) and copy every feature release and monthly update into your test calendar.
- For each one, note when your test tenant updates and when production does. Do not assume a gap: read it from the calendar.
- Name one person who signs off each update. Put that name in writing before the next release, not after.
- If you are still on-premises, ask Infor in writing for the support status of your exact version. Forum posts are not a support policy.
Number of the week
2 per year
multi-tenant feature releases, in April and October, plus monthly maintenance updates.
Source: Infor CloudSuite system notification (2023), via LGUGUse this week
- Infor On-Premises to CloudSuite Migration Test Plan (Word) →
13 sections: what changes in the cloud, phases, tenants, updates during the project and exit criteria.
- Guide: testing Infor CloudSuite updates →
The release cadence, Release Reports, feature toggles and a regression plan that keeps up.
Next week: you cannot test what you have not listed. We rank your manufacturing processes.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.