Workday Integration Workday Integration Inbound EIB

In most of the Workday Integration instances we’ve done before, we took data from Workday and transmitted it to other systems.

That is usually called outbound Workday Integration.

But when we talk about inbound EIB with Workday Integration, we’re doing the opposite.

We are putting data into Workday and doing business right inside the system.

With Workday Integration’s Inbound EIB, you can load, change, or remove data.

You can recruit a lot of people at once, fire a lot of people at once, change phone numbers, change email addresses, or even change legal names.

Using a structured spreadsheet template, Workday Integration makes all of this feasible.

Workday Integration will still process your record correctly even if you just upload one.

Creating Workday Integration Inbound EIB

In the search bar, I type “Create EIB.” The interface looks a lot like the one you see in outbound Workday Integration.

The key difference is that I choose “Inbound” as the type of integration here.

In this case, I want to fire an employee using Workday Integration.

I give the integration a name that makes sense and then move on to the next stage.

When you click OK in Workday Integration, the system automatically produces an Integration ID.

Next, I set up the Get Data phase in Workday Integration.

Here, I choose how to get the file. With Workday Integration, you may get information back in a number of ways, including SFTP and other server-based solutions.

I need to give the server address, directory, authentication method, user ID, and password if I choose SFTP.

But in most manual Workday Integration cases, I utilize “Attach File at Launch.”

This choice lets me upload the spreadsheet file when I start the Workday Integration procedure.

After that, the system scans the associated file and processes the transactions as needed.

Configuring Workday Integration Data Format and Web Service

Choosing the right data type is very important in Workday Integration.

When I wish to change normal Workday data, I usually choose “Web Service as Spreadsheet Template.”

I choose “Custom Object as Spreadsheet Template” if I need to make changes to custom objects in Workday Integration.

After I selected the type of spreadsheet in Workday Integration, I have to pick the right web service activity.

For instance, if I want to fire an employee, I look for the right web service under Workday Integration.

I enter in keywords like “Terminate” and look at the available web service activities, even if I’m not sure of the actual name.

I choose the “Terminate Employee” web service function in Workday Integration for myself.

I carefully look over the choices and pick the one that fits the business procedure.

Workday Integration automatically connects the chosen online service to the stages for transforming and delivering.

When I do the Transform phase in Workday Integration, I normally use the default template model that the web service operation created.

You don’t have to modify anything here because Workday Integration sets it up automatically based on the operation I choose.

The delivery method is automatically set to “Workday Web Service Operation” again in the Deliver step.

Because I choose “Terminate Employee” previously, Workday Integration links everything correctly without any more work.

Executing Transactions and Bulk Processing in Workday Integration

Bulk processing is one of the best things about Workday Integration.

With inbound EIB in Workday Integration, I can conduct all of my business operations in one go.

Workday Integration takes care of all the steps in a business process effortlessly.

For instance, I can use one Workday Integration file to hire several people, fire several people, or change the contact information for hundreds of workers.

Workday Integration uses the same framework to process even one record that I upload.

Workday Integration is quite useful for HR operations because it is so flexible.

I don’t have to update each record by hand anymore; I use Workday Integration to make sure that all the updates are done correctly and consistently throughout the system.

Encryption and Decryption in Workday Integration

When we send sensitive information through Workday Integration, security is always our first priority.

Encryption in Workday Integration changes data that can be read into a format that only authorized users may access.

When Workday Integration gets encrypted data, it employs decryption to turn it back into a readable form as it is being processed.

This makes sure that Workday Integration keeps employee information safe, like their personal information, pay, and identity information.

Encryption is very important when you set up file-based Workday Integration with other systems.

You can protect files while they are being sent by using public and private keys.

Workday Integration makes guarantee that only systems that have permission can decrypt and read the data.

You may make Workday Integration solutions that work and are safe by combining inbound processing with security.

You will feel more confident addressing real-time business situations when you practice these settings directly in Workday Integration.

Workday Integration: Setting Up EIB Inbound

When you select “OK” in the IP inbound configuration, the system makes your EIB inbound integration.

This is the first thing you need to do to get Workday Integration ready to work with data.

After creating the integration, you need to know how to pass data correctly.

Go to the associated actions, choose your template model, and make sure the kind of transformation is set to web service template model.

Then, make a template for a spreadsheet that you may use for your integration.

I suggest utilizing an Excel file instead of XML because it’s easier to use.

Workday Integration: Populating EIB Templates

Making the EIB is just the first step. The hardest part is figuring out which fields and IDs to fill in on your template.

You can precisely map your data for Workday Integration once the Excel sheet is made.

This stage makes sure that the integration works properly and that all employee data moves smoothly.

Workday Integration: Handling Confidential Data

We have to encrypt files every time we send them from Workday Integration to another system.

This includes private information like bank accounts, health information, and birth dates.

Workday Integration encrypts and decrypts data using public-private key pairs.

The file is encrypted at the source with the public key and decrypted at the target with the private key.

For example, when Workday Integration sends data to Concur, the target system gives Workday Integration its public key.

Then, Workday Integration encrypts the file using this key before sending it.

The data can only be decrypted and seen by the target system that has the private key.

This method protects data while it is being sent.

Workday Integration: Implementing Key Management

Key management is very important for encrypting Workday Integration.

A different public-private key pair is needed for each integration.

You can distribute the public key, and Workday Integration uses it to encrypt data.

The target system is the only place where the private key is stored and kept secret.

Workday Integration makes sure that all sensitive employee information is safe, whether it’s moving or not, by following this configuration.

Even if someone gets to the file as it is being sent, they won’t be able to read the data without the private key.

Workday Integration: Data Flow Scenarios

Data goes from Workday Integration to Concur.

The public key encrypts the file on the Workday Integration side.

Concur gets the encrypted file and then uses the secret key to open it.

Both systems can view the data, but anyone who gets in the way of the transmission can’t.

This approach makes sure that Workday Integration keeps data safe while also making it easy for systems to work together.

Every Workday Integration project that deals with sensitive employee data needs to use encryption and key management.

Workday Integration Public and Private Key Setup

Let me show you how we use pairs of public and private keys in Workday Integration.

As Conquer gives Workday a public key, Workday installs it and utilizes it to encrypt files as they are sent.

This makes sure that your data is safe during every transaction.

Workday Integration Encryption Configuration

When you set up encryption in Workday Integration, you’ll see options like text mode, ASCII armored, and integrity check.

The downstream system determines these settings.

To adequately protect your data, you need to make sure your keys work together and set them up correctly in “Encrypt Using.”

Workday Integration Creating Public Keys

You need to put a public key into Workday Integration if someone offers you one.

You do this by making a public key for your PZP. Always include the tenant, such as implementation or sandbox, when you set up the key.

Choose “production” for production. When you’re done, your keys will be ready, and your files will be encrypted while they are being sent.

Workday Integration File Delivery Verification

When the integration runs, you can see the unencrypted file inside, but as soon as it gets to the SFTP server, it is encrypted.

You won’t be able to see the data if you try to download it from SFTP.

This is how Workday Integration protects your data and makes sure it meets encryption standards.