13.3 Enterprise Interface Builder (EIB): Outbound Integrations & Transformations

13.3 Enterprise Interface Builder (EIB): Outbound Integrations & Transformations

Quick Answer: An Outbound Enterprise Interface Builder (EIB) is a configurable point-to-point integration that extracts data from Workday and transmits it to an external endpoint without requiring procedural coding. The outbound architecture consists of three sequential stages: Data Source (typically a custom Advanced Report enabled as a Web Service / RaaS), Transformation (converting Workday XML into CSV, delimited text, or custom formats via XSLT), and Delivery Mechanism (securely transmitting via SFTP, FTPS, HTTP, AS2, or Email, with optional PGP encryption). Dynamic runtime inputs are configured via Integration Launch Parameters, while static connection settings are maintained as Integration Attributes.

---

Enterprise Interface Builder (EIB) Architecture & Core Philosophy

The Enterprise Interface Builder (EIB) is Workday's most widely utilized integration tool. Built directly into the core administrative user interface, the EIB enables business analysts and HCM administrators to configure, deploy, and maintain interfaces using guided tasks.

The Immutable Architectural Boundary

The fundamental design rule of an EIB is: $\text{Exactly 1 Data Source} \longrightarrow \text{Optional Transformation} \longrightarrow \text{Exactly 1 Delivery Destination}$ An EIB cannot query two reports, merge disparate database tables, or deliver different files to three separate vendors in a single definition. Any requirement demanding multiple sources or destinations requires Workday Studio.

+-----------------------------------------------------------------------------------------+
|                             OUTBOUND EIB ARCHITECTURE                                   |
+-----------------------------------------------------------------------------------------+
|  STAGE 1: DATA SOURCE         STAGE 2: TRANSFORMATION         STAGE 3: DELIVERY         |
|  +-----------------------+    +-----------------------+    +-----------------------+   |
|  | Custom Report (RaaS)  |    | None (Raw XML)        |    | SFTP / FTPS / FTP     |   |
|  | - Advanced Report     |--> | CSV / Delimited Text  |--> | HTTP / REST Endpoint  |   |
|  | - Web Service Enabled |    | Custom XSLT (Stylesheet|   | Email Attachment      |   |
|  | Workday Web Service   |    | Document Transform)   |    | Workday Attachment    |   |
|  +-----------------------+    +-----------------------+    +-----------------------+   |
|                                                                 + PGP Encryption       |
+-----------------------------------------------------------------------------------------+

---

Stage 1: Outbound Data Sources

When creating an Outbound EIB via the Create Integration System task (selecting the template Export Process), the first architectural decision is selecting the data source.

1. Custom Report (Report-as-a-Service / RaaS)

The vast majority of Outbound EIBs utilize a Custom Report as their data source:

• Report Type Requirement: Must be an Advanced Report with the Enable as Web Service checkbox enabled on the Advanced tab.
• Business Object Power: Allows the designer to leverage the full power of Report Writer—including multi-level Related Business Object (RBO) navigation, runtime prompts, and complex Calculated Fields.
• Field Aliases: Every column in the custom report must have a clean, valid XML element alias (no spaces or special characters) that becomes the XML tag name in the generated payload.

2. Workday Web Service (WWS)

Alternatively, an Outbound EIB can invoke a delivered Workday Web Service operation (e.g., Get_Workers, Get_Job_Profiles). While comprehensive, web service operations return rigid, deeply nested XML structures that frequently require complex XSLT transformation to parse.

---

Stage 2: Transformations & XSLT Processing

The transformation stage reformats the extracted Workday data into the precise structural schema required by the external recipient.

Transformation Options

1. None (Workday XML): Emits the raw XML payload generated by the data source. Selected when downstream integration platforms (e.g., MuleSoft, Dell Boomi, Informatica) prefer to ingest native XML and perform external parsing.
2. CSV / Delimited Text: Workday natively converts report columns into flat delimited files without custom code:
   • Delimiters: Comma (,), Semicolon (;), Pipe (|), or Tab (\t).
   • Text Qualifiers: Wrap values in double quotes (") or omit qualifiers.
   • Header Formatting: Include or suppress column header labels.
3. Custom Transformation (XSLT): When a vendor demands a specialized format that standard CSV cannot deliver—such as fixed-width positioning, complex XML schemas, or electronic data interchange (EDI) standards—the designer writes and uploads an XSLT (Extensible Stylesheet Language Transformations) file.

<!-- Conceptual XSLT Snippet: Transforming Workday XML to Delimited Text -->
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns:wd="urn:com.workday.report/CR_Active_Workers_Export">
    <xsl:output method="text" encoding="UTF-8"/>
    <xsl:template match="/">
        <!-- Output Header Row -->
        <xsl:text>EmployeeID|LastName|FirstName|JobTitle&#10;</xsl:text>
        <!-- Iterate over each Worker record -->
        <xsl:for-each select="wd:Report_Data/wd:Report_Entry">
            <xsl:value-of select="wd:Worker_ID"/><xsl:text>|</xsl:text>
            <xsl:value-of select="wd:Legal_Last_Name"/><xsl:text>|</xsl:text>
            <xsl:value-of select="wd:Legal_First_Name"/><xsl:text>|</xsl:text>
            <xsl:value-of select="wd:Job_Profile"/>
            <xsl:text>&#10;</xsl:text>
        </xsl:for-each>
    </xsl:template>
</xsl:stylesheet>

Document Transformation (DT) Framework

For advanced formatting requirements on top of an EIB, administrators can attach a Document Transformation integration. Document Transformation provides pre-processing and post-processing steps, including string manipulation, special character replacement, and conditional line suppression.

---

Stage 3: Delivery Mechanisms & Transport Protocols

Once the payload is extracted and transformed, the EIB transmits the resulting document to the external receiver.

Supported Delivery Endpoints

• SFTP (SSH File Transfer Protocol): The enterprise standard for secure batch delivery. Supports Password Authentication or SSH Key Pair Authentication (uploading an SSH Private Key to Workday and sharing the Public Key with the vendor). Allows configuring custom port numbers and directory paths.
• FTPS (FTP over SSL/TLS): Encrypted FTP transport utilizing SSL certificates.
• HTTP / HTTPS / REST: Transmits the output payload via an HTTP POST or PUT request to a remote web service endpoint or API gateway.
• AS2 (Applicability Statement 2): Point-to-point encrypted transmission with digital receipts (MDN), widely utilized in EDI healthcare and supply chain feeds.
• Email: Dispatches the transformed file as an email attachment to designated recipients. Subject to file attachment size limitations and enterprise security policies.
• Workday Attachment: Stores the resulting output file directly inside the Workday tenant, attached to the Integration Event. Users can manually download the file from the event document repository.

Cryptographic Security: PGP / GPG Encryption

Regardless of the delivery protocol, sensitive human resources and payroll files frequently require encryption at rest before network transmission:

• Public Key Encryption: The external vendor provides their PGP Public Key.
• Workday Encryption Engine: The administrator registers the public key via the Create PGP Public Key task. In the EIB delivery settings, the administrator checks Encrypt with PGP and selects the registered key.
• Security Guarantee: Workday encrypts the payload before transmission; only the external vendor holding the matching private key can decrypt and read the file.

---

Integration Attributes vs. Integration Launch Parameters

A critical distinction on the Workday HCM Certification Exam is the operational difference between Integration Attributes and Integration Launch Parameters.

+-----------------------------------------------------------------------------------------+
|                 INTEGRATION ATTRIBUTES vs. INTEGRATION LAUNCH PARAMETERS                |
+-----------------------------------------------------------------------------------------+
|  INTEGRATION ATTRIBUTES (Static Config)        INTEGRATION LAUNCH PARAMETERS (Dynamic)  |
|  - Configured on Integration System definition | - Prompted to user/scheduler at launch |
|  - Environment-specific (Host, User, Path)    | - Run-specific (Dates, Filters, Orgs)  |
|  - Set once during deployment                  | - Supplied every time integration runs |
|  - Example: SFTP Directory Path                | - Example: As-Of Date, Organization    |
+-----------------------------------------------------------------------------------------+

Detailed Architectural Contrast

---

Scheduling & Automated Business Process Launches

Outbound EIBs can be triggered through three execution modes:

1. Manual Execution (Launch / Schedule Integration): An administrator manually initiates the integration, providing launch parameters and executing immediately in the foreground or background.
2. Recurring Automated Schedule: Configured via the Schedule an Integration task. Integrations run on defined frequencies (Daily, Weekly, Monthly, Every N Hours) under the security context of a designated Integration System User.
3. Business Process Integration Step: An outbound EIB can be embedded directly into a Business Process Definition (such as Hire, Change Job, or Terminate) as an Integration Step. When the business process reaches that step, Workday automatically triggers the EIB, extracting data for the specific worker and transmitting it to downstream provisioning systems (e.g., creating an active directory account or ordering a security badge).

---

Certification Pitfalls & Common Exam Traps

1. The Multi-Report EIB Fallacy: Exam questions regularly ask: "An administrator needs to create an Outbound EIB that merges worker compensation from Report A with worker benefit elections from Report B into a single file. How should this be configured?" The answer is that it cannot be done with an EIB. An EIB strictly supports exactly one data source. Merging two reports requires Workday Studio or creating a single comprehensive report using Calculated Fields.
2. Integration Attribute vs. Launch Parameter Confusion: If a question asks where to configure the remote SFTP directory path that differs between the Test tenant and the Production tenant, the correct answer is Integration Attributes. If it asks where an administrator enters the reporting date range for a specific run, the answer is Integration Launch Parameters.
3. XSLT Processing Engine Limits: While Workday supports standard XSLT 1.0, 2.0, and 3.0 transformations, complex procedural Java extensions cannot be invoked within an EIB's XSLT stylesheet. If external Java classes or custom libraries must be executed during transformation, the integration must be architected in Workday Studio.
4. Delivery Failure vs. Extraction Failure: When troubleshooting an integration event in Error status, examine the stage. If the extraction succeeded but the delivery failed (e.g., invalid SFTP host or bad password), the transformed payload is still accessible in the integration event document repository for inspection.