Publishing person and assignment changes

Downstream systems need to know when somebody joins, moves or leaves — directory services, access management, badge systems, payroll, benefits providers, learning platforms. Every one of those holds a copy of part of your workforce data, and every one of them is wrong the moment yours changes and theirs does not. There are mechanisms for communicating changes to consuming applications, covered here at a concept level: the specifics are release-dependent and an integration project in their own right. What triggers a notification and what does not is a common source of surprise. Not every change you would consider significant is treated as one. Find out which are which in your release, early, and test the ones you are depending on — because a change that silently does not publish looks exactly like an integration that is working. The design questions are per consumer rather than per system: which changes matter…

In this module: Module 17 · Connections, Help Desk and Integration

1. 1Connections
2. 2HR Help Desk configuration
3. 3Publishing person and assignment changes
4. 4Integration patterns for workforce data
5. 5What breaks
6. 6Lab: design the joiner-mover-leaver integrations