Building and publishing trees

Create a department tree and a version, add nodes to build a three-level structure, then run audit and watch it fail on a duplicate node, fix it and re-run. Activate and publish. Show the tree consumed by an organization chart. Then create a second version dated for a future reorganisation, and show both coexisting. Audit errors are literal. Read them. The instinct is to skim an error and start guessing, and this particular error tells you the node. The future-dated version is the professional pattern for a known reorganisation, and most people learn it the hard way — by editing the live version on the morning the reorganisation takes effect. And trees used in security profiles must be republished after changes, or visibility silently goes stale. That word again: silently. Nothing errors, and somebody keeps seeing a population they should no longer see.

In this module: Module 5 · Divisions, Departments, Locations and Trees

1. 1Divisions and when you need them
2. 2Departments and cost centers
3. 3Department classifications and reporting establishments
4. 4Locations
5. 5Disability organizations
6. 6Worker unions and collective agreements
7. 7HCM trees
8. 8Building and publishing trees
9. 9What breaks
10. 10Lab: build the management structure