Additional Configuration Parameters

Boolean attribute to decide whether to perform aggregation depending on the LATEST_WORKER_RECORD calculated field result or not.

Key: (boolean)disableMultipleWorkerRecords

Value: true

If the mentioned key is set to "TRUE", it is required to add the future event maps described below to capture future data while aggregating.

This list contains events from which workers can be hired in Workday and these events will be used while fetching future hiring workers.
For example:

Key: Future_Hire_Events

Values: ["Hire Employee", "Onboarding"]

The additional events can be appended.

Boolean attribute to decide whether to skip future termination events while requesting the future data.

Key: SKIP_FUTURE_TERMINATION_RECORDS

Value: true

This offset is used while getting the past inactive workers through the mentioned past termination event list.

Key: Past_Termination_Offset

Value: Number of days For example, 100

Note
If no offset is provided then the source uses the date 01 Jan 1970.

<entry key="Future_Termination_Events">
  <value>
    <List>
     <String>End Contingent Worker Contract</String>
     <String>Terminate Employee</String>
    </List>
  </value>
</entry>

Key: Future_Termination_Events

Values: ["End Contingent Worker Contract","Terminate Employee"]

The additional events can be appended.

The additional keys to fetch the data based on various events or filters when disableMultipleWorkerRecords is set to true:

The Workday source correctly aggregates the future-terminating worker records when the future date is updated on the Workday managed system.

Used for fetching past inactive workers up to the day of full aggregation. This list contains termination events through which workers were terminated in Workday.

Key: Termination_Events

Values: ["End Contingent Worker Contract","Terminate Employee"]

The list will contain additional attributes to be populated when certain workers are terminating in the future. Four default attributes will be in the list.
For example:

Key: Termination_Attributes

Value: ["TERMINATION_DATE", "LAST_DAY_OF_WORK", "CONTRACT_END_DATE", "PRIMARY_TERMINATION_REASON_REFERENCE"]

For the existing source, the Future_Data_Business_Process (responsible for getting the future data), must be removed and split into the following child entries for accurate results: Future_Hire_Events, Future_Termination_Events.

Note
By default, the above mentioned attributes will be a part of the future Termination Attributes. Additional attributes can be appended in the above list.

(Supported only for Workday 30.1 API version onwards) These APIs would be used by default in all the new workday sources.

To enable contact change the API on the existing sources supporting 30.1 API version, add the following attribute using the Identity Security Cloud REST API:

Key: useChangeContactInfoAPI

Value: true

The new API used to update the contact information has a strict validation on the format of contact used during provisioning. SailPoint recommends to include the country code as a prefix (country code should be in sync with home or work country address) along with the contact number to be provisioned.

When set to true includes the reference descriptors in the response:

<entry key="Include_Reference_Descriptors_In_Response" value="true"/>

The XPATH of the respective attribute must be modified as mentioned in the following example for the COUNTRY attribute:

<entry key="COUNTRY" value="ns1:Worker_Data/ns1:Personal_Data/ns1:Contact_Data/ns1:Address_Data/ns1:Country_Reference/@ns1:Descriptor"/>

Note
Using this flag impacts performance.

To aggregate an account using delta aggregation that has been back dated (for example, account details such as termination date which has been set prior to the last aggregation):

Key: connector_pastEffectiveDateOffset

Value: 30

In the above example, the connector includes account updates up to 30 days old in delta aggregation.

Note
The Workday source does not update the future dated attributes before the correct effective date in delta aggregation. For accounts that have future termination records on the Workday source, delta aggregation does not fail using the Organization_Reference_ID.

The Workday source manages the following change events in delta aggregation for workers having a future termination or conversion event:

• personal details change

• job detail change

The Workday source does not aggregate partial records in delta aggregation if the future worker's data is changed beyond the future offset date.

This list contains events that will be used while performing delta aggregation.

Key: Delta_Aggregation_Events

Value: ["Change Personal Information", "End Additional Job"]

This list can be extended or any event can be removed from the existing events list.

<entry key="Delta_Aggregation_Events"> 
  <value> 
    <List> 
      <String>Hire Employee</String> 
      <String>Onboarding</String> 
      <String>Terminate Employee</String> 
      <String>End Contingent Worker Contract</String> 
      <String>Change Personal Information</String> 
      <String>Contact Information Event</String> 
      <String>Change Job</String> 
      <String>Change Legal Name</String> 
      <String>Change Business Title</String> 
      <String>Add Retiree Status</String> 
      <String>Assign Organization Roles</String> 
      <String>Change Owner</String> 
      <String>Assign Superior</String> 
      <String>EMERGENCY_CONTACT_EVENT</String> 
      <String>Change Organization Assignments for Worker</String> 
      <String>Change Primary Address</String> 
      <String>Contract Contingent Worker</String> 
      <String>Create Change Order from Contingent Worker Contract</String> 
      <String>Create Primary Address</String> 
      <String>Edit Worker Additional Data</String> 
      <String>Maintain Employee Contracts</String> 
      <String>End Additional Job</String> 
      <String>Change Marital Status</String> 
      <String>Move to New Manager</String> 
      <String>Assign Worker</String> 
      <String>Move Workers Staffing</String> 
      <String>Assign Workers</String> 
      <String>New Hire Provisioning</String> 
      <String>Change Preferred Name</String> 
      <String>Request Worker</String> 
      <String>Submit Resignation</String> 
      <String>Transfer Contingent Worker</String> 
      <String>Transfer Employee</String> 
    </List> 
  </value> 
</entry> 

Note
To include or exclude any events in delta aggregation for the existing application, add the Delta _Aggregation_Events entry and modify accordingly.

Used in the provisioning policy to update contact details on a specified date.

The allowed date formats are as follows:

• yyyy-MM-DD

• yyyy-MM-DD+TZ

  Note
  The +TZ represents a positive differential from UTC. For example, 2025-02-15+05:30 would be interpreted as February 12, 2025, in a timezone that is 5 hours and 30 minutes ahead of UTC (e.g., India Standard Time - IST).

• yyyy-MM-DD-TZ

  Note
  The -TZ represents a negative differential from UTC. For example, 2025-02-15-06:00 would be interpreted as February 12, 2025, in a timezone that is 6 hours behind UTC (e.g., Central Standard Time - CST).

• yyyy-MM-DDTHH:mm:ss.msTZ

  Note
  The T serves as a separator between the date and time values, and must be included.

If the Worker is a future hire and the Effective_Date_For_Contact_Update parameter is not provided in the provisioning policy then the connector uses the Worker's hire date as the effective date to update the contact details.

When set to true this enables auto-approval on the contact change business process.

In scenarios where approvals are mandatory and you want to skip them while updating the attributes from the source, you must add the following attribute using the Identity Security Cloud REST API:

Key: autoComplete

Value: true

Default value: true

The Configure_Response_Group map contains the list of attributes that can be customized based on the requirements. It will filter out the non required data from aggregation.

This is used to improve the performance of the Workday source. For more information, refer to Performance Improvement.