To launch an employee into Enboarder, the required fields are:

Any extra fields that you wish to include as part of your workflow can be configured using Categories, Custom Fields and Locations.

Workday allows you to leverage business objects and data sources to access report data. Your Workday administrator can create reports to fetch data to use with other systems (such as Enboarder!). In this approach to integration between Workday and Enboarder, your Workday administrator will expose a report as a web service, and then share the endpoint with Enboarder.

To get candidate data in a report, data from the below business objects and modules will be required (it can come from just one of the below three areas). These should be enabled in Workday for this integration:

The below business objects are required to pull candidate data:

Primary object:

Related objects:

Following this activation, below are the high level steps on how this integration approach works:

Launch Candidate Report

Please follow the steps to creating a custom report:

Provide a name to this custom report and set the properties as per below: 

In the 'Additional Info' section, you can add columns and filters based on your requirements:

In addition to your specific requirements that you choose above, below are the mandatory columns that you need to select:

Mapping Managers & Stakeholders via Custom Fields

To map managers and stakeholders with their mobile numbers or emails, Custom fields should be used. The convention to be used for “Immutable Field Key” value of the custom field should be a lowercase stakeholder label defined in Enboarder, with any spaces converted to an underscore: “_”.

For example, if there is a stakeholder in Enboarder called Report To Manager, the value in "Column Heading Override XML Alias" should be report_to_manager.

To define Mobile or Email for this manager user, the key naming convention is the same as the stakeholder label, but suffixed with _mobile or _email e.g.
​

Note: The default "direct manager" is mapped with "manager key".

This means that the stakeholder name must remain as Direct Manager as this has been hardcoded into the Enboarder/Workday integration.

Other examples of stakeholders you may want to include in your journeys and map with the custom fields could also include, Recruiter, Onboarding Specialist, L&D Manager, or anyone else you want to be part of the experience.

Once the report is finalized, you will need to expose it as a web service. Click on 'Actions' > 'Web Service' > 'View URLs' > 'Rest Simple XML'.

Workday may prompt for your administrator credentials here again. Enter the credentials and note down the URL in the browser. This URL is required to integrate with Enboarder.

Note - In end of URL, the query parameter format value is simplexml, please change it to json

The final url will be https://impl.workday.com/ccx/service/customreort/{{_instanceName_}}/{{usrname}}/GeHiredCandidates?format=json

In case you want to more query parameter, you can pass it. Ex- location=Sydney

Update Candidate Report

Please follow the steps to creating a custom report:

Provide a name to this custom report and set the properties as per below: 

In the 'Additional Info' section, you can add columns and filters based on your requirements:

In addition to your specific requirements that you choose above, below are the mandatory columns that you need to select:

Once the report is finalized, you will need to expose it as a web service. Click on 'Actions' > 'Web Service' > 'View URLs' > 'Rest Simple XML'.

Workday may prompt for your administrator credentials here again. Enter the credentials and note down the URL in the browser. This URL is required to integrate with Enboarder.

Note - In end of URL, the query parameter format value is simplexml, please change it to json

The final url will be https://impl.workday.com/ccx/service/customreort/{{_instanceName_}}/{{usrname}}/UpdateCandidates?format=json

In case you want to more query parameter, you can pass it. Ex- location=Sydney

Cancel Candidate Report

Please follow the steps to creating a custom report:

Provide a name to this custom report and set the properties as per below: 

In the 'Additional Info' section, you can add columns and filters based on your requirements:

In addition to your specific requirements that you choose above, below are the mandatory columns that you need to select:

Once the report is finalised, you will need to expose it as a web service. Click on 'Actions' > 'Web Service' > 'View URLs' > 'Rest Simple XML'.

Workday may prompt for your administrator credentials here again. Enter the credentials and note down the URL in the browser. This URL is required to integrate with Enboarder.

Note - In end of URL, the query parameter format value is simplexml, please change it to json

The final url will be https://impl.workday.com/ccx/service/customreort/{{_instanceName_}}/{{usrname}}/CancelCandidates?format=json

In case you want to more query parameter, you can pass it. Ex- location=Sydney

Following the above report creation, you will now need to configure this within Enboarder.

    3. Click on 'Add Integration'

4. Enter the workday report url to pull records. You can add multiple workday reports and define their type on this page. Click on Add Report button. Enter the URL and select the type of report:

Note - To add multiple reports, please click on Add Report button . All reports with type launch will be executed first and then update and last cancel reports by the system.

5. Next add the workday id and password and select the data pull frequency (the interval at which the Enboarder server will report to get new candidates in Workday) and also select Job pull time to specify the time when job should run. Then click on Add Integration button.

6. Enboarder will validate the details and If there is no error, the system will mark the tile Workday as Integrated.

Once this tile is integrated, Enboarder will fetch the data based on your chosen frequency.

Mapping fields from Workday to Enboarder

To ensure that the data from Workday populates the new hire profiles in Enboarder, you will need to ensure that you have setup Categories and/or Custom Fields in Enboarder that have the exact same name as fields from Workday. Once you do this, the fields will automatically be populated in Enboarder with the values fetched from Workday.

For customers who have more than one Enboarder account, it is possible to have the data flow from the source system (Workday) to the parent account in Enboarder, and then be pushed to the child accounts based on criteria sent in the payload.

​Parent-child flow in Workday integration

Set up in Enboarder

We will need a mapping of your child account names and the unique ID of each child account. This ID will be used to find the child's account in Enboarder. The ID can be alphanumeric or string. It should be passed to our system as a string.

Example: A customer has 3 child accounts in Enboarder and they are using the office location city as the child ID (assuming they have only one office per city). They will send us the below data in a CSV file:

Set up in Workday

Add a new field in your Workday report with label subsidiarycompanyid in Column Heading Override XML Alias. The type of this field should be String. The value of this field should be the same as that provided in previous steps to us (E.g Sydney, Brisbane, London)

Any questions on this? Reach out to your Support who will be able to assist you in getting this up and running.