Workday Integration EIB Outbound Overview

I use EIB as an integration tool to get data from Workday and make output files.

When I use EIB Outbound to establish a Workday Integration, I always follow three simple steps: Get Data, Transform Data (optional), and Deliver Data.

The system always gets data from either a Custom Report or a Web Service before starting the Workday Integration EIB Outbound procedure.

I always use a Custom Report in Workday Integration because it’s easy to use and works well in most real-time situations.

After Workday Integration gets the data, I can change it if I need to, and then I send the file to the target system.

Workday Integration Custom Report Requirements

I always check my Custom Report before I make a Workday Integration EIB Outbound.

To be accepted by Workday Integration, the report must be an Advanced kind and have Web Service Enabled.

If a report is Web Service Enabled in Workday Integration, it is automatically an Advanced report.

I normally show how to use Workday Integration with a small Advanced Custom Report that has only a few columns.

When you first learn Workday Integration, it can be hard to understand all the calculated fields and columns.

That’s why I do this. But Workday Integration itself isn’t hard. The more fields there are, the harder it gets.

I know that Workday Integration can use my Custom Report as a valid data source once it is Web Service Enabled.

This is a simple yet extremely crucial rule for Workday Integration.

Workday Integration Create EIB Task Process

I use the task “Create EIB” to establish this Workday Integration.

When I start Create EIB in Workday Integration, the system prompts me to give it a name.

I normally use a naming scheme like INT_001_Worker_Details so that I can find the Workday Integration again later.

I choose the Integration Type after giving the Workday Integration a name.

I choose the Outbound option because I am teaching EIB Outbound.

After that, Workday Integration produces an Integration ID on its own.

Every item in Workday Integration has its own ID, which makes it easier to find and fix problems.

After that, Workday Integration wants to know what kind of data source it is.

I can pick between Custom Report and Web Service in EIB Outbound Workday Integration.

I choose Custom Report, like I said before.

When I click on “Custom Report,” the system opens the Custom Report form, and I look for my Web Service Enabled Advanced report.

At this point, Workday Integration knows where to get the data from.

Workday Integration Transformation Step

The Transform phase is not required in Workday Integration.

A lot of newcomers think that every Workday Integration has to involve transformation, but that’s not true.

If the data in my source report is already in the right format, I just choose None in the transformation phase.

But Workday Integration lets me make changes to the file’s structure, format, or layout when I need to.

While I learn the principles of Workday Integration, I keep the transformation step simple and don’t choose a type of transformation.

How to Deliver Workday Integration

Delivery is the last stage in Workday Integration EIB Outbound.

This phase is one of the most crucial sections of Workday Integration since it tells the system where the file that was made will go.

I notice a lot of ways to send things in Workday Integration, like Workday Attachment, SFTP, FTP, FTPS, Email, and even cloud storage.

When I choose Workday Attachment in Workday Integration, the system makes the output file and sends it right to the Integration Event.

Workday Integration doesn’t transfer the file somewhere else in this scenario.

It just puts the file that was made inside the integration event so that you may download it.

When I choose SFTP in Workday Integration, everything change.

Workday Integration still makes the file and stores a copy in the Integration Event.

However, it now also sends the file to the SFTP server that has been set up.

I need to set up the SFTP address, directory path, authentication method, username, and password for this kind of Workday Integration.

I set up SFTP in Workday Integration as if it were a secure storage server.

Workday Integration puts the file it makes on a secure SFTP server, just way you upload files to cloud storage.

The target system then uses credentials to connect to that server and open the file.

Workday Integration also lets you use different ways to log in, like SSH Key and Username/Password.

I set up one or both of them based on the security standards of the company.

Workday Integration even lets you encrypt and decrypt files to make sure they stay safe while they are being sent.

For interviews, delivery choices in Workday Integration are quite significant.

If someone asks me about how to distribute things in Workday Integration EIB Outbound, I make sure to clarify the distinction between Workday Attachment and other delivery methods like SFTP.

This shows me how Workday Integration makes and sends files.

 Workday Integration Document Delivery Options

One of the most essential things I look at when I set up a Workday Integration is the option for document delivery.

You can choose from several distribution options in Workday Integration. By default, the system picks Workday Attachment.

I always make sure my students understand this well because this parameter lets you decide where your integration output really travels.

For example, in a normal Workday Integration situation, I could make an EIB like INT001 to get information on workers.

If I choose Workday Attachment as the delivery option, the Workday Integration makes the file but doesn’t transmit it anyplace else.

The output file stays tied to the integration event in Workday instead. This is the easiest way to offer Workday Integration.

The system makes an integration event every time I perform a Workday Integration with Workday Attachment.

The output file is stored in that integration event. The file doesn’t go to any outside system.

This configuration is helpful when I only want to look at the Workday Integration output inside the company.

Running a Workday Integration and Reviewing the Output

After I make the EIB, I proceed to the Workday Integration’s relevant steps and choose either Launch or Schedule.

When I select Launch, Workday Integration asks me if I want to execute it right away or set it up for later.

I may run the Workday Integration right away, or I can set it to run every day, week, or month.

When I run the Workday Integration, the system can ask me for some settings.

The report I set up as the data source generally gives me these parameters.

In Workday Integration, the values for the prompts come directly from the report configuration.

The Workday Integration processes the input and makes the output file once I enter the parameters.

After the integration event is over, I open it and download the Workday Integration file that was created.

I can access an XML file in either a browser or Notepad++.

The most important thing to know is that the Workday Integration only lets you see the file in Workday when you use Workday Attachment.

Workday Integration Authentication and Authorization

Every Workday Integration needs to have good security.

Workday Integration usually deals with private employee information, payroll information, or personal information.

This is why no SFTP server lets anyone in.

I choose an authentication method, like a username and password, in the Workday Integration settings.

After that, I ask the external system team for the user’s ID and password.

The Workday Integration can’t get in to the SFTP server or put the file in the right folder without these credentials.

The credentials I set up in Workday Integration are only for getting to that server and that folder.

They don’t let everyone see everything. They only let the Workday Integration put files in or take them out of the right directory.

Workday Integration Access to the Target Folder

Let’s say I make a folder on my desktop called SFTP.

Inside that folder, I make a folder called Concur. Inside that folder, I make a folder called Workday Outbound.

The Workday Integration has to be able to access that folder in order to put a file in Workday Outbound.

If someone doesn’t have permission to open that folder, they can’t put a file in it.

The same reasoning holds true for Workday Integration.

The Workday Integration can’t get to the target location unless I set up the right authentication and directory information.

I always check that the server IP, folder path, login, and password are all set up correctly for every Workday Integration.

The Workday Integration can only make and send the file after that.

Workday Integration as a Common Exchange Location

Some individuals think that Workday Integration connects two systems directly.

In fact, Workday Integration commonly uses the same SFTP site as a meeting point.

I prefer to call it a shared exchange point where both systems can get to the data.

I set up Workday Integration to put the outgoing file in a certain SFTP folder as part of a normal Workday Integration between Workday and Concur.

After that, the external system team can access the folder and use the file.

The Workday Integration does not log into the other app directly.

Instead, it puts the file in a safe and controlled place for exchange.

Workday Integration Outbound and Inbound Folder Structure

I often notice two different directories on the SFTP server for Workday Integration projects: one for outgoing files and one for incoming files.

There can be Workday to Concur Outbound and Workday to Concur Inbound, for instance.

When I set up an outbound Workday Integration, I put the file that was made in the outgoing folder.

After that, the SFTP team or an automated process moves the file from the outbound folder to a place that the external system can get to.

This separation maintains the Workday Integration safe and tidy.

For inbound Workday Integration, the external system puts the file in the inbound folder in the same way.

After that, Workday Integration gets the file from that folder and works on it in Workday.

This planned method makes sure that every Workday Integration goes off without a hitch without directly connecting systems.