Skip to content

Commit b8bf3c0

Browse files
committed
Incorporated review comments
1 parent 7adab80 commit b8bf3c0

File tree

4 files changed

+45
-45
lines changed

4 files changed

+45
-45
lines changed

articles/active-directory/app-provisioning/workday-attribute-reference.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -208,13 +208,14 @@ The table below provides a list of other commonly used custom XPATH API expressi
208208

209209
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.
210210

211-
| \# | Workday Attribute Name | Workday API version | Workday XPATH API expression |
212-
|----|-------------------------|---------------------|--------------------------------|
213-
| 1 | UniversalID | v30.0+ | wd:Worker/wd:Worker_Data/wd:Universal_ID/text() |
214-
| 2 | UserName | v30.0+ | wd:Worker/wd:Worker_Data/wd:User_Account_Data/wd:User_Name/text() |
215-
| 3 | ManagementLevelID | v30.0+ | wd:Worker/wd:Worker_Data/wd:Employment_Data/wd:Worker_Job_Data[@wd:Primary_Job=1]/wd:Position_Data/wd:Job_Profile_Summary_Data/wd:Management_Level_Reference/wd:ID[@wd:type="Management_Level_ID"]/text() |
216-
| 4 | HireRescinded | v30.0+ | wd:Worker/wd:Worker_Data/wd:Employment_Data/wd:Worker_Status_Data/wd:Hire_Rescinded/text() |
217-
| 5 | AssignedProvisioningGroup | v21.1+ | wd:Worker/wd:Worker_Data/wd:Account_Provisioning_Data/wd:Provisioning_Group_Assignment_Data[wd:Status='Assigned']/wd:Provisioning_Group/text() |
211+
> [!div class="mx-tdBreakAll"]
212+
> | \# | Workday Attribute Name | Workday API version | Workday XPATH API expression |
213+
> |----|-------------------------|---------------------|--------------------------------|
214+
> | 1 | Universal ID | v30.0+ | wd:Worker/wd:Worker_Data/wd:Universal_ID/text() |
215+
> | 2 | User Name | v30.0+ | wd:Worker/wd:Worker_Data/wd:User_Account_Data/wd:User_Name/text() |
216+
> | 3 | Management Level ID | v30.0+ | wd:Worker/wd:Worker_Data/wd:Employment_Data/wd:Worker_Job_Data[@wd:Primary_Job=1]/wd:Position_Data/wd:Job_Profile_Summary_Data/wd:Management_Level_Reference/wd:ID[@wd:type="Management_Level_ID"]/text() |
217+
> | 4 | Hire Rescinded | v30.0+ | wd:Worker/wd:Worker_Data/wd:Employment_Data/wd:Worker_Status_Data/wd:Hire_Rescinded/text() |
218+
> | 5 | Assigned Provisioning Group | v21.1+ | wd:Worker/wd:Worker_Data/wd:Account_Provisioning_Data/wd:Provisioning_Group_Assignment_Data[wd:Status='Assigned']/wd:Provisioning_Group/text() |
218219
219220

220221
## Supported XPATH functions

articles/active-directory/saas-apps/workday-inbound-cloud-only-tutorial.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,11 +45,11 @@ This Workday to Azure Active Directory user provisioning solution is ideally sui
4545

4646
* Organizations using Office 365 for email
4747

48-
## Solution Architecture
48+
## Solution architecture
4949

5050
This section describes the end-to-end user provisioning solution architecture for cloud-only users. There are two related flows:
5151

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.
5353
* **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.
5454

5555
![Overview](./media/workday-inbound-tutorial/workday-cloud-only-provisioning.png)

articles/active-directory/saas-apps/workday-inbound-tutorial.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1058,8 +1058,7 @@ To do this change, you must use [Workday Studio](https://community.workday.com/s
10581058
7. Set **Operation** to **Get_Workers**
10591059

10601060
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.
1061-
1062-
![Workday Studio](./media/workday-inbound-tutorial/wdstudio2.png)
1061+
![Workday Studio](./media/workday-inbound-tutorial/wdstudio2.png)
10631062

10641063
9. Select **OK**.
10651064

articles/active-directory/saas-apps/workday-writeback-tutorial.md

Lines changed: 34 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -92,48 +92,48 @@ In this section, you will configure how writeback attributes flow from Azure AD
9292

9393
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.
9494

95-
>[!div class="mx-imgBorder"]
96-
>![Azure portal](./media/workday-inbound-tutorial/workday-writeback-mapping.png)
95+
>[!div class="mx-imgBorder"]
96+
>![Azure portal](./media/workday-inbound-tutorial/workday-writeback-mapping.png)
9797
9898
5. Use the guidance shared below to map phone number attribute values from Azure AD to Workday.
9999

100-
| Workday phone attribute | Expected value | Mapping guidance |
101-
|-------------------------|----------------|------------------|
102-
| 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. |
100+
| Workday phone attribute | Expected value | Mapping guidance |
101+
|-------------------------|----------------|------------------|
102+
| 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. |
111111

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+
>
119119
120-
**Reference regex expressions - Example 1**
120+
**Reference regex expressions - Example 1**
121121

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
124124

125-
```C#
126-
Replace([telephoneNumber], , "\\+(?<isdCode>\\d* )(?<phoneNumber>\\d{10})", , "${phoneNumber}", , )
127-
```
125+
```C#
126+
Replace([telephoneNumber], , "\\+(?<isdCode>\\d* )(?<phoneNumber>\\d{10})", , "${phoneNumber}", , )
127+
```
128128

129-
**Reference regex expressions - Example 2**
129+
**Reference regex expressions - Example 2**
130130

131-
Use the below regular expression, if phone number in Azure AD is set using the format (XXX) XXX-XXXX. <br>
132-
Example: if the phone number value is (111) 222-3333 -> then the regex expression will output 1112223333
131+
Use the below regular expression, if phone number in Azure AD is set using the format (XXX) XXX-XXXX. <br>
132+
Example: if the phone number value is (111) 222-3333 -> then the regex expression will output 1112223333
133133

134-
```C#
135-
Replace([mobile], , "[()\\s-]+", , "", , )
136-
```
134+
```C#
135+
Replace([mobile], , "[()\\s-]+", , "", , )
136+
```
137137

138138
6. To save your mappings, click **Save** at the top of the Attribute-Mapping section.
139139

@@ -154,8 +154,8 @@ Once the Workday provisioning app configurations have been completed, you can tu
154154

155155
5. Once the initial sync is completed, it will write a summary report in the **Provisioning** tab, as shown below.
156156

157-
> [!div class="mx-imgBorder"]
158-
> ![Provisioning progress bar](./media/sap-successfactors-inbound-provisioning/prov-progress-bar-stats.png)
157+
> [!div class="mx-imgBorder"]
158+
> ![Provisioning progress bar](./media/sap-successfactors-inbound-provisioning/prov-progress-bar-stats.png)
159159

160160
## Next steps
161161

0 commit comments

Comments
 (0)