Skip to main content
Documentation
Documentation
Peakon
Last Updated: 2026-04-03
Concept: Worker Eligibility

Concept: Worker Eligibility

Overview

Worker eligibility refers to controlling the employee records that the Workday sync should create in Peakon. You can control worker eligibility by using the
PEAKON_INCLUDED
 custom override. Example: Exclude workers from a newly acquired entity.
The
PEAKON_INCLUDED
 is a calculated field that instructs Workday to sync an employee to Peakon if the value is
True
, or to skip the employee during the sync if the value is
False
.
Administrators must also enable the
Based on custom criteria set in Workday
 checkbox in the Workday integration page in Peakon to ensure this logic is applied.
Note that this calculated field is not the same as the
Eligibility criterion
 field in Workday.

Change in Eligibility Criteria

It’s essential to configure the
PEAKON_INCLUDED
 field correctly, to avoid a change in eligibility criteria not syncing employee updates caused by a gap in the setup.
Change
Worker profile in Peakon
False to True
Depending on the existence of the worker profile in Peakon, the sync will create or update it.
True to False
The worker profile will no longer sync updates, because the integration scope only covers eligible employees. To avoid this from happening, configure the eligibility criteria to cover the broadest possible scope of workers and make manual updates when necessary.

Terminated Workers

When an employee is terminated in Workday, their status transitions from active to inactive. As part of standard system logic, Workday intentionally clears specific attributes from the worker profile because data associated with active employment is deemed no longer relevant. This results in null values for the terminated individual.
To ensure terminated workers retain necessary attribute values for accurate synchronization, you must configure calculated fields. This is a requirement if your integration utilizes
PEAKON_INCLUDED
 logic or custom eligibility fields that reference Workday data cleared upon termination.

Recommendations

  • Set broad eligibility: Configure eligibility criteria to cover the broadest possible scope of workers to prevent manual updates.
  • Identify at-risk fields: Review your integration to identify attributes (Example:
    Department
     or
    Cost Center
    ) or eligibility logic that reference Workday fields cleared at termination.
  • Freeze attribute values: Create calculated fields using
    Lookup Related Value
     or
    Evaluate Expression
     logic to retain the last known value of the attribute prior to the termination event.
  • Update logic: Ensure your
    PEAKON_INCLUDED
     logic or custom eligibility fields point to these new calculated fields rather than standard Workday fields.
  • Test Logic: If you use Workday-delivered
    Class Report Fields
     (CRFs), test them thoroughly, as fields like
    Supervisory Organization
     and
    Employee Type
     do not return values once a termination date has passed.