You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/app-provisioning/workday-attribute-reference.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -208,13 +208,14 @@ The table below provides a list of other commonly used custom XPATH API expressi
208
208
209
209
To add more attributes to the XPATH table for the benefit of customers implementing this integration, please leave a comment below or directly [contribute](https://docs.microsoft.com/contribute) to the article.
210
210
211
-
|\#| Workday Attribute Name | Workday API version | Workday XPATH API expression |
Copy file name to clipboardExpand all lines: articles/active-directory/saas-apps/workday-inbound-cloud-only-tutorial.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,11 +45,11 @@ This Workday to Azure Active Directory user provisioning solution is ideally sui
45
45
46
46
* Organizations using Office 365 for email
47
47
48
-
## Solution Architecture
48
+
## Solution architecture
49
49
50
50
This section describes the end-to-end user provisioning solution architecture for cloud-only users. There are two related flows:
51
51
52
-
***Authoritative HR Data Flow – from Workday to Azure Active Directory:** In this flow worker events (such as New Hires, Transfers, Terminations) first occur in Workday and then the event data flows into Azure Active Directory. Depending on the event, it may lead to create/update/enable/disable operations in Azure AD.
52
+
***Authoritative HR data flow – from Workday to Azure Active Directory:** In this flow worker events (such as New Hires, Transfers, Terminations) first occur in Workday and then the event data flows into Azure Active Directory. Depending on the event, it may lead to create/update/enable/disable operations in Azure AD.
53
53
***Writeback flow – from on-premises Active Directory to Workday:** Once the account creation is complete in Active Directory, it is synced with Azure AD through Azure AD Connect and information such as email, username and phone number can be written back to Workday.
Copy file name to clipboardExpand all lines: articles/active-directory/saas-apps/workday-inbound-tutorial.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1058,8 +1058,7 @@ To do this change, you must use [Workday Studio](https://community.workday.com/s
1058
1058
7. Set **Operation** to **Get_Workers**
1059
1059
1060
1060
8. Click the small **configure** link below the Request/Response panes to set your Workday credentials. Check **Authentication**, and then enter the user name and password for your Workday integration system account. Be sure to format the user name as name\@tenant, and leave the **WS-Security UsernameToken** option selected.
Copy file name to clipboardExpand all lines: articles/active-directory/saas-apps/workday-writeback-tutorial.md
+34-34Lines changed: 34 additions & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -92,48 +92,48 @@ In this section, you will configure how writeback attributes flow from Azure AD
92
92
93
93
4. Typically you map the Azure AD *userPrincipalName* attribute to Workday *UserID* attribute and map the Azure AD *mail* attribute to the Workday *EmailAddress* attribute.
| WorkphoneLandlineIsPrimary | true/false | Constant or expression mapping whose output is "true" or "false" string value. |
103
-
| WorkphoneLandlineCountryCodeName |[Three-letter ISO 3166-1 country code](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-3)| Constant or expression mapping whose output is a three letter country code. |
104
-
| WorkphoneLandlineCountryCodeNumber |[International country calling code](https://en.wikipedia.org/wiki/List_of_country_calling_codes)| Constant or expression mapping whose output is a valid country code (without the + sign). |
105
-
| WorkphoneLandlineNumber | Full phone number including the area code | Map to *telephoneNumber* attribute. Use regex to remove whitespace, brackets and country code. See example below. |
106
-
| WorkphoneLandlineExtension | Extension number | If *telephoneNumber* contains extension, use regex to extract the value. |
107
-
| WorkphoneMobileIsPrimary | true/false | Constant mapping or expression mapping whose output is "true" or "false" string value |
108
-
| WorkphoneMobileCountryCodeName |[Three-letter ISO 3166-1 country code](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-3)| Constant or expression mapping whose output is a three letter country code. |
109
-
| WorkphoneMobileCountryCodeNumber |[International country calling code](https://en.wikipedia.org/wiki/List_of_country_calling_codes)| Constant or expression mapping whose output is a valid country code (without the + sign). |
110
-
| WorkphoneMobileNumber | Full phone number including the area code | Map to *mobile* attribute. Use regex to remove whitespace, brackets and country code. See example below. |
| WorkphoneLandlineIsPrimary | true/false | Constant or expression mapping whose output is "true" or "false" string value. |
103
+
| WorkphoneLandlineCountryCodeName |[Three-letter ISO 3166-1 country code](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-3)| Constant or expression mapping whose output is a three letter country code. |
104
+
| WorkphoneLandlineCountryCodeNumber |[International country calling code](https://en.wikipedia.org/wiki/List_of_country_calling_codes)| Constant or expression mapping whose output is a valid country code (without the + sign). |
105
+
| WorkphoneLandlineNumber | Full phone number including the area code | Map to *telephoneNumber* attribute. Use regex to remove whitespace, brackets and country code. See example below. |
106
+
| WorkphoneLandlineExtension | Extension number | If *telephoneNumber* contains extension, use regex to extract the value. |
107
+
| WorkphoneMobileIsPrimary | true/false | Constant mapping or expression mapping whose output is "true" or "false" string value |
108
+
| WorkphoneMobileCountryCodeName |[Three-letter ISO 3166-1 country code](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-3)| Constant or expression mapping whose output is a three letter country code. |
109
+
| WorkphoneMobileCountryCodeNumber |[International country calling code](https://en.wikipedia.org/wiki/List_of_country_calling_codes)| Constant or expression mapping whose output is a valid country code (without the + sign). |
110
+
| WorkphoneMobileNumber | Full phone number including the area code | Map to *mobile* attribute. Use regex to remove whitespace, brackets and country code. See example below. |
111
111
112
-
> [!NOTE]
113
-
> When invoking the Change_Work_Contact Workday web service, Azure AD sends the following constant values: <br>
114
-
> ***Communication_Usage_Type_ID** is set to the constant string "WORK" <br>
115
-
> ***Phone_Device_Type_ID** is set to constant string "Mobile" for mobile phone numbers and "Landline" for landline phone numbers. <br>
116
-
>
117
-
> You will encounter writeback failures if your Workday tenant uses different Type_IDs. To prevent such failures, you can use the Workday **Maintain Reference IDs** task and update the Type_IDs to match the values used by Azure AD. <br>
118
-
>
112
+
> [!NOTE]
113
+
> When invoking the Change_Work_Contact Workday web service, Azure AD sends the following constant values: <br>
114
+
> ***Communication_Usage_Type_ID** is set to the constant string "WORK" <br>
115
+
> ***Phone_Device_Type_ID** is set to constant string "Mobile" for mobile phone numbers and "Landline" for landline phone numbers. <br>
116
+
>
117
+
> You will encounter writeback failures if your Workday tenant uses different Type_IDs. To prevent such failures, you can use the Workday **Maintain Reference IDs** task and update the Type_IDs to match the values used by Azure AD. <br>
118
+
>
119
119
120
-
**Reference regex expressions - Example 1**
120
+
**Reference regex expressions - Example 1**
121
121
122
-
Use the below regular expression, if phone number in Azure AD is set using the format required for Self Service Password Reset (SSPR). <br>
123
-
Example: if the phone number value is +1 1112223333 -> then the regex expression will output 1112223333
122
+
Use the below regular expression, if phone number in Azure AD is set using the format required for Self Service Password Reset (SSPR). <br>
123
+
Example: if the phone number value is +1 1112223333 -> then the regex expression will output 1112223333
0 commit comments