From 6fbf35d1de9bb503c18d7978f4c5822e42da0b8c Mon Sep 17 00:00:00 2001 From: sourabh-stackone Date: Fri, 5 Dec 2025 19:41:24 +0530 Subject: [PATCH 1/6] [INT-7705] HRIS Workday Raas T2 Doc --- .../hris/workday-raas.mdx | 43 ++++++++++++++++--- 1 file changed, 38 insertions(+), 5 deletions(-) diff --git a/integration-configuration-concepts/hris/workday-raas.mdx b/integration-configuration-concepts/hris/workday-raas.mdx index 91e01f0..2c8e46c 100644 --- a/integration-configuration-concepts/hris/workday-raas.mdx +++ b/integration-configuration-concepts/hris/workday-raas.mdx @@ -65,9 +65,14 @@ configuring security group permissions, and connecting it through the integratio - Click the `+` icon to add a field. - Select a Business Object (e.g. Worker) in the **Business Object** column. - Choose the specific field (e.g. Employee ID) in the **Field** column. - - Set aliases in **Column Heading Override** and **Column Heading Override XML Alias** to ensure stable field names in API responses. + - Set aliases in **Column Heading Override** to ensure stable field names in API responses. + + + The **Column Heading Override XML Alias** column will appear only after you enable **Enable As Web Service** under the Advanced tab and save the report. You can view this column when you return to edit the report. + + - For employee data, you can include the following fields: + Add following **field's Alias** in your report. The aliases serve as stable identifiers for the API responses but the underlying fields must be properly configured. - Employee_ID - First_Name - Last_Name @@ -83,6 +88,7 @@ configuring security group permissions, and connecting it through the integratio - Termination_Date - Company_Name + Fields and Aliases Settings @@ -96,7 +102,9 @@ configuring security group permissions, and connecting it through the integratio - Enable prompt display by ticking **Display Prompt Values in Subtitle**. Leave other settings at their defaults. + - Tick **Populate Undefined Prompt Defaults** to make prompt default fields visible in the report table. Once `Prompt Defaults` grid is visible, ticked **Populate Undefined Prompt Defaults** field will be unticked again. + - Tick **Display Prompt Values in Subtitle** to enable prompt display. + Prompts Settings @@ -261,11 +269,18 @@ Use the **ISU Username**, **ISU Password**, and **Report URL** to create a conne **Transferring ownership** revokes access from the current owner. After transferring, ensure you reconnect in the StackOne Connector Hub using the new owner’s ISU credentials; otherwise you will encounter the `The task submitted is not authorized` error. + If the current owner is not the ISU you intend to use to connect with StackOne, open the three‑dot menu under _Custom Report_ and select `Transfer Ownership`. Change Report Owner + Enter the new ISU username in `New Owner` and click `OK`. + + + If you cannot find the ISU in the `New Owner` dropdown. You can share the report access without transferring ownership as described in the next **Grant access without transferring ownership**. + + Enter New Owner @@ -300,15 +315,33 @@ Use the **ISU Username**, **ISU Password**, and **Report URL** to create a conne ## Troubleshooting - - - Verify ISU credentials in the StackOne Connector Hub. + + - Verify that the ISU username and password are correct in the StackOne Connector Hub. + - Ensure the credentials have not expired or been changed. + - Confirm the ISU has the necessary security group permissions configured. + + + + - Ensure the ISU has access to the custom report (either as owner or through authorized user sharing). + - Verify the report ownership configuration matches the ISU credentials being used. + - If ownership was recently transferred, reconnect in the StackOne Connector Hub with the new owner's credentials. + + + - Verify the Report URL is correct and reachable. + - Ensure the ISU has access to the report through ownership or authorized user sharing. + - Check that the report is enabled as a web service in Advanced settings. + - Add missing **Domain Security Policy Permissions** as described in the security configuration section. - Activate pending security policy changes after modifications. - Retry the endpoint (fields populate once permissions are effective). + + Even after adding permissions, you may still see null values for some fields. Ensure the specific Domain Security Policy Permissions for those fields are set and that security changes are activated. + + From b07a2461ed2fde940bdf42dd263db970369d0ff9 Mon Sep 17 00:00:00 2001 From: sourabh-stackone Date: Sat, 6 Dec 2025 11:16:22 +0530 Subject: [PATCH 2/6] Update integration-configuration-concepts/hris/workday-raas.mdx Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- integration-configuration-concepts/hris/workday-raas.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/integration-configuration-concepts/hris/workday-raas.mdx b/integration-configuration-concepts/hris/workday-raas.mdx index 2c8e46c..1d1cd5c 100644 --- a/integration-configuration-concepts/hris/workday-raas.mdx +++ b/integration-configuration-concepts/hris/workday-raas.mdx @@ -102,7 +102,7 @@ configuring security group permissions, and connecting it through the integratio - - Tick **Populate Undefined Prompt Defaults** to make prompt default fields visible in the report table. Once `Prompt Defaults` grid is visible, ticked **Populate Undefined Prompt Defaults** field will be unticked again. + - Tick **Populate Undefined Prompt Defaults** to make prompt default fields visible in the report table. Once the `Prompt Defaults` grid is visible, the **Populate Undefined Prompt Defaults** field will be automatically unticked. - Tick **Display Prompt Values in Subtitle** to enable prompt display. From d72a753c5981a72beb83ab4e0cd7d5f5e6b73869 Mon Sep 17 00:00:00 2001 From: sourabh-stackone Date: Sat, 6 Dec 2025 11:16:43 +0530 Subject: [PATCH 3/6] Update integration-configuration-concepts/hris/workday-raas.mdx Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- integration-configuration-concepts/hris/workday-raas.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/integration-configuration-concepts/hris/workday-raas.mdx b/integration-configuration-concepts/hris/workday-raas.mdx index 1d1cd5c..bd43d97 100644 --- a/integration-configuration-concepts/hris/workday-raas.mdx +++ b/integration-configuration-concepts/hris/workday-raas.mdx @@ -278,7 +278,7 @@ Use the **ISU Username**, **ISU Password**, and **Report URL** to create a conne Enter the new ISU username in `New Owner` and click `OK`. - If you cannot find the ISU in the `New Owner` dropdown. You can share the report access without transferring ownership as described in the next **Grant access without transferring ownership**. + If you cannot find the ISU in the `New Owner` dropdown, you can share the report access without transferring ownership as described in the next section **Grant access without transferring ownership**. From 41606b1e74379a94ec8e9b1daacc1b8de25c7deb Mon Sep 17 00:00:00 2001 From: sourabh-stackone Date: Sat, 6 Dec 2025 11:17:00 +0530 Subject: [PATCH 4/6] Update integration-configuration-concepts/hris/workday-raas.mdx Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- integration-configuration-concepts/hris/workday-raas.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/integration-configuration-concepts/hris/workday-raas.mdx b/integration-configuration-concepts/hris/workday-raas.mdx index bd43d97..7e30bdf 100644 --- a/integration-configuration-concepts/hris/workday-raas.mdx +++ b/integration-configuration-concepts/hris/workday-raas.mdx @@ -72,7 +72,7 @@ configuring security group permissions, and connecting it through the integratio - Add following **field's Alias** in your report. The aliases serve as stable identifiers for the API responses but the underlying fields must be properly configured. + Add the following **field aliases** in your report. The aliases serve as stable identifiers for the API responses but the underlying fields must be properly configured. - Employee_ID - First_Name - Last_Name From d09f7f4bbeb05248ce7fcd82bf29c7884b4c4011 Mon Sep 17 00:00:00 2001 From: sourabh-stackone Date: Sat, 6 Dec 2025 11:18:11 +0530 Subject: [PATCH 5/6] Update integration-configuration-concepts/hris/workday-raas.mdx --- integration-configuration-concepts/hris/workday-raas.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/integration-configuration-concepts/hris/workday-raas.mdx b/integration-configuration-concepts/hris/workday-raas.mdx index 7e30bdf..feee233 100644 --- a/integration-configuration-concepts/hris/workday-raas.mdx +++ b/integration-configuration-concepts/hris/workday-raas.mdx @@ -278,7 +278,7 @@ Use the **ISU Username**, **ISU Password**, and **Report URL** to create a conne Enter the new ISU username in `New Owner` and click `OK`. - If you cannot find the ISU in the `New Owner` dropdown, you can share the report access without transferring ownership as described in the next section **Grant access without transferring ownership**. + If you cannot find the ISU in the `New Owner` dropdown, you can share the report access without transferring ownership as described in the next step **Grant access without transferring ownership**. From abb2e0ca7e8c5108d69795ed0505a8a3dbd1caeb Mon Sep 17 00:00:00 2001 From: sourabh-stackone Date: Tue, 9 Dec 2025 12:26:12 +0530 Subject: [PATCH 6/6] Update integration-configuration-concepts/hris/workday-raas.mdx Co-authored-by: yash-stackone --- integration-configuration-concepts/hris/workday-raas.mdx | 3 --- 1 file changed, 3 deletions(-) diff --git a/integration-configuration-concepts/hris/workday-raas.mdx b/integration-configuration-concepts/hris/workday-raas.mdx index feee233..e099c7e 100644 --- a/integration-configuration-concepts/hris/workday-raas.mdx +++ b/integration-configuration-concepts/hris/workday-raas.mdx @@ -337,9 +337,6 @@ Use the **ISU Username**, **ISU Password**, and **Report URL** to create a conne - Add missing **Domain Security Policy Permissions** as described in the security configuration section. - Activate pending security policy changes after modifications. - Retry the endpoint (fields populate once permissions are effective). - - Even after adding permissions, you may still see null values for some fields. Ensure the specific Domain Security Policy Permissions for those fields are set and that security changes are activated. -