urity-secext-1.0.xsd"> ISU_Apexion@healthnetwork_gms1 ...

Patricia Chen

``` The SOAP envelope requires WS-Security headers with username token authentication — different from the REST API's bearer token. The namespace is `urn:com.workday/bsvc`. The operation name includes a version number (`v43.0`) that must match the customer's Workday release. The XML nesting depth for a simple name entry is five levels: `Pre-Hire_Data > Personal_Data > Name_Data > Legal_Name_Data > Name_Detail_Data > First_Name`. Ralph constructs the envelope, sends it, and receives a SOAP fault: ```xml SOAP-ENV:Client.validationError Validation error occurred. Invalid subelement Legal_Name_Data for element Name_Data ``` The schema changed in Workday release 2025R2. The `Legal_Name_Data` element was renamed to `Legal_Name` in the Staffing service. The customer's tenant is on 2025R2, but the WSDL Ralph downloaded was from Workday's public documentation, which defaults to the latest version. The WSDL URL is tenant-specific: `https://wd5-impl-services1.workday.com/ccx/service/healthnetwork_gms1/Staffing/v43.0?wsdl`. Ralph downloads the correct WSDL — a 2.4 MB XML file with 847 type definitions for the Staffing service alone. The Staffing service is one of approximately 40 SOAP services. Each has its own WSDL, its own type definitions, and its own version. The Human Resources WSDL is 3.1 MB. The Payroll WSDL is 1.8 MB. Ralph is parsing 7+ MB of XML schema definitions to construct API calls. ## The Tenant-Specific Reality Ralph asks the operations director about custom fields. Workday calls them **custom objects** and **calculated fields**. The healthcare network has 23 custom objects — `Nurse_Credential_Type`, `Shift_Preference`, `Facility_Assignment`, `License_Expiry_Tracker`, among others. These objects are defined in the Workday tenant configuration. They do not appear in the standard WSDL. They are accessible only through RaaS reports or Workday's custom object API endpoints — which require additional domain security policies that the ISU does not have. The `Nurse_Credential_Type` custom object tracks whether a nurse has an active RN license, BLS certification, and state-specific credentials. This is the core data Vanessa needs — it determines whether a contract nurse can be placed at a facility. The data exists in Workday. It is visible in the GUI. It is not accessible through the standard REST or SOAP APIs without a custom RaaS report built by a Workday administrator. The administrator builds the report in the Workday GUI: Report Writer > Create Custom Report > add fields > configure sharing > deploy as web service. The report takes 45 minutes to build and test. The report URL is: `/ccx/wd-report/healthnetwork_gms1/ISU_Apexion/CR_Nurse_Credentials`. But the report returns XML by default. To get JSON, Ralph must append `?format=json` — a parameter not mentioned in the report's deployment settings. Every Workday tenant is different. The standard APIs cover generic HR concepts. The business-specific data — credential tracking, shift scheduling, facility assignments, custom approval workflows — lives in tenant-specific custom objects that require GUI configuration to expose. ## Vanessa Cancels the Partner Call Vanessa fi