Showing posts with label EIB. Show all posts
Showing posts with label EIB. Show all posts

Wednesday, July 20

MIME

 Multipurpose Internet Mail Extensions

MIME is the acronym of Multipurpose Internet Mail Extensions. MIME type is an optional field on your integrations. 

Instead of you defining your extension along with your File name, you may choose among the listed extension types for the output file. This option doesn't change the actual file format. To change the file format you need to select an alternate output format in Get Data or modify your transformation in Transformation Data tabs.



Wednesday, July 6

iloads vs Inbound EIB

iloads vs Inbound EIB


iload's are used during implementation by Workday Partner Companies ( The company that is helping implement Workday for customer).

Inbound EIB's are used post implementation i.e. after Go-Live by Business users or Workday Analysts. (The customer company)

Sunday, April 12

Integrations: EIB - Inbound Validation Only mode

How to Run EIB Inbound in Validation mode


When you want to load some data into Workday, you typically use the EIB Inbound. You know you will use the three phases involved in EIB - Get Data, Transform Data, Deliver Data.

Its always a good approach to run your EIB Inbound integration load with Validation Only Load.

This helps you in identifying the issues so that you can fix it and proceed with the actual load.

Below shown is the screen when you click on Launch/Schedule integration. Here is where you set the Validation Only Load. When you are comfortable with the load validation, in the next launch just make sure that you don't select so that your run will not be a Validation only but an actual load.


Workday EIB Inbound - Validation Mode Setup

Monday, January 27

Integrations: When to use EIB vs Core Connector

The big advantage with Core Connectors is the Change Detection. Which helps in generating the outbound files with the change data / delta data.

Most of the times, the requirement will be to generate the full file for the first time run and later on the change file.

Example: 

Worker demographics data - on Jan 1st 2020. - Send Full File as it is the first time for the vendor. Then here on 1st of every month send the change file. i.e. difference in data from Jan 1st to Feb 1st. It could include new hires, terminations and any other requested data changes for the said duration. It goes on every month. - Best accomplished with Core Connectors.

Through EIB also you could achieve the change detection, however it is not as simple as selecting the parameters during the launch.

Lets say, if the requirement is to send full file as output every time, we use EIB as the integration system.

Tuesday, November 5

Why am I not able to see my Workday Attachment ran through integration?

Document Retention Policy


We need to know what Document Retention Policy is all about, to answer the question.

In Integrations, like EIB, Core Connectors and Studio we have Document Retention Policy. When your Delivery Method is Attachment we will have a Document Retention Policy to set.

At the maximum you can retrieve your workday generated attachment / file with in 6 months based on the # of days you provide in the setup. (Select in between, 1 day to 180 days).

In simple words, how many days should the generated be preserved by workday for you to access.

Core Connector Sample:

Go to Integration System >> Configure Integration Attributes >> (Attribute provider) Integration Document Retention

Core Connector Document retention Policy
















EIB Sample Screenshot:

EIB Document retention Policy






















For example:

Lets Say, your integration was set up with Document Retention Policy of 90 days, and you are trying to retrieve your report/file which got generated 90 days back.

Now on this day when you wanted to retrieve that report, if it is not showing up, that means, as per the setup you can not view greater than 90 days old report.

--
Few may say that, I saw the report few days back attached to the integration, but today it is not showing up, the reason is Document Retention Policy.

Monday, July 22

EIB - Inbound Template Processing Instructions

Processing Instructions


While loading your file for EIB - Inbound, you will see the Processing Instructions Options to choose on your Overview Tab in the excel template.

Sample Hire Employee Template:

Here is the detailing on these BP related processing selection. Most widely used is Automatic Processing which avoids the approval workflow.


Monday, June 17

Workday EIB - Inbound

EIB - Inbound


The Workday Enterprise Interface Builder (EIB) tool provides an easy-to-use graphical and guided interface to define inbound and outbound integrations without requiring any programming. 

There are two types of EIBs - Inbound and Outbound. I encourage you to first read EIB Outbound. Here we will discuss about EIB Inbound.

The Inbound EIB is just like an Outbound EIB but the way of doing is just a mirror-image. When you want to load the data into Workday from different sources then you would use Inbound EIB. Bulk loads can be done through this EIB Inbounds.

Workday generates a default spreadsheet for the most common set of bulk update operations. These operations include mass payroll, time off, benefit adjustments, etc.

We need to download the generated spreadsheet, add data to it, and then use EIB to import it to the system and update all the records. If your data spreadsheet that you have loaded have any issues, it will notify you of any errors in the load process, and will even highlight which data in the input spreadsheet caused the issue.

Here are the three steps / phases involved in creating an Inbound EIB:

Inbound EIB

1. Get Data

Here in Get Data you define how you retrieve the data. This means how you input the data to workday. This Phase is very important as this defines how your transform and delivery phases are going to be, like what defaults it will pass on.

Below are the different formats that Workday accepts : Attach File at Launch, Amazon Simple Storage Service, FTP/SSL, REST URL, SFTP.

It is important to select the Web Service operation as to where exactly you want to load the data within Workday. For example if you are updating personal information or emergency contacts or one-time payments etc.,
Also there are different file types available to use
  • Web Service Spreadsheet Template (Most commonly used), 
  • Custom Object Spreadsheet Template (Used when loading the data for Custom Objects), 
  • Predefined Template (less likely used)

2. Transform

Transform will be like using the default options, as this section depends up on the Get Data file type selection.

Custom Object Transformation - By Default and only option when selected Custom Object Spreadsheet Template in Get Data.
Template Model - By Default and only option when selected Web Service Spreadsheet Template in Get Data.

3. Deliver

Workday Web Service Operation is the default Delivery method for Web Services.
Custom Object is the default Delivery Method for Custom Objects.
Use the defaults and proceed.
---
Once you configure your EIB, its time to generate the spreadsheet template.

Go to Related Actions >> Template Model >> Generate Spreadsheet Template.  -- This will generate the excel sheet for the Web Service that you have selected.

These delivered spreadsheets can also be customized so that you can specifically identify the columns you need, hide irrelevant fields, etc. Use the Edit and View options in the Template model to edit your spreadsheet template. Once you have your data ready in the spreadsheet, you can launch your integration with below navigation.

Go to Related Actions >> Integration >> Launch / Schedule >> Integration Attachment 
Value Type: Specify Value
Value: Create Integration Attachment -- Here you will attach your data spreadsheet


Configuration of a Sample Inbound EIB:


Create EIB Task



Guided Path:


Get Data


Set Web Service Operation in Get data



 Transform


Deliver


Generate Spreadsheet from Template Model


Additional Reads

Sunday, June 16

Workday EIB - Outbound

EIB Outbound


The Workday Enterprise Interface Builder (EIB) tool provides an easy-to-use graphical and guided interface to define inbound and outbound integrations without requiring any programming. 

There are two types of EIBs - Inbound and Outbound. Here we will discuss about EIB Outbound.

Outbound EIBs are used to extract data from the Workday system and send it to external system that could be a third party, vendor, legacy system or just a simple attachment. Mostly they are used to send a file to an external destination via ftp. 

Here are the three steps / phases involved in creating an Outbound EIB:


Outbound EIB


1. Get Data

In "Get Data" Phase, we will identify the data source. In 90% of the cases, this is will be a custom report and it should be an advanced report which acts as Report as a Service (RaaS). 

If you are specifying a Report Data Source, you can choose the format in which the report results can be delivered. 

Below are the different output formats: XML, simplified XML, CSV, JSON, GData, or RSS

You can also use Workday Web Service endpoint as the data source for an EIB.

2. Transform

This is used to transform the data from one format to other. You can either choose from the set of predefined (XSL) transforms, or specify a new one that you will define. The out-of-the-box options include transforms to CSV and Excel formats.This is an optional step if you do not want to transform anything. By default your EIB will produce an XML format.

When you use Custom Report as your Data source, you can make use of the Delivered Transformation or Custom Transformation. And when you use Web Service on the other hand, you will have only one option Custom Transformation.
Like said above, you can use None option if you don't want to transform.

New Custom Report Transformation: This is the delivered one's, it will allow you to use it for the first time, it will automatically create the transformation for your EIB. One you select this option, you will not see this later, It will become Custom Report Transformation.

Custom Report Transformation: Same as above. 

Custom Transformation: This is the custom transformation where you will write a XSLT for your XML and upload the same.

3. Deliver

The output resulting from executing the EIB can either be attached back to your tenant, or alternatively delivered to an external endpoint. 

Supported Delivery Methods are: Workday Attachment, FTP, HTTP/SSL, FTP/SSL, FTP, Email, AS2 

You can configure multiple delivery options for different tenants, For example - for production you may configure PGP Production Key and for non production tenants you may configure PGP non-Production Key. Additionally you can use Workday attachment to be delivered to the local tenant where the EIB is ran.

Configuration of a Sample Outbound EIB:


Create EIB task


Guided Path


Get Data


Transform


Deliver


Additional Reads:

Thursday, June 13

Interview Questions: EIB

Workday EIB Interview Questions


Here is the list of Interview Questions related to EIB - Enterprise Interface Builder Integrations.


What is EIB and what are the types of EIB?

EIB - Enterprise interface builder tool which is used to build simple inbound and outbound Integrations to connect workday with external endpoints.
Types:
      Inbound
     Outbound 

How many steps are involved in creation of an EIB?
3 Steps / Phases
Get Data, Transform, Deliver

What are outbound EIB?
Outbound EIBs are used to export data from workday. We can also send this exported data to any external vendors or legacy systems through different endpoints such as SFTP/FTP etc.
E.g. Send Dependents data to Benefits vendor from workday.

What are Inbound EIB?
Inbound EIB Integration are used to upload data into Workday from external endpoints or from spreadsheets.
E.g. Inserting One Time Payments, Inserting Bonus Data, Update Emergency Contacts 
We can upload data to workday using spreadsheet attachment or external file from SFTP/FTP/EMAIL locations.

What are the main types of Workday Integrations?
          Workday Studio Integration, 
          Enterprise Information Builder (EIB) Integration, 
          Cloud Connect Integration.

How do you choose which tool is best out of three integrations available?
Few things needs to be considered while choosing the integration tool. Here is what you need to identify first in place.
Is the solution already pre-built? Am I connecting to a third-party vendor with a solution already in place? – If yes, most likely you will choose a Core Connector (Packaged Connector).

Does this integration just need to export or import some data into Workday? – If yes, then most likely you need to go with EIBs.

Do I need to execute several rules, and reports to get the data and calculate the results I need? For example: Determining payroll between Exempt and Non-Exempt employees, calculate deductions, etc. – If yes, then most likely you need a Workday Studio Integration.

Can we create an EIB with the help of matrix report?
No, the reason being reports need to be Web Service enabled for creating EIB and Matrix reports can’t be Web Service enabled.

Can we use all advance reports as a data source in EIB?
 No, we cannot use all advance reports in EIB. We can use only those reports which are web service enabled.

Can we use simple reports as a data source in EIB?
No

What are the types of transformation allowed with EIB?
We can use 3 types of transformation with EIB:

Custom report Transformation -This type is inbuilt transformation of EIB and have limited functionality.
Custom transformation - In this we have to attach XSLT with EIB and supports XSLT functionality. So, this has more features than Custom report Transformation. Learn here w3schools
Document Transformation -This is type of connector that we can connect with EIB and will supports all functionality of Document transformation such as XTT and ETV.

What are the limitations of EIB?
Only one data source can be used. And only one destination point can be configured for one tenant. Can’t define output tag in EIB.

What data sources can we choose while creating the EIB outbound?
EIB outbound is to export the data from Workday.
Data Source - Custom report or Web Services or REST URL

What data sources can we choose while creating the EIB Inbound?
EIB Inbound is to Import the data into Workday.
Data Source - Attachment or External file or REST Endpoint

Name some Web services that you have used for inbound EIB Load?
Request One-Time Payment (OTP)
Change Emergency Contacts
Request Compensation Change
Terminations

While performing EIB Inbound load what should we do to avoid get pending actions / Tasks in inbox?
This represents, when you do a load through EIB the underlying BP/task should get complete without going for any approvals. Because your load may be huge , say 10,000 EE bonus data you are loading at that time, there shouldn't be any workflow triggering for approvals. So, while filling the Inbound Spreadsheet template, we need to select “Automatic processing” on first tab. This will skip the BP's

Where can you view Error messages for an EIB?
You can view the EIB run through Integration Events , Process Monitor

Name some input and output types for EIBs?
Input:   SFTP/FTP, REST, or attachment 
Output: SFTP/FTP, HTTP, Email, CSV, JSON, XML, etc

EIB Integration issues with Scenarios and Resolutions


Scenario 1: The EIB does not display in the integration prompt of the Launch/Schedule Integration task.
Resolution: Verify EIB security Configuration. Edit the EIB and resolve any critical errors.

Scenario 2: Non-legible character appears in Microsoft Excel when you open a CSV output file.
Resolution: Before opening the CSV file in Excel, open the CSV in notepad , Then select File>>save as, UTF-8 encoding.

Scenario 3: File name does not include generated date and time variables when the sequence Generator is configured correctly.
Resolution: When launching or scheduling the EIB, Use these settings with the file name launch parameter.
Value type: Determine value at run time
Value: Next sequence for integration File Utility.

Scenario 4: Workday returns the following error message: Root Cause: BadRequestException: Error code: unknown Response: 500: Processing error occurred. No value provided for required [Prompt Name].
Resolution:  Ensure that all required prompts are being populated when the EIB is launched. You may have to edit the scheduler if the EIB was launched from there.

Scenario 5: Workday returns the following error: Transform failed at component: HandleTransform.request.0.XsltTransform. Reason: Output character not available in this encoding
Resolution: 
  1. Open the XSLT transformation file in a text editor.
  2. Find the element <xsl: output>.
  3. Within that element, search for the setting for encoding=.
  4. Often this is set to ISO-8859-1 Change this value to UTF-8.
If the recipient of the EIB cannot accept UTF-8-encoded files, then you must change the source data in Workday.

Additional Reads

Workday EIB Inbound
Workday EIB Outbound
Workday Core Connectors Interview Questions

I will be updating / adding some more questions