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.

Packaged Connectors - Special Character Translations

Perform Character Translation

There are chances where your end-point would not be expecting any special characters in the output file that you send to them. When you are working on a Packaged Connector / Core Connector look out for the Integration attribute - Perform Character Translation, and check the check box, which will automatically take care of the translations in your file.

Any of the below special characters you may typically see from Name or an Address field.

Special Characters: 'àâäèéêëîïôœùûüÿÀÁÂÄÈÉÊËÎÏÔŒÙÛÜŸçÇáéíóúÁÉÍÓÚäöüÄÖÜßàèéìòóùÀÈÉÌÒÓÙáéíóúüÁÉÍÓÚÜñÑ¿¡
Translated Characters: aaaeeeeiioeuuuYAAAAEEEEIIOEUUUYCCaeiouAEIOUaouAOUBaeeioouAEEIOOUaeiouuAEIOUUnN?1

Navigation: Go to your Integration >> Related Actions >> Integration System >> Configure Integration Attributes

How to Test your Workday Integration Connection / Delivery Method?

Test Transport

Its always a good practice to test your transport (Delivery) before Launching the integration, this way you know whether your credentials say SFTP / FTP related are working fine or not. This can be for any type of integrations. 

If there is any challenges in the details that you had setup in the delivery method of your integrations you can always reconfirm with your end-point and fix it.

Here is an example of one Integration System as how to navigate and test.

Navigation: Go to your Integration System >> Related Actions >> Integration >> Test Transport

Pick up the required action that you want to perform during the test. Here you can see the selection Connect.

Once you click OK in above screen it tests the delivery method and gives you the response, it could be Completed or it may error if it could not connect.

Tip - Re Launch EIB or Core Connector or Studio Integration

Re-Launch Integration Event

While you launch your integration depending on the type say it EIB or a Core Connector, many a times you may need to provide the required / optional Launch Parameters. For one time it will be fine but during the testing you may want to repeatedly run your Integration with same or a different parameters. In that cases, instead of just launching the integration you may use the Relaunch Integration Event. 

This will populate the same integration event related parameters which you used in the last run. According to your need, you may change and quickly launch it.

So make use of Relaunch Integration to launch your integration to auto fill your launch parameters.

Access the task Integration Events and key in your integration name and hit enter to see the below screen. Go to the Integration Event related actions and then Relaunch Integration Event task. This will take you to the next screen.

Below shows the example of a Core Connector.

On this screen below, you can edit your launch Parameters according to your current need and Launch.

Integration Common Issues in PROD

 Integration Common Issues in Production

Here are some of the common Issues related to files that you would encounter while supporting any type of integrations in Production. 

For example, an ongoing EIB Outbound integration, you would typically see issues like below:

File Empty:

The file that was sent to the end point is empty where as they were expecting some data in the file. You need to check your Data Source and specially parameters / filters on your integration event. Which parameters were passed during the launch of integration. Check for the data parameters, and try to run your report by passing the same parameters and see if you fetch any rows.

File Not Received:

In the above case, the file was sent but if was empty. Here, the file was not received at the end point. This is most probably something to do with your Delivery method. Check if the SFTP / FTP passwords got changed or any address / directory got changed so that you can update it and relaunch the integration.

File Has Incorrect Data:

In this scenario, the file was sent and the data in the file was not as expected. It could be of two scenarios 

1. More rows than expected 

2. Less rows than expected.

Its not always the fault on our side, there are times when your end point had a different understanding. So it is important to analyze the data as what was sent vs what is expected. You need to know your data source or web service and filters, sub filters properly. 

Example: If your file is missing some employees, you can ask for the sample Employees who are being missed and try to analyze what is causing that employees to miss in the output file. Same goes with the additional employees in the file.

Integrations: XML to XSL Coding - Sample 2

XML to XSL Sample Coding - Having reference ID's

Here is another sample coding of xml to xsl. This highlights as how to handle some fields having reference ID related information especially you see this in Workday XML vs Simple XML.

Notice the highlighted Workday XML code for the field Gender. If you compare with other fields like Age or Employee_ID , this field (Gender) is showing up additional information like wd:type and so on. Understand that this is nothing but the object related information. Read this to understand more about reference ID's Reference ID's Explained

Workday XML Sample:

<?xml version="1.0" encoding="UTF-8"?>

<wd:Report_Data xmlns:wd="urn:com.workday.report/WD_Sample_Report">

  <wd:Report_Entry>

    <wd:Employee_ID>1234</wd:Employee_ID>

    <wd:firstName>Steve</wd:firstName>

    <wd:lastName>Morgan</wd:lastName>

<wd:Gender wd:Descriptor="Male">

<wd:ID wd:type="WID">98juht8074e54970962128e1105a</wd:ID>

<wd:ID wd:type="Gender_Code">Male</wd:ID>

</wd:Gender>

    <wd:Age>56</wd:Age>

  </wd:Report_Entry>

  <wd:Report_Entry>

    <wd:Employee_ID>1235</wd:Employee_ID>

    <wd:firstName>Logan</wd:firstName>

    <wd:lastName>McNeil</wd:lastName>

<wd:Gender wd:Descriptor="Female">

<wd:ID wd:type="WID">d3afbf8074e549709sdf362128e1</wd:ID>

<wd:ID wd:type="Gender_Code">Female</wd:ID>

</wd:Gender>

    <wd:Age>40</wd:Age>

  </wd:Report_Entry>

  <wd:Report_Entry>

    <wd:Employee_ID>1236</wd:Employee_ID>

    <wd:firstName>Joy</wd:firstName>

    <wd:lastName>Banks</wd:lastName>

<wd:Gender wd:Descriptor="Male">

<wd:ID wd:type="WID">e35sef8074e54970962128e1105a</wd:ID>

<wd:ID wd:type="Gender_Code">Male</wd:ID>

</wd:Gender>

    <wd:Age>42</wd:Age>

  </wd:Report_Entry>

</wd:Report_Data>

Use the Below highlighted code to access the information which is of type BO.

XSL Sample:

<?xml version="1.0" encoding="UTF-8"?>

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"

   xmlns:wd="urn:com.workday.report/WD_Sample_Report" version="2.0">

<xsl:output method="text" indent="no"/>

<xsl:strip-space elements="*"/>

<xsl:variable name="NEWLINE" select="'&#xa;'"/>

<xsl:variable name="PIPE" select="'|'"/>

<xsl:template match="/">

    <!-- Header Record --> 

    <xsl:text>Employee ID</xsl:text>

        <xsl:value-of select="$PIPE"/>

<xsl:text>First Name</xsl:text>

        <xsl:value-of select="$PIPE"/>

<xsl:text>Last Name</xsl:text>

        <xsl:value-of select="$PIPE"/>

<xsl:text>Gender</xsl:text>

        <xsl:value-of select="$PIPE"/>

<xsl:text>Age</xsl:text>

<xsl:value-of select="$NEWLINE"/> 

<xsl:for-each select="wd:Report_Data/wd:Report_Entry">

    <!-- Detail Record --> 

        <xsl:value-of select="wd:Employee_ID"/>

                <xsl:value-of select="$PIPE"/>

    <xsl:value-of select="wd:firstName"/>

                <xsl:value-of select="$PIPE"/>

    <xsl:value-of select="wd:lastName"/>

        <xsl:value-of select="$PIPE"/>

    <xsl:value-of select="wd:Gender/@wd:Descriptor"/>

        <xsl:value-of select="$PIPE"/>

    <xsl:value-of select="wd:Age"/>

        <xsl:value-of select="$NEWLINE"/>

 </xsl:for-each>

    <!-- Trailer Record --> 

 <xsl:text>End of Records</xsl:text>

 

</xsl:template>

</xsl:stylesheet>

Test

Use XLS Transformer to test the above code.

Result:

Employee ID|First Name|Last Name|Gender|Age 1234|Steve|Morgan|Male|56 1235|Logan|McNeil|Female|40 1236|Joy|Banks|Male|42 End of Records

Additional Reads:

XML to XSL Coding - Sample 1

XSL Coding Tips

Free XSL Transformer Online

Integrations: EIB with Email as Delivery method throws an error

EIB with Email as Delivery method throws an error - Fix

When you set the delivery method as Email for your Outbound and try to save it, it throws an error. To overcome this error, you have two ways, 

1. As demonstrated below with screenshots

2. By using Encryption for your generated file(Ex: PGP )

The Error pops up when you try to configure and save  your Delivery method with Email

Here is the workaround, if you don't want to set any encryption.  Click below with the navigation.

Enterprise Interface >> Toggle Approve Unencrypted Transport

Depending on the security that you have to approve, you can check the Approve checkbox and approve this.

Finally, you will not see the error but an alert to warn you that you are sending an email which could be outside of your company so be cautious about the data. You may consider Encrypting your data and send it.

This scenario is one among the mostly asked interview questions.

Integrations: Integration System User (ISU)

7 Steps to create and Assign ISU to the Integrations

Integration Security Users also popularly known as ISU are used to assign the integration Worker Account. (It is created in majority of the cases for your vendors / third party systems)

Here are the 7 Steps to Create and Assign your ISU's to the Integrations.

1. Create Integration System User (ISU)

2. Create Security Group - Integration System Security Group (ISSG)

3. Assign the Integration System User to Security Group ( ISU --> ISSG )

4. Find out the list of all domains required for the particular template in WD Community 

5. Assign Newly created security group to all the domains (ISSG --> Domains)

6. Activate pending security policy Changes

7. Assign the Integration System User to the Integration - (Related actions > Workday Account > Assign ISU)

Integrations: List of Packaged / Core Connector Templates

Integration Template Catalog

Use this report to see what are the delivered Packaged Connectors and Core Connectors. This report helps you in making out which template you want to use based on the requirement.

Look at the sample, Kronos Employee Extract Template.

Also click on the View Details to see the Integration Services, Attributes and Maps. This let you see these details before you head start with the selected / identified template.

Integrations: Workday xml vs Simple xml

Workday xml vs Simple xml

There is a difference between Workday XML and Simple XML. Let us understand with a generated report.

 Here is the sample report for 3 EEs. 

We are selecting 6 fields. Shown below are the field types.

Employee ID    - Text

Worker             - BO (Single Instance)

First Name        - Text

Gender              - BO (Single Instance)

Marital_status  - BO (Single Instance)

Age                     - Numeric

Navigation to generate XML -  (Make sure firstly your report is a RaaS Report)

Go to Your Report >> Related Actions >> Web Services >> View URL's

When you generate your xml's , Notice below:

In Simple XML all fields are just fields, it do not differentiate where as in Workday XML notice that the WID's and reference id type show up for each instance related fields ( Single Instance / Multi - Instance).

We can say that, when you run the report and see the related actions on any of the column values, then that is likely to give you WID and reference id type.

Simple XML:

<wd:Report_Data xmlns:wd="urn:com.workday.report/pb_Advanced_Report">

<wd:Report_Entry>

<wd:Employee_ID>1234</wd:Employee_ID>

<wd:Worker>Aidan Mitzner</wd:Worker>

<wd:FirstName>Aidan</wd:FirstName>

<wd:Gender>Male</wd:Gender>

<wd:Marital_Status>Single (United States of America)</wd:Marital_Status>

<wd:Age>48</wd:Age>

</wd:Report_Entry>

<wd:Report_Entry>

<wd:Employee_ID>1235</wd:Employee_ID>

<wd:Worker>Wesley Kingston</wd:Worker>

<wd:FirstName>Wesley</wd:FirstName>

<wd:Gender>Male</wd:Gender>

<wd:Marital_Status>Single (United States of America)</wd:Marital_Status>

<wd:Age>31</wd:Age>

</wd:Report_Entry>

<wd:Report_Entry>

<wd:Employee_ID>1236</wd:Employee_ID>

<wd:Worker>Xaviere Francois</wd:Worker>

<wd:FirstName>Xaviere</wd:FirstName>

<wd:Gender>Female</wd:Gender>

<wd:Marital_Status>Free Union (France)</wd:Marital_Status>

<wd:Age>42</wd:Age>

</wd:Report_Entry>

</wd:Report_Data>

Workday XML:

<wd:Report_Data xmlns:wd="urn:com.workday.report/pb_Advanced_Report">

<wd:Report_Entry>

<wd:Employee_ID>1234</wd:Employee_ID>

<wd:Worker wd:Descriptor="Aidan Mitzner">

<wd:ID wd:type="WID">12831f1b82954a3a0ad85fb85367</wd:ID>

<wd:ID wd:type="Employee_ID">1234</wd:ID>

</wd:Worker>

<wd:FirstName>Aidan</wd:FirstName>

<wd:Gender wd:Descriptor="Male">

<wd:ID wd:type="WID">d3afbf8074e54970962128e1105a</wd:ID>

<wd:ID wd:type="Gender_Code">Male</wd:ID>

</wd:Gender>

<wd:Marital_Status wd:Descriptor="Single (United States of America)">

<wd:ID wd:type="WID">5e50cb12452487de0caf7f262d4f</wd:ID>

<wd:ID wd:type="Marital_Status_ID">Single_USA</wd:ID>

</wd:Marital_Status>

<wd:Age>48</wd:Age>

</wd:Report_Entry>

<wd:Report_Entry>

<wd:Employee_ID>1235</wd:Employee_ID>

<wd:Worker wd:Descriptor="Wesley Kingston">

<wd:ID wd:type="WID">480fa11010d6501bfc3dad351f1d</wd:ID>

<wd:ID wd:type="Employee_ID">1235</wd:ID>

</wd:Worker>

<wd:FirstName>Wesley</wd:FirstName>

<wd:Gender wd:Descriptor="Male">

<wd:ID wd:type="WID">bf8074e549ffb070962128e1105a</wd:ID>

<wd:ID wd:type="Gender_Code">Male</wd:ID>

</wd:Gender>

<wd:Marital_Status wd:Descriptor="Single (United States of America)">

<wd:ID wd:type="WID">5e50cb12452487de0caf7f262d4f</wd:ID>

<wd:ID wd:type="Marital_Status_ID">Single_USA</wd:ID>

</wd:Marital_Status>

<wd:Age>31</wd:Age>

</wd:Report_Entry>

<wd:Report_Entry>

<wd:Employee_ID>1236</wd:Employee_ID>

<wd:Worker wd:Descriptor="Xaviere Francois">

<wd:ID wd:type="WID">b31600011066de010d5410b714d0</wd:ID>

<wd:ID wd:type="Employee_ID">1236</wd:ID>

</wd:Worker>

<wd:FirstName>Xaviere</wd:FirstName>

<wd:Gender wd:Descriptor="Female">

<wd:ID wd:type="WID">3bec2d0d420283f76f51b928d885</wd:ID>

<wd:ID wd:type="Gender_Code">Female</wd:ID>

</wd:Gender>

<wd:Marital_Status wd:Descriptor="Free Union (France)">

<wd:ID wd:type="WID">f0f5d5eb405b9ffa48755d4d8b41</wd:ID>

<wd:ID wd:type="Marital_Status_ID">Free_Union_France</wd:ID>

<wd:ID wd:type="Marital_Status_Code" wd:parent_type="WID" wd:parent_id="6971ffb4bf0b116fe7651ec789a">UNIFRA</wd:ID>

</wd:Marital_Status>

<wd:Age>42</wd:Age>

</wd:Report_Entry>

</wd:Report_Data>

Workday: Core Connector Templates

Below are some of the hand picked core connector integration templates that you generally see during work.

Core Connector for HCM -Templates:

Core Connector: Worker

Core Connector: Positions

Core Connector: Locations

Core Connector: Job Requisitions

Directory Service

E-Verify - Employment Verification

Core Connector: Job Profile and Job Family

Core Connector: Organization Inbound

Core Connector: Organization Outbound

Integration - Templates:

Enterprise Interface Builder  (EIB Related)

Cloud Integration Template   (Studio related)

Document Transformation

Cloud Connect for Benefits - Templates:

CIGNA: Medical, Dental, Wellness, FSA

Guardian: Dental, Vision, Insurance

Delta Dental of CA: Dental

Aetna: FSA, HSA, Life, Disability

MetLife: Dental, Vision

HealthPartners: Medical, Dental, Vision, Rx

Cloud Connect for Third Party Payroll - Templates:

Payroll Interface

PI External Results Inbound (Do Not Use)

Import External Payslips

Payroll Effective Change Interface

PECI - Merge Files Integration Template

External Payroll Results Inbound

Worker Effective Change Interface

iLoad- Templates:

iLoad Bulk: Process Input File Template

iLoad Bulk: Doc Splitter

Access the report - Integration Template Catalog to view all the integration templates that Workday is offering.

Related Terms & Glossary: Integrations

Related Terms & Glossary: Integrations

Integration System

A tenanted definition of an integration between Workday and an external system based on a template that provides the methodology for communicating data.

Reference ID

A unique identifier used to look up data for integration purposes.

System User

An account associated with and required to launch a Connector or Studio integration. Workday delivered integrations and custom integrations require a system user account for authentication and web service calls. A system user account is not associated with a person in Workday.

Integration Template

A collection of integration services that enables communication between Workday and an external system. Workday provides integration templates in categories such as Benefits, Financials, HCM, Payroll, Payroll Interface, Procurement, Recruiting, Security, and Settlement. Many of the delivered templates contain default values for attributes, as well as prompt values for attributes and maps, to define the integration further.

Integration Event

The record of an integration process. Every integration—current or past, involving the import or export of data, successful or not—gets recorded as an integration event. The integration event contains all the information about the integration process, including its status.

Connector

A set of  one or more integration templates that provide a framework for building integrations in a particular functional area. The integration can support a specific type of data, or can support a specific endpoint ( vendor, legacy system, third party payroll )

Enterprise Interface Builder (EIB)

An integration tool that enables you to create simple, secure, and customizable integrations with Workday. Alternately, an EIB is a simple integration created by the integration tool. An EIB consists of an integration system, an integration data source, an integration transformation, and an integration transport protocol.

Integration Field Overrides

A service that lets you customize integration systems that are based on a connector template. Field overrides are managed through an integration service. They use calculated fields or report fields to supply values to an integration system. Example: member IDs in benefit provider integrations.

Integration Attribute

An integration component that specifies the tenanted value of a data element in Workday. Example: Master Policy Number is a type of attribute in benefit provider integrations.

Integration Data Source

Indicates the type of data that Workday receives from or exports to an external system and its location.

Workday Web Services

Workday’s public API. Based on open standards, Workday Web Services (WWS) provide the core method for integration with Workday.

Integration Map

An integration component that specifies how values in Workday map to values in an external system. Example: Pay Rate Frequency is a type of map in third-party payroll integrations.

Integration Service

A group of related integration attributes, maps, and XSLT that provides a framework to transform Workday data into the format required by an external system.

Integration Transformation

Converts data into a format that Workday or a receiving external system can understand. Workday provides some delivered transformations, and you can also create custom transformations.

Integration Transport Protocol

Controls how Workday exports data to an external endpoint or service or imports the data from an external endpoint or service. Workday supports several types of transport protocols, including email, FTP and SFTP, HTTP/SSL, Workday attachments, and Workday Web Services.

Workday Studio

An Eclipse-based development environment that enables you to build more complex integrations with Workday.

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.

Integrations: How to you identify which integration to choose when you get a requirement

What is the approach?

Here is what I think you should consider while choosing the integration system. It hold good for both inbound and outbound.

When you get the requirement, first see if there are any Packaged Connectors (Delivered) for the third party directly with a little tweaks can help achieve the need.

Then if you were not able to find any delivered packaged connectors, try to see if there are any Core Connectors which are template based can help achieve the need of integration.

If you do not find one from above, check if you can do it with a custom report and through Enterprise Interface Builder.

And if any of the above does not show way for your integration needs, then you look out for Workday Studio. This is the final place where you achieve any complex integrations.

Summary:

Packaged connectors              - Delivered by Workday to connect with third party [End-to-End]
Core Connectors                     - Template based.
Enterprise Interface Builder - Custom Report or Web Service
Workday Studio                      - Multiple output files, Read from different sources , Exceptions,                                                                                                   Inbound & Outbound in same integration.

Integrations: Workday Web Services

Workday Web Services (WWS)

To access the Workday web services, you do not need community access. You can simply search on google and find the links as shown below.

This link below holds all the versions of workday web services. Click to view.

Version Directory

This link below shows all the public web services that you can access and the detailing of its attributes and properties. Click to view.

Workday Web Services

Example below:
Human_Resources is the Service
Change_Emergency_Contacts is the operation that you can perform.

As of today Jan 15th 2020, there are 43 broader services that you can find. Each of these services contain Operations.

You will be able to download the wsdl and xsd definitions.

• WSDL - Web Services Description Language
• XSD    - XML Schema Definition

Also notice that if any services were deprecated, they will be shown next to the operation.

Prefix: intsys

Prefix: Integration Systems

You can find all the integrations Enterprise Interface Builder (EIB) , Cloud Connect (both Packaged Connector, Core Connector), Workday Studio easily with the usage of prefix - intsys

This Prefix will come really handy for you when you are searching for any integrations in your tenant.

intsys: (keyin your search keywords)

Example - 

intsys: INT001 EIB out

Integrations: Workday Studio Introduction

Workday Studio

Workday Studio is one of the 3 ways of building your integrations. (Other two include EIB and Core Connector)

For you to work on Studio, you need to have the Eclipse Software installed on your machine. Once you install your software, and go to your application. You will see number of items on the initial page after the welcome page.

Below are some of the detailing as you move on.

Cloud Explorer :

This is the place where you connect your studio you to the Tenant. It could be any tenant.
You need to pass on Tenant Name, User ID, Password in order to get connected.

Preferences > Workday > Connections

** Be cautious when you right click on your project / Integration, Don't tend to click on remove, which will remove from the server / tenant.

Project Explorer :

This is the preview of your work space which means you are accessing you local files. Each folder is an integration. Clicking on Assembly will open the design for  you.

Outline:

Gives the complete picture of your integration, where you can navigate easily. Check out for different views by clicking the 4 different icons in Outline window.

Design | Tree Structure | mVal | Props(properties) and Variables

Schema Explorer:

You can add WSDL or WSD / You can add WWS (Mostly used for)  / You can add Custom Report schema (Raas) / XSLT

3 different perspectives in seeing your applications -- WD | Debug | Design Report (BIRT)

FYI -
Workday runs on web services.
Global fields fall under Integration system Business Objects

Integrations: Event Statuses

Integration Event Statuses

When You run any integration, ultimately you will see any of the below integration run status. Its good to understand what each status mean.

Workday Integration Run: Event Status

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.

Integrations - Sequence Generator

Sequence Generator

While producing an output file for your vendor or third party system, you don't want to send same file name all the time. Sequence Generator is used to generate a unique, sequenced number each time you run and produce an output file.

For Example your file name looks like - WorkdayDemog.csv and your vendor needs this file every day two times, then with the same file name it will add to more confusion to identify.

If we make using Sequence Generator to the above example you can generate the file name say WorkdayDemog0109112019124039.csv

This represents:

              WorkdayDemog is the file name,               01 is the sequence ,               09112019 is the date,              124039 being the time HHMMSS

The Sequence generator can be used in EIB , Core Connectors or Studio integrations.

If a process generates multiple requests for the next sequence number very close together:

·        Workday attempts to generate the sequence numbers.

·        Workday can generate skipped, nonconsecutive numbers.

Tasks you can use to create, edit and view sequence generators for EIB :

Create ID Definition / Sequence Generator (Also see View and Edit)

Integration System > Configure Integration Sequence Generators 

Below are the detailing of the field while 

Last Number Used- Manually sets the last sequence number. This option is useful if you previously used a different ID generator and you want to continue from where the ID ended. When you set the number, the initial sequence number will be your number plus the Increment by value.

Last Date Used- Specify this date, plus an interval for Restart Every to determine whether the date is before or after the last restart interval. Then Workday sets the sequence number based on the date.

Increment by- Specify the value to increment sequence numbers by.

Restart Every -Specify how often Workday resets the sequence numbers.

Restart Based on Time Zone- The standard time zone is Pacific Standard Time/Pacific Daylight Time (PST/PDT). To use a different time zone for the file generation date and time used in the Format/Syntax field, select the time zone from the prompt.

This value doesn't affect when the event actually occurs. Use this prompt only to localize the date for display purposes.

Restart at Number- Specify the number Workday uses when restarting sequence numbers. To use this field, you set the Restart Every value.

Padding with '0'- To pad sequence numbers, specify the number of zeros that Workday uses to pad each sequence number.

Format/Syntax- Define the filename format by entering:

o A string constant.

o A pattern for the date and time.

o A sequence number pattern.

o The file extension.

Workday can dynamically generate only date values and a sequence number for use in the filename. Any other values are static; they're identical for all files generated by the integration. Hold your cursor over this field to see the full list of valid sequence generator and date/time patterns.