Data import

Connection details

Parameter	Value
Base URL	{Base URL}
Authentication type	OAuth2 Custom
Token endpoint	[Token endpoint]
OAuth token type	Bearer
Auth request body	grant_type=refresh_token&refresh_token={Refresh token}&client_id={Client id}&client_secret={Client secret}
Auth request content type	application/x-www-form-urlencoded
Authentication server response format	JSON
Access Token Location	access_token
Authorization header	Authorization
Test connection	Select the checkbox

Queries and mappings

Workers - identity

Additional fields can be mapped by adding them directly to the mapping configuration.

Parameters

Tab	Parameter	Value
General	URL	ccx/api/staffing/v6/ibmsrv_pt1/workers
General	Distinct	Yes
General	Enabled	Select the checkbox
Advanced	HTTP verb	GET
Advanced	URL is a DynamicExpresso expression	No
Paging	Change paging	No

In the URL, you can add a query parameter to include or exclude terminated workers:

Include: ccx/api/staffing/v6/ibmsrv_pt1/workers?includeTerminatedWorkers=true
Exclude: ccx/api/staffing/v6/ibmsrv_pt1/workers?includeTerminatedWorkers=false

Mappings

Destination	Operator	Source
Business key	Map	id
Unique ID	Map	id
Name	Map	descriptor
Status	Constant	Active
First name	Expression	descriptor.Split(' ')[0]
Last name	Expression	descriptor.Split(' ')[descriptor.Split(' ').Length - 1]
Email	Map	person_email
Job title	Map	primaryJob_descriptor
Country	Map	primaryJob_location_country_ISO_31661_Alpha3_Code
Employee ID	Map	workerId
Type	Constant	Primary
Category	Constant	Employee

Optional:

• You can set the status to either terminated or active by using the following expression: descriptor.Contains("(Terminated)") ? "Terminated" : "Active".
• You can add extra extensions to retrieve work types and additional jobs:

Destination	Operator	Source
workType	Map	workerType_descriptor
additionalJob	Map	additionalJobs_descriptor

Supervisory Organizations – context

Additional fields can be mapped by adding them directly to the mapping configuration.

Parameters

Tab	Parameter	Value
General	URL	ccx/api/staffing/v6/ibmsrv_pt1/supervisoryOrganizations
General	Distinct	Yes
General	Enabled	Select the checkbox
Advanced	HTTP verb	GET
Advanced	URL is a DynamicExpresso expression	No
Paging	Change paging	No

Mappings

Destination	Operator	Source
Business key	Expression	"SupervisoryOrganization_" + id
Name	Map	descriptor
Type	Constant	OrgUnit
Short name	Expression	"SupervisoryOrganization_" + id

Locations – context

Additional fields can be mapped by adding them directly to the mapping configuration.

Parameters

Tab	Parameter	Value
General	URL	ccx/api/staffing/v6/ibmsrv_pt1/workers
General	Distinct	Yes
General	Enabled	Select the checkbox
Advanced	HTTP verb	GET
Advanced	URL is a DynamicExpresso expression	No
Paging	Change paging	No

Mappings

Destination	Operator	Source
Business key	Expression	"Location_" + primaryJob_location_id
Name	Map	primaryJob_location_descriptor
Type	Constant	Location
Short name	Expression	"Location_" + primaryJob_location_id

Countries – context

Additional fields can be mapped by adding them directly to the mapping configuration.

Parameters

Tab	Parameter	Value
General	URL	ccx/api/staffing/v6/ibmsrv_pt1/workers
General	Distinct	Yes
General	Enabled	Select the checkbox
Advanced	HTTP verb	GET
Advanced	URL is a DynamicExpresso expression	No
Paging	Change paging	No

Mappings

Destination	Operator	Source
Business key	Expression	"Country_" + primaryJob_location_country_ISO_31661_Alpha3_Code
Name	Map	primaryJob_location_country_descriptor
Type	Constant	Countries
Short name	Expression	"Country_" + primaryJob_location_country_ISO_31661_Alpha3_Code

Job title – context

Additional fields can be mapped by adding them directly to the mapping configuration.

Parameters

Tab	Parameter	Value
General	URL	ccx/api/staffing/v6/ibmsrv_pt1/workers
General	Distinct	Yes
General	Enabled	Select the checkbox
Advanced	HTTP verb	GET
Advanced	URL is a DynamicExpresso expression	No
Paging	Change paging	No

Mappings

Destination	Operator	Source
Business key	Expression	"JobTitle_" + primaryJob_id
Name	Map	primaryJob_descriptor
Type	Constant	JobTitle
Short name	Expression	"JobTitle_" + primaryJob_id

Supervisory Organization Assignments for Identities – context assignment

This mapping establishes the relationship between workers and supervisory organizations. It ensures that the worker identity is correctly linked to the supervisory organization within Omada.

Parameters

Tab	Parameter	Value
General	URL	ccx/api/staffing/v6/ibmsrv_pt1/workers
General	Distinct	Yes
General	Enabled	Select the checkbox
Advanced	HTTP verb	GET
Advanced	URL is a DynamicExpresso expression	No
Paging	Change paging	No

Mappings

Destination	Operator	Source
Context business key	Expression	"SupervisoryOrganization_" + primaryJob_supervisoryOrganization_id
Identity UID	Map	id

Location Assignments for Identities – context assignment

This mapping establishes the relationship between workers and locations. It ensures that the location is correctly linked to the corresponding worker identity within Omada.

Parameters

Tab	Parameter	Value
General	URL	ccx/api/staffing/v6/ibmsrv_pt1/workers
General	Distinct	Yes
General	Enabled	Select the checkbox
Advanced	HTTP verb	GET
Advanced	URL is a DynamicExpresso expression	No
Paging	Change paging	No

Mappings

Destination	Operator	Source
Context business key	Expression	"Country_" + primaryJob_location_country_ISO_31661_Alpha3_Code
Identity UID	Map	id

Supervisory Organization managers – context owner

This mapping establishes the relationship between managers and supervisory organizations. It ensures that the manager identity is correctly linked to the supervisory organization within Omada.

Parameters

Tab	Parameter	Value
General	URL	ccx/api/staffing/v6/ibmsrv_pt1/supervisoryOrganizations
General	Distinct	Yes
General	Enabled	Select the checkbox
Advanced	HTTP verb	GET
Advanced	URL is a DynamicExpresso expression	No
Paging	Change paging	No

Mappings

Destination	Operator	Source
Context business key	Expression	"SupervisoryOrganization_" + id
Identity UID	Map	managers_id
Type	Constant	OrgUnit

Job titles assignments for Identities – Context assignment

The following mapping is currently not part of the standard package. You can add it manually. This mapping establishes the relationship between workers and job titles.

1. Open Queries and mappings. Click New.
2. Select Context assignment as the object type for your query.
3. In the General section, enter the following details:
   • URL: ccx/api/staffing/v6/ibmsrv_pt1/workers
   • Distinct: Yes
   • Description: Job titles and workers
4. In Mappings, enter the following details:
   • Context business key (Expression): "JobTitle_" + primaryJob_id
   • Identity UID (Map): id
5. Click OK.

Parameters:

Tab	Parameter	Value
General	URL	ccx/api/staffing/v6/ibmsrv_pt1/workers
General	Distinct	Yes
General	Enabled	Select the checkbox
Advanced	HTTP verb	GET
Advanced	URL is a DynamicExpresso expression	No
Paging	Changing paging	No

Mappings:

Destination	Operator	Source
Context business key	Expression	"JobTitle_" + primaryJob_id
Identity UID	Map	id

Advanced configuration

Parameter	Value
Paging mechanism	URL Parameters
URL parameters	offset={index}&limit=100
Starting index	0
Total field	total

Additional configuration

Perform the following configuration to align Workday's data model with the identity and context structure of Omada Identity. This will ensure correct linking of identities to contextual entities (country/location) that are essential for policies that depend on contextual attributes (for example, location-specific policies). The configuration completes the governance logic.

Modifying the data object type

1. In Omada Identity, go to Setup and then Data object types.
2. In the Name filtering field, enter Countries.
3. Click Properties and then Add.
4. Add two properties with the following System names: OWNERREF and ODWBUSIKEY. Click OK.

Creating context type - countries

1. In Omada Identity, go to Setup and then Context types. Click New.
2. Enter the following details:
   • Name: Countries
   • Object type: Countries
   • Owner property: Owner [OWNERREF]
   • Membership property: Country [COUNTRY]

Import profiles

1. In Omada Identity, go to Setup and then Import profiles.
2. From the list, select Import. Click Start import and wait until the import is completed.

Omada Identity configuration

1. In Omada Identity, go to Setup > All systems, and then select your system.
2. Click one of the following options:
   • (on-premises) Warehouse to portal mapping
   • (cloud) Export queries and mappings
3. Open the first Identities data object type and then click Mappings.
4. Enter the following details:
   • Email: select Map as the operator; search and select Email as Source.
   • EmployeeID: select Map as the operator; search and select EmployeeID as Source.
5. Perform the following procedure for Location and Countries:

Location

1. Enter the following details:

   • Operator: Lookup
   • Source (search source field): ComposedBusinessKey

2. Click Edit. Enter the following details (ensure to change the ContextType to the respective destination you are editing):

   • Target key property: ODWBUSIKEY
   • Lookup view: Context assignments
   • Lookup join field: IdentityComposedBusinessKey (on-premises) or Identity_ComposedBusinessKey (cloud)
   • Lookup value field: ContextComposedBusinessKey (on-premises) or Context_ComposedBusinessKey (cloud)
   • Lookup field: [ContextType]= 'Location' (on-premises) or {context:{type:{eq:"Location"}}} (cloud)

3. Click OK.

Countries

1. Enter the following details:

   • Operator: Lookup
   • Source (search source field): ComposedBusinessKey

2. Click Edit. Enter the following details (ensure to change the ContextType to the respective destination you are editing):

   • Target key property: ODWBUSIKEY
   • Lookup view: Context assignments
   • Lookup join field: IdentityComposedBusinessKey (on-premises) or Identity_ComposedBusinessKey (cloud)
   • Lookup value field: ContextComposedBusinessKey (on-premises) or Context_ComposedBusinessKey (cloud)
   • Lookup field: [ContextType]= 'Countries' (on-premises) or {context:{type:{eq:"Countries"}}} (cloud)

3. Click OK.

Location

1. Enable the two data object types named Location. Open the first one and select the Source tab.
2. In the Additional filtering (SQL) field, change Personal Area to Location (the complete entry: [Type]='Location').

3. Click OK.

Countries

1. In Warehouse to portal mappings, click New. From the list, select Countries. Click OK.

2. Open the new Countries data object type.
3. Under Destination, enter the following details:
   • Operation: Update or create
   • Key property: ISO code
4. Under Source, enter the following details:
   • (on-premises) Warehouse view: Contexts
   • (cloud) Entity type: Context
   • Scope: New and updated objects
   • Action on objects originating from ES: Exclude
5. Under Mappings, enter the following details:
   • Business key: ComposedBusinessKey (Map)
   • ISO code: ShortName (Map)
   • Name: Name (Map)
6. Click OK.

Adding fields in the identity

Perform the following steps to view the location, country, and employeeID of a specific identity after an import (this procedure can be completed after the import and then followed by an additional import).

1. Go to Setup > Identities. Open any identity.
2. Press Ctrl + right click and select Form designer. Click OK.
3. Click Add existing property, and then OK.
4. Select the following fields: Location, Country, and EmployeeID. Click OK.
5. Click Apply.

Event definitions

1. Go to Setup > Event definitions.
2. Search for the event definition: load
3. Open the Create identity user (initial load only) event definition.
4. Select the Disabled checkbox. Click Apply and OK.

---

1. Go to Setup > Event definitions.
2. Search for the event definition: Email
3. Open the Generate Email for Identities event definition.
4. Select the Disabled checkbox. Click Apply and OK.