🪨🔒 Set in Stone? 🦁💙

Click any card to reveal what you can do with it after promotion

🦁 Model First — The Core Rules

In Workday Extend, your Dev tenant is the playground — build, break, rebuild. But once you promote to Implementation, Sandbox, or Production, parts of your model become permanent. This game teaches you which parts survive, which can flex, and which are carved in stone.

🛠️ The Three Buckets

• Add New Only — You can add brand-new BOs, fields, security domains post-promotion. But you cannot REMOVE the existing ones — they're locked.
• Can Change / Remove — Labels, descriptions, and most attributes can flex. These are truly flexible — you can toggle them either direction freely.
• Locked Forever — Field types, removed BOs/fields, and one-way switches like enableReportingFromTarget, enabledForPageSecurity, enabledForOrchestrationSecurity — once enabled, cannot disable.

⚠️ The One-Way Trap (most dangerous!)

Some attributes look like they "can change" — but only in one direction:

false → true ✅ allowed (once)
true → false ❌ never allowed

These behave like locked attributes the moment you flip them. The Workday docs technically say "Allowed Update" — but that's misleading. Treat these as Locked. Examples: enableReportingFromTarget, enabledForPageSecurity, enabledForOrchestrationSecurity.

🎯 The Take-Home

Build with the promotion in mind from day one. Cap your BOs at ~45 fields (not 50) for runway. Be EXTREMELY stingy with index and reporting flags. Your future self will thank you.

"50 is the limit. 47 is the best practice. 45 is the instinct." 🦁💙