Week 3 of 8
Tenants and the refresh calendar
On multi-tenant CloudSuite you do not own servers; you own tenants. Production plus a set of non-production tenants, often named TST and TRN, as your contract defines. Refreshing a test tenant from production is how you get realistic data, and it is a test event in its own right.
Infor’s documentation is direct about the limits. Through the Self-Service Portal you can schedule one refresh per calendar month per target suite, the refresh replaces all data in the target, and it may not be reversible. On LN, security settings on the target are deleted and extensions are overwritten.
This week: write the tenant plan and the refresh checklist
- List every tenant you have, what it is for, who may request a refresh and how often. Confirm the list against your contract.
- Book refreshes a month ahead, aligned to SIT cycles and to the April and October regression windows.
- Before each refresh: back up identity settings and extensions, and block automatic activities so the test tenant cannot email invoices or call real partners.
- After each refresh: restore roles, repoint ION connections to test partners, re-apply extensions and run a smoke suite before anyone tests.
Number of the week
1 per month
refreshes you can schedule per target CloudSuite through the Self-Service Portal.
Source: Infor documentation, Refreshing a CloudSuiteUse this week
- Infor CloudSuite Update Regression Plan →
Includes a 12-step tenant refresh checklist built from Infor’s own refresh documentation.
- Test Schedule & Cycle Calendar →
Put refreshes, cycles and Infor’s update dates on one calendar.
Next week: ION. Every BOD flow needs an owner, a partner contact and an error test.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.