Lab briefing · Extend a page and survive an update

Add a flexfield and a page change in a sandbox, publish, then verify both against the update readiness checklist. The flexfield first, and answer the four questions from Lesson 4 in writing before creating it: who enters it, what validates it, who reports on it, what happens if it is blank. Give it a value set, so it is data rather than a text box. Then the page change in the SAME sandbox: expose the new field, hide something the client does not use, and relabel one thing into their vocabulary. Three changes, one of each kind from Lesson 3. Before publishing, do Lesson 2's three checks — what is in it, does it still apply, has a real user seen it — and publish to a test environment. Then the verification, which is the deliverable. Write the runbook entry: every personalisation, one sentence each describing what the page should…

In this module: Module 12 · Extensions: sandboxes, Page Composer and the boundaries

1. 1What a sandbox is, and what it is notFree preview
2. 2Publishing, and the point of no return
3. 3Page Composer: what it can change
4. 4Descriptive and extensible flexfields
5. 5Value sets and validation
6. 6Application Composer versus Page Composer
7. 7Visual Builder: where it fits
8. 8Recognising an unsupported request
9. 9What breaks: extensions and quarterly updates
10. 10Lab briefing · Extend a page and survive an update