PingOne

Workday attribute mapping

The following table lists the default Workday attributes that can be mapped to PingOne user attributes for user provisioning.

Attribute Description

Work Email

The user’s email address.

Username

The user’s username and Workday sign-on.

Active

The status of the user account in Workday.

First Name

The user’s first (given) name.

Middle Name

The user’s middle name.

Last Name

The user’s last (family) name.

For inbound provisioning from Workday, LDAP gateway, and SCIM identity stores, you can specify some additional options for onboarding new users. Learn more in Adding attribute mapping for inbound provisioning.

The following is an example of how to get user details by SOAP call:

Endpoint:

https://{{workday_host}}/ccx/service/{{tenant}}/Human_Resources/v36.0

XML Request Body:

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
                  xmlns:bsvc="urn:com.workday/bsvc"
                  xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">

<soapenv:Header>
  <wsse:Security soapenv:mustUnderstand="1">
   <wsse:UsernameToken>
     <wsse:Username>{{username}}@{{tenant}}</wsse:Username>
      <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">
         {{password}}
       </wsse:Password>
     </wsse:UsernameToken>
  </wsse:Security>
 </soapenv:Header>
 <soapenv:Body>
   <bsvc:Get_Workers_Request>
     <bsvc:Request_References bsvc:Skip_Non_Existing_Instances="true">
       <bsvc:Worker_Reference>
         <bsvc:ID bsvc:type="WID">{{worker_id}}</bsvc:ID>
       </bsvc:Worker_Reference>
     </bsvc:Request_References>
     <bsvc:Response_Group>
       <bsvc:Include_Personal_Information>true</bsvc:Include_Personal_Information>
       <bsvc:Include_Employment_Information>true</bsvc:Include_Employment_Information>
       <bsvc:Include_Organizations>true</bsvc:Include_Organizations>
       <bsvc:Include_Management_Chain_Data>true</bsvc:Include_Management_Chain_Data>
       <bsvc:Include_Employee_Contract_Data>true</bsvc:Include_Employee_Contract_Data>
       <bsvc:Include_User_Account>true</bsvc:Include_User_Account>
     </bsvc:Response_Group>
   </bsvc:Get_Workers_Request>
  </soapenv:Body>
</soapenv:Envelope>

Replace the variables with the following values:

  • {{username}}: Integration System User

  • {{workday_host}}: Workday host

  • {{tenant}}: Workday tenant (for example, ping_pt1)

  • {{password}}: Your Workday user’s password

  • {{worker_id}}: Workday Worker ID (WID) or Employee ID

Attribute dependencies

When mapping attributes for write-back, some attributes are dependent on other attributes. For example, to configure a Name attribute, you must also map First Name, Middle Name, Last Name, and Name Locale.

The following table shows the dependent attribute groupings.

If you map one attribute in a group for write-back, you must map them all.

Groups Dependents

Name

First Name

Middle Name

Last Name

Name Locale

Home Address

Home Street Address Line One

Home Street Address Line Two

Home Postal Code

Home City

Home Region

Home Country

Home Phone

Home Phone

Home Phone Country

Home Phone Type

Work Address

Work Street Address Line One

Work Street Address Line Two

Work Postal Code

Work City

Work Region

Work Country

Work Phone

Work Phone

Work Phone Country

Work Phone Type

You can map the following attributes independently of one another:

  • WID

  • Work Email

  • Home Email