10.1 Creating & Launching an Inbound EIB

What an inbound EIB does

The Enterprise Interface Builder (EIB) is Workday's no-code tool for moving data in and out of the tenant. An inbound EIB imports data into Workday.

The critical mental model: an inbound EIB performs the same transactions a user would perform in the interface. It is not a database load. Loading job title changes through an EIB runs the same business processes, the same validations, and the same security checks as a user completing the task by hand. Everything you know about business processes and security applies unchanged.

That has three consequences worth stating up front:

• Business processes fire. A load can trigger hundreds of approval workflows.
• Validations apply. Rows failing a validation condition fail individually.
• Security applies. The account needs the permissions a user performing that transaction would need.

The three parts of an EIB

Every EIB has the same structure:

For a basic spreadsheet-driven inbound EIB, the Get is the attachment you upload and the Deliver is the web service operation.

Building an inbound EIB

Step 1 - Create the integration system

Run the Create EIB task. Name it for what it does and which system or process it serves, so the tenant's integration list stays readable.

Set the direction to Inbound.

Step 2 - Choose the web service operation

This is the decision that determines everything downstream. The web service operation corresponds to the transaction you want to perform - Put_Position, Change_Job, Import_Organization, and so on. The template Workday generates is derived from the operation you select, so choosing the wrong operation produces a template with the wrong columns.

Work backwards from the task. Identify the task a user would run to make this change one record at a time, then find the web service operation corresponding to it. Selecting an operation because its name sounds close to the business requirement is how administrators end up with a template that cannot express what they need.

In the Get Data step, set the retrieval method to Attach File at Launch and the file type to Web Service Spreadsheet template, then select the Workday web service operation. The Transform step then defaults to a template model built from that same operation, and the Deliver step targets the operation that loads the data into Workday.

Step 3 - Generate the spreadsheet template

From the integration system's Related Actions, open the Template Model tab and select Generate Spreadsheet Template. Workday produces a workbook whose columns match the fields of the chosen web service operation, including which fields are required and which are optional.

Step 4 - Populate the template

Fill in the workbook outside Workday. Points that decide whether the load succeeds:

• Use reference IDs, not display names. Workday identifies instances by ID. A cost center's display name may be ambiguous or may change; its reference ID does not.
• Respect required fields. The template marks them; a blank required field fails the row.
• Get effective dates right. Most staffing and organization transactions are effective-dated, and the effective date determines when the change takes effect and which business process definition version applies.
• Do not restructure the workbook. Adding, removing, or reordering columns breaks the mapping between the sheet and the operation.
• Watch data types. Dates and numbers reformatted by a spreadsheet application are a common cause of a whole file failing validation.

Step 5 - Attach and launch

Attach the populated workbook to the integration system and launch the integration. Workday processes the rows and produces an integration event with results.

Step 6 - Review the results

Check the integration event for the outcome and the messages. Rows can fail individually - covered in section 10.3.

Security for an inbound EIB

The EIB runs as the launching user or, when scheduled, as the configured Integration System User.

Because an inbound EIB writes data, the account needs:

• Put permission on the domains securing the data being created or updated - the integration register from section 9.3, not View and Modify.
• Business process participation where the load initiates business processes. If the transaction routes through a business process, the account must be permitted to initiate that business process type on its security policy.
• Access to the EIB itself, secured by integration domains.

The failure that looks like a data problem: every row fails and the messages mention permissions rather than data. The account can authenticate and launch the EIB but lacks Put on the target domain, or lacks initiate permission on the business process the transaction triggers. Diagnose it exactly as in section 4.3 - identify the securable item from the message, run View Security for Securable Item, run View Security Groups for User, close the gap, activate.

Testing an inbound EIB

The stakes are higher than for a report, because an inbound EIB changes data.

1. Test in a nonproduction tenant first. Sandbox holds a copy of Production, so it is a realistic rehearsal.
2. Start with a handful of rows. Two or three records prove the template, the operation, the security, and the business process behavior. A failure at three rows costs nothing; a failure at three thousand may need unwinding record by record.
3. Verify the result in the interface, not only in the integration event. Confirm the change appears on the worker or organization as intended, with the right effective date.
4. Check what business processes fired. A load that silently launched 400 approval events is a problem even when every row succeeded.
5. Scale up in stages, checking results at each stage.
6. Then run in Production - remembering that configuration proven in Sandbox must be rebuilt deliberately, because Sandbox is refreshed from Production.

Ask before every load: what does this trigger? Notifications, approvals, integrations chained to those events, and downstream systems all react. The exam's inbound-EIB scenarios frequently turn on the fact that an EIB is not a quiet back-door write.