Integration patterns for workforce data

Four patterns: scheduled extract, real-time API, event-driven notification, and file exchange. The common workforce integrations are identity and access management, payroll where it is separate, benefits providers, learning platforms, badge and physical access, and expense and finance systems. Choosing is simpler than it sounds: latency requirement and volume decide it. Access provisioning wants events, because the gap between somebody joining and somebody having a laptop is measured in hours and everybody notices it. A benefits provider file wants a weekly extract, because nothing about it is urgent and a weekly file is trivially auditable. Do not build an event stream for a consumer that reads it once a week. Now the dimension specific to HR, and it is why this is not the same lesson as its Financials counterpart. Every integration exports personal data. So each one needs a documented purpose, a defined data set, and a security review. And…

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