Steps: Configure a Pipeline in People Analytics
Security:
Manage: People Analytics
domain in these functional areas:- People Analytics
- Prism Analytics
You can configure a pipeline in People Analytics to:
- Specify which fields Storyteller should analyze for creating stories.
- Filter which populations to analyze.
- Specify how many months of data to analyze.
- Enforce security on the data.
Workday displays the current status of each pipeline on the
Configure People
Analytics
report.Pipeline Status | Description |
|---|---|
Committed | The current pipeline configuration is committed and installed in the People Analytics
application. |
Not Committed | The current pipeline configuration has changed since the last
installation. To commit these changes to the People Analytics application,
select Run Installation . |
Action Required | The pipeline isn't configured correctly to install People Analytics. The pipeline
status might be because:
|
- Access theConfigure People Analyticsreport.
- SelectEditorConfigurefor a pipeline to make changes to that pipeline.
- (Skills pipeline only) On theOpt Instep, selectMatch Score.
- (Employee Sentiment pipeline only) On theQuestion Selectionstep, for each question type, select one or more questions to map.
- For the Skills pipeline, proceed to the Review step.
- (Optional) On thePopulation Filtersstep, add population filters to constrain the data that Workday analyzes using the Storyteller engine.The population filters you define affect all business questions, visualizations, stories, and KPIs in the People Analytics application.
- (Worker pipeline) On thePromptsstep, configure prompts for the source data for this pipeline.
- On theSecuritystep, select how to enforce security in the application.You can:
- Provide unconstrained access. Anyone who has permission to view thePeople Analyticsreport can see all data.
- Constrain access to the data by selecting one of the configured hierarchies from the Field Mapping step:
- Primary hierarchy. When you constrain access using the primary hierarchy, ensure that the Assigned Organization field accurately reflects the current position of the worker or job requisition.
- Secondary hierarchy. When you constrain access using the secondary hierarchy, ensure that the Level 3 field is associated with the worker or job requisition.
For more details, see Steps: Set Up Constrained Security to People Analytics.
Select the same security option for both the worker and hiring pipelines. - On theData Historystep, select how much data to include in the application.
- Reviewall configuration details, and selectFinishto save the changes.
Workday saves the pipeline configuration, but doesn't update the data in the application yet.
Workday changes the pipeline state to
Not Committed
.Configure all pipelines necessary and then select
Run Installation
on
the Configure People Analytics
report.