The recruiting star, events first

Two facts and five dimensions. The stage-event fact carries every application transition with its real timestamp; the requisition snapshot carries every opening by day. Everything else on this module is a query against these.

RuleStore the transition, not just the state: event rows with real timestamps are what funnels, clocks, and audits are made of.

Neverderive elapsed time from current-state fields. Backdated entries and edited stages rewrite states; the event log keeps what happened.

◆ The tablestwo facts, five dimensions, one handoff.

Two facts, five dimensions. The requisition and calendar serve both facts; the star matches the Core HR design.

Table	Grain	Feeds
fct_application_event	One application entering one stage, with the transition timestamp.	Funnel, time to fill, source.
fct_requisition_day	One open requisition per day. The module's snapshot fact.	Aging, open-count trend, as-of questions.
dim_requisition	The opening: job profile, organization, recruiter, opened and filled dates.	Every report's slicer.
dim_candidate	The person applying, deduplicated across applications.	Funnel and source.
dim_source	Where the application came from, mapped once.	Source of hire.
dim_date	The calendar, shared with every module star.	Trends, windows, and as-of filters.
dim_stage	The stage ladder, ordered, with each tenant's names mapped to it.	Funnel arithmetic.

◆ Where the events come frombusiness process history, extracted once, kept forever.

Stage transitions live in Workday's business process event history, which delivered reports reach only through brittle calculated-field chains. The pipeline extracts them on the extraction pattern, lands them raw, and types them into the event fact. Timestamps are the recorded ones, so a backdated entry is visible as a backdated entry rather than silently bending a duration.

The requisition snapshot follows the same daily-snapshot discipline as headcount history: one row per open requisition per day, so aging and any as-of question read stored history instead of reconstructing it.

◆ The handoffa start becomes a worker, and the numbers keep tying.

When an application reaches started, the event fact carries the worker key, and the person appears in the Core HR star as a hire. That single join is why the quarter's 16 starts here are the same 16 hires on the headcount table, priced by the payroll module. The battery checks the tie on every build. Sample values are illustrative, never client data.

Use case

Problem

Stage timestamps are trapped in business process history, so every recruiting duration and funnel count is rebuilt by hand with different rules.

What we build

A stage-event fact and a daily requisition snapshot in your warehouse, with dimensions shared with the Core HR star.

What you get

One model that answers funnel, clock, source, and aging questions with arithmetic instead of archaeology.

Still mining business process history one report at a time?

We ship the event fact, the snapshot, and the reports on them, in your cloud.

Talk to us

Terms on this page

HR: Human resources. Core HR is the module a start hands off into.
fact: A table of measured rows. Here, stage events and requisition days.
dimension: A table describing things facts point at: requisitions, candidates, sources, stages.
grain: What one row means. The module’s law: one transition, one row.
business process: Workday’s workflow engine, where transition history lives.
snapshot: A dated copy of a state, kept so the past stays queryable.
stage ladder: The ordered list of stages an application can pass through.
handoff: The join from a started application to the worker it became.