HR Integrations, Lifecycle Events, and Analytics
Integrations: keep the profile truthful
The HR system of record (Workday, SuccessFactors, or another HCM) owns employee data; ServiceNow consumes it. Integration spokes and flows ingest worker records to create or update HR profiles and users - employee number, department, manager, hire date, termination date, location. Design questions usually probe direction of data flow (HR system → ServiceNow for profile attributes) and idempotency (matching on employee ID rather than name). Inbound email, LDAP/SSO, and Virtual Agent are also integration surfaces.
Lifecycle events
Lifecycle events (onboarding, offboarding, leave, relocation) orchestrate cross-team work from a single trigger tied to the employee's profile - a hire date arriving, a termination date being set - rather than to a catalog request. An event expands into activities: employee tasks (things the person must do, surfaced in their portal to-do list), fulfiller tasks for HR/IT/facilities, and approvals, often sequenced as before/on/after the event date. Journeys present that sequence to the employee.
Analytics
HRSD analytics answers three questions: how much (case volume by service, COE, channel), how fast (average resolution, SLA compliance, backlog aging), and how well (CSAT from post-closure surveys, deflection, reopen rate). Indicators depend on scheduled data collection jobs, so a blank dashboard is usually a collection or date-range problem, not a broken report. Report on case tables for case metrics; use task SLA tables for SLA metrics.
Traps
Expecting a catalog item to launch a lifecycle event (it does not - events fire from profile conditions), and assuming an integration creates a duplicate user instead of matching an existing one. Also expect confusion between a fulfiller task the agent owns and an employee task the new hire must complete.
Rule of thumb
Event = lifecycle moment; activity = who does what, when; analytics = volume, speed, satisfaction.