Lab: extend it, then prove the register

An hour, and the first deliverable governs all the others. An extension register, started, with every item below entered. Every one — if you build it, it goes in the register, and that is the discipline being examined rather than the flexfields. Two lookups extended, one code disabled. One descriptive flexfield with a global segment and two contexts on the assignment. One extensible flexfield for repeating qualification data. One value set filtered by a flexfield parameter, demonstrated. Two profile options changed and documented. Design Studio rules for the promote action, differentiated for HR specialist and line manager. And evidence: two logins showing the same action rendering differently. Four acceptance criteria, and two of them decide it. Every extension in the register names a purpose, a consumer and an owner — the three questions from the first lesson, answered per row; an extension with a blank column fails, deliberately, because a…

In this module: Module 15 · Configuration Options and Design Studio

1. 1Extend, do not customize
2. 2Lookups
3. 3Descriptive flexfields
4. 4Extensible flexfields
5. 5Value sets and flexfield parameters
6. 6Profile options
7. 7Transaction Design Studio
8. 8What breaks
9. 9Lab: extend it, then prove the register