MSAMM
Back to course

Implementing Global HR: From Enterprise Model to Live Workforce · Module 15 · Configuration Options and Design Studio

What breaks

Lesson 151 of 175 · 2 min

Seven cases, and one of them is the reason the module opens with a governance argument. One. "The flexfield does not appear." Not deployed. Check this first, always — it costs five seconds and it is the answer most of the time. Two. "There are ninety fields on the person page." Five years of unregistered flexfields; prevention is the register, and there is no cure, because you cannot safely remove a field nobody can account for — which is precisely why they accumulate. Three. "Old records show blank values." A lookup code deleted instead of disabled. Four. "The Design Studio rule is not applying." Not activated, or a conflicting rule with higher precedence — two causes, and the second is why the rules should be few. Five. "The dropdown shows values from all countries." The value set is not filtered by parameter, which is the difference between a field that

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Implementing Global HR: From Enterprise Model to Live Workforce, with a certificate on completion and a fourteen-day refund window.

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

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