Skip to main content
Administrator Guide
Last Updated: 2024-09-20
Steps: Configure Application Settings

Steps: Configure Application Settings

Security: Manage: People Analytics domain in these functional areas:
  • People Analytics
  • Prism Analytics
Complete the following steps in the Worker Pipeline:
  1. In the Field Mapping, opt in to the placeholder fields selected as population views (Worker Type or Worker Classification).
  2. Map your source fields into the population view fields
For more information about this, see Configure Pipeline Field Mappings.
The Application Setting card in the Configure People Analytics report provides you the ability to:
  • Enable in People Analytics the fiscal schedule used by your organization
  • Define population views to refine your People Analytics content by.
Fiscal Schedule:
Before choosing a fiscal schedule, ensure that you understand the configurations of the fiscal year, quarter, and month that Workday uses. In People Analytics, fiscal years can only have 12 posting intervals, and you need to manually add every year up to the current point in time in the
Set Up Fiscal Schedules and Years
report. To learn about configuring fiscal schedules to match the data history snapshots for People Analytics, see Steps: Set Up Fiscal Schedules and Years.
Population Views:
Population views enable you to define meaningful worker populations and refine your People Analytics content based on the structure of your organization. Configuring population views is optional and not doing so doesn’t prevent you from running the installation. If you don’t configure population views, you won’t be able to refine your People Analytics content by them. See Concept: Refining in People Analytics.
  1. Access the
    Configure People Analytics
    report.
  2. On the report, open the
    Application Settings
    card.
  3. On the
    Time Configuration
    step, select a predefined Fiscal schedule and define how the report should treat terminations at the end of a fiscal period.
  4. If you want workers terminated on the last day of a period to remain part of the active headcount for the period, check the
    Include Termination on Period End Date
    box. The
    Active Status
    and
    Terminated This Period
    fields will be affected by this selection.
    Example
    : One of your workers was terminated on May 31. If you select this check box, this worker will be considered active for the period of May, and their termination will take effect from June 1, for the purposes of the People Analytics analysis.
  5. In the
    Population Views
    step, select the placeholder fields you’d like to use as population views:
    Field name
    Description
    Default Source Field
    Value Example
    Worker Type
    Specifies the worker type (employee or contingent worker) for a worker. This can be any field.
    Worker Type
    Regular
    Worker Classification
    Additional classification for a worker that is used to differentiate from the worker populations specified in the field Worker Type. This can be any field.
    Pay Rate Type
    Salaried Worker
    If you require your population view to combine different values from one field to form a single population, use calculated fields. For more information about how to create calculated fields, see Create Calculated Fields.
  6. For each population view, use the
    Select Values
    field to list up to 6 accepted values. This enables you to use high cardinality fields (fields that can have more than 6 values) as population views. You’ll be able to refine your People Analytics content by these values.
Workday saves the pipeline configuration, but doesn't update the data in the application. Workday changes the pipeline state to
Not Committed
.
Configure all the pipelines necessary and run the installation in the
Configure People Analytics
report. The
Application Settings
card shows the status of your
Population Views
configuration.
Status
Description
-
Default status. Shows that you’ve never opened the
Population Views
step.
0
You’ve clicked into the
Population Views
step and saved your changes without configuring any population views.
1
1 population view is configured.
2
2 population views are configured.
To review specific population view configuration examples, see: