Reporting

Difference between integration, implementation and support?

Integration: Integration is the process of integrating the two system. Example

integration between workday System and Benefit Vendor. After integration they can
communicate each other.

Implementation: Implementing any application/Software for an Organization.

Support: It’s a maintenance of already implemented software of application.

What are your roles and daily tasks at work during implementation, integration and any other
routine Tasks?

I am working as an integration consultant. My day today activity involves creating a

integration, Testing integration, getting involve in vendors calls to get a clarity of
requirement.

Report Types in Workday:

1. Standard Reports
2. Custom Reports

Standard Reports:

1. Report Writer Type

2. XpressO Type

We can only use and copy Report Writer Type reports.

XpressO type are used by Workday Developers.

Custom Reports: Total 8 types. Out of 8 types, three report types are very important. Those are
Simple, Advanced and Matrix.

All types are defined below:

Simple Report: A simple report provides straightforward design options for the beginning or
occasional user to create reports quickly and easily with limited options.
 Advanced: An advanced report type provides all the features of a simple report, plus more
advanced ones such as accessing related business objects and producing multiple levels of
headings and subtotals. Advanced reports also enable the use of sub-filters, run time prompts,
charts, worklets, and report sharing, and provide the ability to expose the report as a web
service.

 Matrix: A matrix report type forms the foundation for custom analytics. It allows you to group
data, summarize metrics for those groupings and then allows the user to further drill into the
summarizations by other dimensions or fields.

 Search: A search report type displays search results based on values selected for facet filters
on the report.

 Transposed: A transposed report type interchanges the rows and corresponding columns on
the report.

 nBox: An nBox report type counts data and displays the results in a 2-dimensional matrix.

 Trending: A trending report type is similar to a matrix report with a time period element. It is
commonly used to report and analyze trended worker data, like headcount and attrition, over
time.

 Composite: A Composite report type allows you to combine several existing matrix reports
into one report. Each matrix report is considered a sub-report and each matrix report can have
its own data source. The resulting composite report can then show data across multiple data
sources if each matrix sub report uses a different data source.

1. What is the relation between Business objects and Data sources in Workday?

Workday stores your data as business objects. A business object can be defined as a
template of an entity, whereas a data source is the data selection or group of data that creates
the template.

Data sources are defined and delivered by Workday. Workday delivers various data
sources for primary business objects. A data source can be designed to return all instances of
the primary business object, or it can have built-in filtering logic defined by Workday

2. What is Matrix Report?

Matrix reports are similar, but not identical to pivot tables and cross tabs found in other
systems. You group data in a row group and optionally a column group. Values in the matrix
cells display aggregate values scoped to the intersection of the row and column groups to which
the cell belongs.
3. What is RAAS?

You may create custom reports and enable them as a web service to be used in an
Outbound EIB (Enterprise Integration Builder) as a data source. If you select this option, then
you must also define Column Heading Override and Group Column Heading values on the
Columns tab, and provide Label Overrides for all prompts on the Prompts tab.

4. What is Worklets?

A worklet is a report that can be displayed in a "tile" on the Workday "landing pages",
which are: My Workday, All about Me, and My Team, and the Dashboard slide-out. Worklets
provide users quick access to frequently referenced data and tasks common to a specific
functional area.

You can create your own Worklets by using the Report Writer and specifying either the
advanced or the matrix report type, and then selecting Enable as Worklet on the Output tab. If
you choose to share a worklet, it becomes available for authorized users to select when
configuring their Workday landing pages.

5. What is Trended Worker Data source?

Trended Worker Data source encompasses a number of fields that fall into 3 general
categories:

Monthly worker snapshots: This type of data includes data about workers as of the last day of
the month, including compensation data, headcount numbers, and biographical information.

Staffing events: These include hires, terminations, transfers and promotions changes in
position, addition or deletion of additional jobs, move events, and international assignments.

Calculated metrics: These are calculations, we can make based on the trended data, such as
turnover rate and span of control.

Workday automatically updates the Trended Workers data source at the end of each month.
Data is collected for the last 36 months (that is, data is collected for as many months that are
available in Workday, up to 36 months). Any data older than 36 months is automatically purged
from the data source. Additionally, any retroactive changes that have been made to a worker in
the last 3 months are automatically incorporated into the trended data.

7. What are the ways to create a report in Workday?

You can create a report in two ways in Workday:

 Run the Create Custom Report task.

 Copy a Workday Standard Report and modify it
8. If a particular report is shared within the organization, will anyone be able to see the same
output while running the report with the same input values?

No, the output will depend on the security access to the data source of the individual who
is running the report.

9. What are Calculated Fields?

A calculated field is used for data manipulation. It is used in reporting, integrations, business
processes, scheduling recurring processes, and other areas within Workday.

You should run the Create Calculated Field task to create calculated fields.

Some of the essential things you can perform with Calculated Fields are currency
conversion, lookup-related values, string or text manipulation, evaluation of an expression,
format a date, etc.

10. Name a few ways of how to access a Workday Standard Delivered Report?

The following are the ways to access Workday Standard Delivered Report:
 Browsing by Category in the Sitemap
 Writing the name of a specific report in the search bar.
 Running Workday Standard Reports
11. How to improve performance of the Reports?
We are using filters, sub filters and prompts concepts in the reports for reducing the Data.
Then it’s automatically performance will be increased. It decreases the system load and
managing all needed records easily.

12. What is the purpose of the web service enable option?

We enable web service option in our report, it allows accessing that report anywhere using
through Web services. It is one of the portable and important options of the workday.

14. Explain the trending report?

Trending report is used by workday to enable a report and analyze trends in worker data like
headcount and reduction through a number of Workdays remitted standard reports. We could
create custom Trending report types that use trended data. Using either custom reports or
standard reports, we can analyze significant trends within our workforce undeviatingly in
Workday without a third-party analytical tool requirement. At the core of all trending reports,
types are the Trended Workers data source.

15. Tell me about Process Monitor?

Process monitor is a process to known about our present execution status of the process. And
its best way to checking and managing our process of execution before executing.

16. What is the difference between reports and templates?

Reports are designed and built by customers or functional users using the Workday Report
Writer tool. They can be created new or as a copy of another standard or custom report.
Workday reports are actionable where you can drill down on items to obtain additional
information and use related tasks to perform authorized actions on items within that report. As
we will see, custom reports can be scheduled, translated, shared, and more features are
available.

Templates have built-in features that extend functionality to end users of Workaday hcm. It
contains different services, Attributes and Maps to build and managing the integration system.
We have different types of templates are available in workaday, and have special features each
of the template. Its take less time to build own integration and it is more flexible. Great look
and fell, user interface are different from reports.

17. What is data source?

It is nothing but a view one primary business object and number of related business
objects.

21. What is difference between filter and Sub-filter?

Primary business object we can use in Filter level

Related business object we can use in Sub-filter level.

22. What is difference between ESI and EMI?

Ex: Employee get salary changes in 5 times by using extract single instance
We can get any single row of data either first occurrence (or) middle occurrence (or)
last occurrence
By using extract multi instance we can get all rows at a time.

22. What all calculated fields are available in workday?

Answer: More than 30 calculated field type are exists in workday. True/False, Text
Constant, Evaluate Expression, Substring, Lookup related value. Date arithmetic .etc
23. What is difference between calculated fields and custom fields?
Calculated fields we have doing validations, data formatting and different
type of functions write in calculations.

Custom fields mean some additional fields we can maintain.

24. What is difference between matrix and composite report?

Matrix Report Composite Report

1. Data Source use in Matrix Report. 1. Business object use in composite report.

2. At a time one data source use in report. 2. Multiple data sources call in composite
report.
3. Non Configurable calculations do total
counts, averages etc., 3. Configurable calculation: sum,
difference, multiply, divide in Composite
Report.

25. Complex task in reporting?

I have a requirement for matrix report my business wants to see the all head count
of each country & cost center wise for that purpose I have created one new custom report.
STEPS:
1. Firstly given report name, report type matrix, data source all active and terminated
workers.
2. Basically in matrix report most important tabs matrix & drill down
3. In matrix tab has 3 main elements row grouping, column grouping, summarize
4. I have selected location address and country in row grouping
5. Coming to drill down tab here my business wants to see the view details of each country
and cost center, region, company, employee
6. I have selected required fields in detailed element.
7. Based on that my business seen the all country details.

26. Can you please tell me difference between simple and advance report

Simple Advanced
 1. Few additional Properties are not 1. All properties are available in Advanced
available in Simple report like Prompt, Report
output, share, Advance

2. we can select only PBO data in Simple 2. we can select PBO data as well as RBO
Report data in Advanced Report

3. you can't share this report to anyone 3. you can share this report to every one

4. you can't use this report in any of the 4. you can use this report in integrations
integrations

27. What are the steps to create a report?

1) Choose Report type and Data Source

2) Select Objects and Fields
3) Order Columns
4) Sort Output
5) Define Filter Criteria

28. What are the Data sources?

1. A Data source defines a particular set of Business objects instance for reporting
purpose
2. Data source is similar to Data Base view ,But Data source is more flexible
3. Data source can return hierarchical data structures
4. Data source Automatically allows the access to all business objects related to
those in
5. The data source.

29. What are the Business objects?

1. Business object is one of the main parts in Workday for retrieving fields Data.
2. Work Day stores data as Business objects, Business object has Fields and
Instances.
3. A Business objects is composed of set of related fields like Data Base Tables.
4. Fields acts as DB columns, Instances acts as DB Rows in workday.
5. Business Objects Automatically links Related Business objects (RBO’s) to access
customer need Fields.
30. What is the difference between Run and Test in reports?

Run is used to be executing all functionalities of the Data in Reports at a time to produces
end of the output file. Test is executing the limited files of Data in the reports for testing
purpose and it displays the limited records of the output file.

31. What is the difference between Report and Custom Report?

Custom reports are designed and built by customers using the Workday Report Writer tool.
They can be created new or as a copy of another standard or custom report. Workday reports
are actionable where you can drill down on items to obtain additional information and use
related tasks to perform authorized actions on items within that report. As we will see, custom
reports can be scheduled, translated, shared, and more features are available.

32. In Filter which fields will be use?

Specify the filter that should be used in the report for filtering data that I will be used fields are
hire date, employee Type.

34. Is it possible to the calculated field can be copy or edit?

Yes, it is possible Any user with access to the domain, we can manage
create/edit/view/delete any system-wide calculated field definition in the tenant.

36. How can you change simple to Advanced Report?

You can create custom reports as an Advanced report type from the start, however, if you
started with a Simple report type, there is an option to convert the report from simple to
advanced. Using the related actions on your report definition, select Custom Report > Change
to Advanced Report Type

35. What is CFBO?

Calculated fields are associated with a business object (BO). This BO is referred to as the
Calculated Field Business Object (CFBO). The CFBO controls the fields are available when
creating the calculated field. There are calculated field function types that enable you to
retrieve values from related business objects (RBOs). Any calculated fields you create for a
business object appear and behave just like any other Workday- delivered fields for the
business object. The business object on which you base your calculated field (CFBO) also
controls when the calculated field appears in prompts and reports.

36. What is the purpose of the web service enable option?

We enable web service option in our report, it allows accessing that report anywhere using
through Web services. It is one of the portable and important options of the workday.
About Reporting:

Report Writing is an essential skill needed for almost any advanced interaction with
Workday, and any Workday Professional (in our opinion) needs to know Report Writing to
perform their job duties successfully. Whether your job includes helping a client through an
implementation, perform data conversion, configure business processes, configure security,
develop integrations, or administer any module in Workday, you need to be able to run and
build custom reports.

37. Name two types of Workday Standard Reports and a difference between them?

Report writer Reports and XpressO reports. Report Writer can be copied and customized,
but you cannot copy XpressO reports.

38. Which prefix limits a search to reports?

“ rd: ”

39. What is the relationship between a Business Object and a Data Source? Give an example.

The Business Object serves as a template of an entity, and the Data Source is the data
selection or group that will create that template. In Workday, one example of a Business Object
is ‘X Employee’ and for a Data Source, ‘All Active Employees’ – a report with these two
selections should only return active employees within the organization. A scenario outside
Workday could be a Business Object called ‘Country’, and a Data Source named ‘All European
Countries’ – this non-Workday example should return Spain, Portugal, France, Germany, Italy,
etc.

40. which delivered report can provide the relationship between data source, business
object and security groups that have access to those?

The “Data Source” Workday delivered report.

41. Name some types of Class Report Fields

Currency, Boolean, Date, Numeric, Text, Object, Self referencing instance.

42. If you share a report with everyone within your organization, will anyone be able to see
the same output when running the report with the same input values? Why?

No, the output will depend on the security access to the data source of the person
who is running the report.

43. What is a Calculated Field? How can you create one? What can you do with it?
 A Calculated Field is a field created to manipulate existing data. To create a
Calculated Field you can run the Create Calculated Field task. Some of the things that you can
do with Calculated Fields are: lookup related values, currency conversion, string or text
manipulation, evaluate an expression, format a date, etc

44. How do you create Report?

Report creation following simple steps, Initially you search for CREATE CUSTOM
REPORT in search Box, then appears a new window on your system it asking report name ,
select the Data source and select report type ,you fill the all information after click OK ,next
another screen you can see options like column, sort, filter, prompts, output, share and
Advanced etc, then you choose column then select the Business Object ,and Field next click “ +
” button for Adding columns. After choose sort option for sorting Ascending or Descending the
fields of data, then select Filtering and sub filtering tab’s for filter the data .Prompts are used in
Reports give Runtime parameters. An output option is used for displaying output format in the
Report. In Share option default selected don’t share others for security. Advanced option, you
choose the web services enabled for retrieve data this Reports data then click Save and Run the
report and then you can see the resulted output in Excel file.

45. Tell me about the data types (PBOs / RBOs) that you have used most often, during your
last project?

Mostly I have used organization (recent project), worker (often), RBO (division,
country).

EIB
1. What is EIB and what are the types of EIBs?
A. EIB is Enterprise interface builder tool which is used to build simple inbound and
outbound Integrations to connect workday with external endpoints.
Types:

a. Inbound
b. Outbound
 2. What is Inbound EIB?
A. Inbound EIB Integration is used to upload data into Workday from external endpoints or
from spreadsheets.
E.g. Uploading personal information of workers, uploading cost centers details in workday.

We can upload data to workday using spreadsheet attachment or external file from
SFTP/FTP/EMAIL locations.

It has 3 components.

a. Get data – For inbound EIBs, this will be external source from which we will
upload file. External source can be spreadsheet or a SFTP location where file is
stored.
b. Transform – This component converts attached file into workday
understandable format.
c. Delivery – This component will specify from where workday will import file.
SFTP/FTP/Email address.

3. What is outbound EIB?

A. Outbound EIBs are used to export data from workday. We can also send this exported
data to any external endpoints such as SFTP/FTP etc.
E.g. Send worker data to ADP from workday, export data from workday to send it regularly to
concern people on a scheduled basis.

The file format can be CSV, XML, JSON, google data, etc.

It also has 3 components.

a. Get data - For inbound EIBs, this will be a web service or a workday report.
b. Transform – This component will convert data retrieved from workday to a
format which external endpoint can understand.
c. Delivery – Here we will specify where to send the transformed data. We can also
download it as attachment if we don’t want to send data to any third-party
system.
4. What are the types of transformation what we can use with EIB.
A. We can use 3 types of transformation with EIB as below.
a. Custom report Transformation
This type is inbuilt transformation of EIB and have limited functionality.

b. Custom transformation.
In this we have to attach XSLT with EIB and supports XSLT functionality. So, this has
more features than Custom report Transformation.

c. 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.

5. Can we use all advance reports as a data source in EIB?

A. No, we cannot use all advance reports in EIB. We can use only those reports which are
web service enabled.

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

A. No

7. What are the limitations of EIB?

A.

a. Only one data source can be used.

b. And only one destination point can be configured for one tenant.
c. Can’t define output tag in EIB.

8. While doing inbound EIB load what should we do to avoid get pending actions in
inbox? BP/task should get complete without any approvals
A. While filling the Inbound template (Spreadsheet template), we need to select
“Automatic processing” on first tab.
For example, while loading compensation change, we use request compensation change
template and it will start “Request Compensation change” BP. So, to avoid this, we need
to select automatic processing option on 1st tab of spreadsheet.

9. Which web service you have used for inbound EIB Load?
A. Here you can name a few web services names and their use.
a. Request comp change: requesting of a compensation change for an employee
via the Request Compensation Change business process.
b. Change job: Perform a job change on an employee or contingent worker. Uses
the Change Job business process. The types of changes include transfer,
promotion, demotion, lateral moves and any other change of data on the job.
c. Change organization assignments: Assigns company, cost center, region, fund,
grant, business unit, program, gift and custom organizations configured for
staffing usage to a filled position or position restriction. Uses the Change
Organization Assignments for Worker business process.
d. Request one-time payment: This operation allows the requesting of a one-time
payment for an employee via the Request One-Time Payment business process.
e. Put Override Balance: This operation will add or update a new Time Off Plan
Override Balance record for a given Employee and Time Off Plan.
f. Edit position: Edits a filled position. Uses the Edit Position business process.

1. Why we are using EIB integrations?

EIB is simplest integration system to build and requires little to no programming and you can
define one source, one transformation and one delivery point that we mostly prefer the EIB
integration.

2. How can you do changes in XSLT?

We can use XML attachment transformation and custom transformations that you create by
using extensible style sheet language transformation (XSLT). Workday
does not generate or validate your XSLT attachments. These attachment XSLT can be used in
EIB, studio and Document transformation.

3. What are the EIB limitations?

EIB’s are purely imported a single data file and it have one data source, one transformation and
one delivery point and It doesn’t allow multiple data sources, transformations, delivery. It
doesn’t support multiple input files and output files and no error handling capabilities. It
doesn’t supports change detection, validation and transaction logs. EIB have limited storage
data.

4. What are the transformation types in EIB?

EIB allows only one transformation in Workday, we use mainly XML transformation using in EIB.

5. What is the difference between Custom report transformation and Custom

transformation?

Workday provides these transformations for build own integration purpose of EIB of lies partly
in the fact that users can create own.

Custom report transformation is used to convert report into something that can understand
external system. Main difference is It converts report into understand EIB integration format.

Custom transformation is convert the already existing data into understand the required format
of other system, we can use processing data of integration EIB included.

6. What is the difference between ILoad and EIB?

When you need to load a small volume of data on a tenant on an ad-hoc basis or day to today
activities, then you go for EIB.

If you need to load for high volume of data and that is initial conversion of data from External
system to workday. Apart from this all report, EIB and any integration you can migrate from
either implementation/sandbox to production by using I load.

Solution is another tool which is used to migrate reports, eib and any integration from one
tenant to another tenant.

7. Complex integration in EIB?

Recently I have created eib integration for request one-time payment,

so the challenge here actually all the bonus and compensation we are loading
request one-time payment here one-time payment we are maintain all employee
 details information and some additional work tags like project, region, product
These three information is added into additional work tags , if generate
that eib these those additional custom work tags are not appearing into
your eib template getting issues like that required work tag information
is missing, so I could observe that and i reading something in community
and can able to understand how I can this is like additional tags so
I just go to view template mode in eib and then simply go to default
work tag section and go manually added the project, region, product and regenerate the
template make sure that template has been update correct data after that i map all data rerun
the process it went to success.

8. What is difference between eib and core connector?

EIB Core Connector

1. One Web service we can use in EIB. 1. Multiple web services we can use in
Core Connector.
2. It generates the single file.
2. It Generates the 6 files.
3. No services options available in EIB.
3. Coming to Core connector 24
4. In EIB some limitations are their eib services are available.
inbound it supports 30MB file eib out
bound it supports 300mb file only. 4. There is no limitations in Core
Connector.

9. What is sequence generator?

Sequence generator enables in our integration to generate unique sequenced file name
each time its runs.

10. What is transaction log?

By using transaction log we can reduce the integration run time.
and also it is pick the specific transaction changes.
ex: personal, compensation.

11. Why you choose EIB and Studio?

EIB: Enter Interface Builder to Build The own Simple and Secure Integration based on
your unique Business need with Work Day

You can use these EIB to build both inbound and outbound integrations.

EIB defined an Integration That has one Data source, one Transformation and one Delivery
point and It allows XML files.
You can choose Set predefined (XSL) Transformation to presented output in Excel and CSV
format.

It’s Deliver the External system endpoint using SFTP, FTPS, HTTP, Email, Web dev and AS/2
services and Encrypt the document with PGP key.

Its creation is simple, flexible and No need of code to build the Integration, so mainly Prefer the
EIB’s

Workday Studio: It is power full Development tool enabling customers and partners to build
sophisticated and highly customized Integration tool from Workday. It has many functionalities
and preferred studio Integration little bit complex when compare to EIB integrations.

12. When do use Transaction Log ?

The Transaction log to monitor The Events for particular transaction type or Business
process type in workday, and find compare differences that have occurred in your workday
Data within a particular Time period. We uses Transaction log after Lunching Integration.

13. Differences B/w Report and EIB?

Report EIB
Report tool Build Simple and Advanced EIB to Build secure and simple
reports in Workday Integrations in workday

It doesn’t supports XML files It’s supports XML file and

Transformations
It doesn’t access the External system reports EIB access the External System reports
data Data using by Web services and
Transformations

Reports are More securable because it runs EIB’s are more flexible compared to
on our local Machines and don’t share others Reports
as report wise It has little bit of code.

Reports are Don’t need of code, Functional

guys are used simply

14. When is eib preferred and studio?

 If you want report to built from scratch better to use report tool and to transform it
eib as we all know its tidy process and require a lot of time but on other hand in studio we can
built have same functionalities as eib but it’s an

Extension when facing complex situations it better to use studio.

15. What is the concept of reference ID in Workday?

Reference id plays a crucial role in workday integrations. It is divides in to type a value.

We allocate reference id to instance of business object. Types can be same but value should
differentiate. For example let’s consider business objet instance like French, English etc

Which has type of language_id but value something else which differ for every
instance. It is assigned by workday using sequence generator, but we can edit them and
remember not assign same id value to same business instance cause problems especially in
mapping when referencing the internal value

With external when both instance have same id cause problems in mapping in overriding the
value.

16. What are the building blocks of an EIB integration?

get data(from web services, SFTP, workday attachment, custom report etc).
Transformation to desired output.(.csv, custom xslt, custom report).

(delivery)Transport Protocol (for sending data to external system using these.).

17. What are the different options available to test a document delivery configuration in
Workday?

Create a definition and configure the retention policy and the address to be delivered the
dress and protocols used to deliver it, give a tag name to

Distinguish itself from other files. Attach it in a business process

Launch a integrationlater test whether it reached its destination by checking it on server,

or using test document which gives the preview of the file on external system.

18. Have you developed and / supported Workday Integrations in the last 2-3 years?

Yes, I was mainly on the supporting side also a very little on the implementation side.

19. What is the difference between Column heading Overwrite and Column heading
Overwrite XML Alias?
 Colum Heading Override XML Alias (on Columns tab), verify the following headers. You
will need to modify Last_Name and First_Name. The headings cannot contain spaces.

Column heading Overwrite to change the column names if you want them to be
different than the field name. Configure a column heading override for the Full Legal Name field
to be just: Legal Name.

20. Why we are using EIB integrations?

EIB is simplest integration system to build and requires little to no programming and you
can define one source, one transformation and one delivery point that we mostly prefers the
EIB integration.

21. How can you do changes in XSLT?

We can use XML attachment transformation and custom transformations that you
create by using extensible style sheet language transformation (XSLT). Workday does not
generate or validate your XSLT attachments. These attachment XSLT can be used in EIB, studio
and Document transformation.

22. What are the EIB limitations?

EIB’s are purely imported a single data file and it have one data source,

One transformation and one delivery point and It doesn’t allow multiple data sources,
transformations, delivery. It doesn’t support multiple input files and output files and no error
handling capabilities. It doesn’t supports change detection, validation and transaction logs. EIB
have limited storage data.

23. What are the transformation types in EIB?

EIB allows only one transformation in Workday, we use mainly XML transformation
using in EIB.

25. Explain about schedule future process by date?

Schedule future process by date describes the integration schedule configurations

and time status that they can schedule to run in future.

26. Tell me about Process Monitor?

Process monitor is a process to known about our present execution status of the
process. And its best way to checking and managing our process of execution before executing.

27. What is the difference between EIB with Studio and Connector with Studio?
 Connectors with studio:-the connectors exists and outputs most of required data field
of studio. We can use studio to enrich the output of workday connector and it needs to require
multiple and complex XSLT style sheets for processing integration, it can be completed in less
than 2hours.

EIB with studio:-it maintains error handling and validation based on condition logic, we can use
multi files and web services exists in order to support the require functionality and it imported
need to custom objects.

About Integrations:

Integrations are crucial when communicating external systems with Workday. To be able to say
you master them means that you understand how data can be imported to or exported from
Workday. Thankfully, there are predefined rules of how that data must look like, and public
interfaces you can access anytime you need to build integration. In this set of integration
questions, we do not attempt to test the mastery of the different Workday Integration tools
available, but the general knowledge of how to build integrations.

28. What are the main types of Workday Integrations and how do you select which solution
to use?

The main types of integrations are Workday Studio Integration, Enterprise Information
Builder (EIB) Integration and Cloud Connect Integration.

When deciding over which tool to use we need to take into account some factors; whenever
you take in the design of an integration, from the requirements you should follow a roadmap,
here is an example of it:

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.

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.

1) Can you let us know with one example of Integration how you worked on?

Integration Name: Sunlife Benefit Integration

 Requirement: Need to send the changed benefit data for employees belongs from
Canada region.

File should contains the Employees data, Dependent Data and Benefit data. These three
data should get sent in file only if it has a change. File should be in xml format.

Approach: We have the core connector for sunlife vendor, But core connector does not
exists for all the plan was client was using.

So I have created a custom report which will capture the all the related event
between period of time and it will get the changed data.

On top of Custom report I have created EIB to get the output of custom report in xml
and next I have created a Document transform to get the data integration map value
into xml file and also in this DT I have created a xml element that will get used in next
level DT. Second level of DT will generate the xml output as per vendor specification.

29. Name a prefix you can use to search for integrations:

“intsys:”

30. Name some Integration ID types:

Workday ID, External ID, Reference ID

31. Name some input and output types for EIBs:

Input: SFTP/FTP, REST, or attachment

Output: SFTP/FTP, HTTP, Email, CSV, JSON, XML, etc

32. What do you use XSLT for in an integration?

You use XSLT to transform the input or output data going into an XML document.

33. What is a WSDL? Why are they important?

WSDL stands for Web Service Description Language, and they are important because
they specify how XML documents should be formatted to be accepted as input or define the
output of Workday Web Services.

Say that you have a data warehouse or an external system that needs to be updated when
an employee changes their information in Workday. What integration should you use?

Core Connector: Worker

34. What is the name of the XML query language you can use to select elements from an
XML?

Xpath

Core Connector
WORKDAY CONNECTORS:

Workday Connectors are pre-built integration templates that extend Workday's functionality to
external vendors for Human Capital Management (HCM), Payroll, Payroll Interface, Financial
Management, and Spend Management. All integrations are hosted and maintained by
Workday.

Workday provides two types of Connectors:

 End-to-end Connectors support a specific named third party application or service.

When a Connector is deployed, the specific business functions between the two systems
are configured with no additional coding required.
 Connectors are pre-built integrations that address the majority of the integration effort
required to connect to third-party end points.

All Connectors require some level of tenant configuration and testing. Each customer may have
specific mapping requirements and different endpoint configurations. These differences in
customer configurations can be accommodated with Workday's integration templates and
mapping capabilities.

INTEGRATION SYSTEM TEMPLATES:

Workday's Connectors share a common design pattern that makes it easy to connect Workday
to complementary applications and services, yet provides the flexibility to configure a tenanted
solution to fit your needs.

Many Workday integrations are simple enough to set up on your own. You start with an
integration template that provides a framework for Workday to communicate with an external
system. Each integration template contains a set of integration services, comprised of
integration attributes and maps that define specific connection points. To reduce complexity,
many integration templates have factory default settings for common definitions and system
requirements. By building in default values for the technical aspects of an integration, Workday
lets you focus on the functional setup tasks related to your data.

Integration systems are tenanted definitions of a Workday integration. An integration system

has the following building blocks:

Integration Template

Establishes the framework for data exchange through a collection of integration services.

Integration Service

Contains a set of attributes and maps related to a specific integration function. Integration
services use XSLT (eXtensible Stylesheet Language Transformations) to convert Workday XML
into a format that an external system can read.

Integration Attribute

Provides one or more tenanted values for a data element in Workday.

Integration Map

Defines relationships between Workday values and external system values. Examples are maps
for benefit coverage levels, marital status, gender, job classifications, and locations.

Transaction Log

Provides a record of business processes and events in Workday. Integrations can subscribe to
specific transaction log events to capture the changes to employee data that are relevant to an
external system.

Core Connector: Worker:

The Core Connector: Worker integration enables you to extract changes to worker data from
Workday and send them to external applications for:

 Identity management.
 Talent management.
 Time tracking.

Business Benefits

Core Connector: Worker enables you to use Workday to maintain a single source of truth for
your entire population of workers. You can then send updates to worker data to other
applications that need that information. Using Core Connector: Worker, you can easily keep
worker data in sync across many different applications.

Additionally, Core Connector: Worker with Data Initialization Service provides a more
performant, resilient, and scalable way to extract worker data. It doesn’t make API calls, helping
it withstand network fluctuations. It can extract data more efficiently; and it can get more data
than Core Connector: Worker without the service enabled.

Use Cases

 Select groups of output fields to include in the integration output file.

 Within each group of fields, include, exclude, or require specific fields.
 Add additional custom report fields.
 Monitor specific business processes for activity.
 Limit output to specific workers or groups of workers.
 Generate an output file that contains only changed fields for each affected worker.
 Send the output file to an external endpoint using FTP, SFTP, email, or other transports.

You can use Core Connector: Worker to send updates on worker data to several types of
external application. Examples:

 Add and remove workers from an identity management application.

 Populate an external time-tracking application.

Recommendations

 Consider engaging with professional services when implementing this integration.

 Workday recommends that you enable the Worker Data Initialization Service. Enabling
this service provides greater resiliency, performance improvements, and an improved
configuration experience.
 If you’re planning to enable an existing Core Connector: Worker integration with the
Data Initialization Service, use the Migrate Integration Configuration for Data
Initialization Service task to ensure proper conversion.
 If you change your Core Connector: Worker integration to use the Worker Data
Initialization Service, note that output can vary when you enable this service. Output
 can vary due to differences in integration behavior with the Data Initialization Service
enabled. You can perform these steps to confirm results in your
Sandbox/Implementation tenant before committing the change to your Production
tenant:
1. Clone the integration.
2. Run the Migrate Integration Configuration for Data Initialization Service task
against the cloned integration.
3. Use the original integration to generate an output file.
4. Use the cloned integration to generate an output file with the same launch
parameters.
5. Thoroughly compare the results.
6. If you find no differences or exceptions, you can migrate the integration in your
Production tenant.
 To improve integration performance and relevance (with either option):

o Don't make integration field attributes required.

o Don't configure a maximum field length for field attributes.
o Set the Version integration attribute to 25 or higher.
o Use XML as the output format (not CSV).
o Don't group additional information fields.
o Use the Transaction Log Service.
o Avoid using more than 20 field overrides.
o Avoid using the Worker History business object.
o Avoid using these report fields:
 Staffing History – All.
 Staffing History – Approved.
 Worker Events Completed.
 Worker History.

Limitations

You can't use Core Connector: Worker to send time-worked data. However, you can send
updates to an external time tracking application when you hire, change, and terminate workers.

These limitations apply when you use Core Connector: Worker with the Worker Data
Initialization Service enabled:

 The Worker Photo data section doesn't include an image field.

 Core Connector: Worker doesn't apply contextual security. You can control what fields
to include in the output through fields and attributes in the integration.
 Any field overrides and external parameter assignments must use the Worker business
object. These field overrides can't have restricted usage.
The Core Connector: Worker integration exports worker data changes from Workday in simple
XML format. Workday also supports output in CSV (Comma-Separated Value) format, with
certain limitations. As you hire, promote, transfer, terminate, or update worker data, the
integration generates a text file containing the changes.

Using configurable data sections or Workday-delivered report fields and calculated fields that
you create, you can export any worker data, in any combination.

Use this Connector to send data for workers and attributes of those workers.

Change Detection

The Core Connector: Worker detects changes to worker data by monitoring a transaction log.
When you configure the integration system, you select which business process and transaction
types that the integration system subscribes to. Workday ignores changes caused by business
processes and transaction types that the integration doesn't subscribe to. By including all
business process and transaction types, you benefit automatically when Workday adds new
types. However, including all is also a potential risk, as the integration might include more
information than is necessary.

The Core Connector: Worker integration uses a three-step process to detect and report
changes:

1. The integration checks the transaction log. It determines which workers have changes
that result in the generation of one of the configured transaction events.
2. For each worker with a matching transactional change, the integration compares their
report fields for:
o The time at which the integration ran.
o The time at which the integration last successfully ran.

The integration identifies which, if any, of the values of interest have changed.

3. If the worker has any changes in field values or eligibility, Workday generates an
appropriate creation, change, or deletion message.

Change Detection Limitations

Changes to the Classification of a Job don’t trigger change detection for this integration. The
context of the change is on the Job Profile (template), and not directly related to any associated
job (instance) for a worker. However, full extraction on worker records includes the job
classification element.

Full-Diff Extract

You can configure your Core Connector: Worker integration to select all workers who meet the
eligibility criteria, then determine changes for the returned data. To enable this option, disable
the Transaction Log service or enable the Use Transaction Log with Full File integration
attribute. When you run the integration, Workday extracts all applicable data for the defined
population of employees. If any data for an employee changed during the defined date range,
Workday includes all data for that employee. The integration doesn’t include prior values when
performing a full extract using the Transaction Log option. Using this option can adversely affect
Workday performance.

Worker Eligibility

For each integration system, you define a group of workers that belongs to the integration
system. A single boolean report field or calculated field defines membership. If the field value is
true for a worker, that worker is a member of the group, and Workday includes changes for
that worker in the output file. If the field value is false, the integration system ignores that
worker.

You can use report fields on the Worker business object to define eligibility. If you can't define
your group membership criteria using a report field, you can create and use a calculated field. If
multiple boolean values are true, the calculated field can evaluate the worker business object
and its related business objects to return true. Example: use a calculated field to return true if:

 The worker is a contingent employee.

 The primary location of the worker is in the United States.
 The supervisor of the worker is John Doe.

Launch Parameters of Core Connector:

As Of Entry Extracts records that are current as of the specified As Of Entry

Moment, Effective Date, Last Moment and Effective Date parameters. If Full File isn’t
Successful As Of Entry selected, then the extract includes only those records that
Moment, Last Successful have changed in one or more output fields. Workday compares
Effective Date to what was current as of the Last Successful As Of Entry
Moment and Last Successful Effective Date parameters.

Full File Extracts Workers as of the As Of Entry Moment and Effective

Date, regardless of whether they’ve changed.

Restrict Results By Orgs Extracts Workers for only the specified Organizations and all
subordinates.

Workers Extracts only the specified Workers.

If you configure no values, then the integration considers all

workers when looking for transactional and data changes.
Specifying workers in this list doesn’t force their inclusion in
the output file. Information for a worker displays in the output
file only if there are changes in the data fields evaluated by the
integration system.

If there was an error involving data for one or more workers

during a prior integration run, specify workers in this
parameter at launch time. Correct the worker data and then
run the integration again only for those workers. Set the Last
Successful As Of Entry Moment to the moment used for that
parameter on the prior run.

Integration Audit Files

Every time the integration runs, Workday generates these files:

 The Data Changes Audit is a readable version of the integration output file.
 The Diagnostic Audit is designed to help you troubleshoot integration errors.
 The Schema XSD file defines the content and the structure of the output file. It includes
only those fields that you’ve enabled for your integration system. Workday generates
this file every time the integration runs. The file reflects your integration configuration
as of the moment that the integration ran. You can only generate this file by running the
integration.

Scheduled Integration Launch Parameter Examples

Example 1: Full File, Run Weekly.

 To schedule a full file integration, specify these values for the Effective Date, As Of Entry
Moment, and Full File launch parameters:

Field Value Type Value

Effective Date Determine Value at Current Effective Date

Runtime

As Of Entry Moment Determine Value at Current Moment (DateTime)

Runtime

Full File Determine Value at Select check box as True.

Runtime

When the integration runs, it sends a file that contains all workers who are in the
specific date range. The integration includes all workers regardless if there are any
changes for a worker.

Example 2: Full File, Compare Current, Run Now.

To schedule an integration that compares:

 Current worker records.

 What was current as of the Last Successful Effective Date and Last Successful As
Of Entry Moment.

Specify these values:

Field Value Type Value

Effective Date Determine Value at Current Effective Date

Runtime

As Of Entry Moment Determine Value at Current Moment

Runtime (DateTime)

Last Successful Determine Value at As Of Effective Date of

Effective Date Runtime Last Completed
Integration Event

Last Successful As Of Determine Value at As Of

Entry Moment Runtime Entry DateTime of Last
 Field Value Type Value

Completed Integration
Event

Each time the integration runs, it sends a file that contains:

 Changes that occurred between the last integration run (From Last Successful As
Of Entry Moment) and the current date and time (As of Entry Moment ).
 Changes that are effective between the Last Successful Effective Date and
the Effective Date.

Example 3: Restrict Results by Orgs.

To schedule an integration that extracts workers from specific orgs and their
subordinates, specify values for these launch parameters:

 Effective Date
 As Of Entry Moment
 Restrict Results by Orgs

Field Value Type Value

Effective Date Determine Value Current Effective Date

at Runtime

As Of Entry Determine Value Current Moment (DateTime)

Moment at Runtime

Restrict Results Determine Value Organizations

By Orgs at Runtime

Example 4: Full File, Workers

To schedule an integration that extracts specified workers, specify these values for
the Effective Date, As Of Entry Moment, and Workers launch parameters:

Field Value Type Value

Effective Date Determine Value Current Effective Date

at Runtime
 Field Value Type Value

As Of Entry Determine Value Current Moment (DateTime)

Moment at Runtime

Workers Determine Value Workers

at Runtime

ACTIVITY OVERVIEW

In this next sequence of activities, you will use the Core Connector: Worker integration
template to generate an XML file based upon how you configured the integration system.

The first integration we build using Core Connector: Worker will generate the following XML
file:
PICOF and PECI
Cloud Connect for Third-Party Payroll (CCTPP) is Workday's catalog of packaged connectors for
integration with third-party payroll systems. The Payroll Interface (PI) and Payroll Effective
Change Interface (PECI) connectors provide the structure necessary for implementing an
integration between Workday and third-party payroll systems, providing the data typically
needed by payroll systems in XML format. This XML data is then transformed into the target
system format using Document Transformation (DT) ETV/XTT attributes.

Third-Party Payroll Connectors are packaged integration templates with a configurable set of
HCM data across a range of categories. Because third-party payroll providers only need a subset
of the employee data in Workday, these interfaces let you specify which data elements to
include in payroll extracts, when to include them, and how to detect changes based on
Workday transactions. When launched, the integration captures changes to employee data for
a given pay group and pay period, and creates an output file in XML or CSV format based on
your specifications. You can then deliver the output file to an external system, perform
additional transformations to convert the file into another format, or use Workday's audit
reports to identify changes for manual data entry into an external system.

PAYROLL INTERFACE

Payroll Interface (PI) is one of Workday’s third-party payroll connectors. This template is built
based on the Get Payees web service.

PAYROLL EFFECTIVE CHANGE INTERFACE

Payroll Effective Change Interface (PECI) serves the same purpose as PI but performs a more
comprehensive evaluation of data changes to create an effective stack of worker data changes.
The data changes are reported in the sequence in which they become effective and entered in
Workday. PECI is not built based on a web service but utilizes the DIS (Data Initialization
Service), a framework built and maintained by Workday.

PAYROLL-RELATED EVENTS

When a change is made to worker data, the change may be passed along to the payroll system
through the Payroll Interface. See the chart below to visualize some examples of events and
how the interface may be configured to pick these changes up for payroll processing.

Event Possible Actions

PROMOTION Change in compensation, position and
organization
ADDRESS CHANGE Mail pay stubs to new address
HIRE Initiate employee on payroll
TRANSFER (WITH PAY GROUP Change in compensation
CHANGE)
LEAVE OF ABSENCE Possible stop in payment
BENEFIT ELECTION Change in earnings and deductions

SETUP CHECKLIST
Unlike non-payroll-related integrations, Workday payroll integrations require payroll-related
tenant configuration. Prior to configuring Payroll Interface, set up and verify the required
tenant configuration items:
1.Payroll Interface Countries
2.Period Schedules
3.Run Category
4.Pay Groups
5.Pay Group Hierarchy
6.Payment Election Rules
7.External Payroll Earnings
8.External Payroll Deductions
9.Leave Types

PAYROLL FRAMEWORK

The Payroll Framework is the starting point of your integration. At the top of the Payroll
structure is the Payroll Company, which is typically defined by the specific Payroll Vendor used.
When you create your Payroll Company, you assign Pay Group as the subtype, allowing the Pay
Group to roll up to the Payroll Company. Each Pay Group is associated with a Run Category and
Period Schedule to derive Pay Periods. Every employee in the system is assigned to a Pay
Group.

PERIOD SCHEDULE

A Period Schedule shows how periods are defined by specified start and end dates, their
frequency, and where the schedule is used in the system. These can be shared by different
processes but our focus for this course is how the Payroll process uses the Period Schedule.
Define a period schedule and frequency for employee payment, such as weekly, bi-weekly, or
monthly. This is how Payroll Interface calculates and distributes payment. Pay periods are
derived from the Period Schedule.

RUN CATEGORY

Each Pay Group is assigned a Run Category. Pay Groups used for Payroll Interface may only
have a single Run Category. A Run Category may only have one Period Schedule. The Period
Schedule defines the start and end dates of the pay periods. In the setup, indicate that the Run
Category is used in Payroll Interface.

PAY GROUP

Pay Groups identify who to pay, the pay frequency, and which payments to process by tying
together the Pay Period and Run Category previously defined.

A Pay Group is a group of workers in Workday who are paid in the same way, including:

 Same frequency
 Same period begin and end dates
 Same pay dates
 Same pay check dates

This is important because large enterprises, especially global enterprises, will likely have various
methods of paying their employees. Perhaps one region uses a monthly frequency, and another
uses a bi-weekly frequency. Perhaps the date paychecks are distributed fall on different dates,
based on department. Pay Groups organize these variations so that automated payment
processes can easily be distributed per the customer requirements.

PAYROLL COMPANY
All of the individual Pay Groups you create roll up into a Payroll Company. Usually this
represents the payroll vendor you are using (for example, ADP Payroll). Sometimes companies
have a more complex way of grouping and paying employees. For instance, if the organization
has one payroll vendor used for the UK and another for the U.S., each of these processes would
be represented by a unique Payroll Company. Within these Payroll Companies, we can define
different Groups who share common ways of being paid and/or periods of payment.
You may have one Payroll Company representing one payroll provider and beneath the Payroll
Company, multiple Pay Groups or a single Pay Group.

PAYROLL INTERFACE COUNTRIES

Select the countries where you're licensed and planning to use Workday Payroll. These
countries determine the values available in the Country field that appears on various payroll
pages.

PAYROLL FRAMEWORK ELEMENTS

Configure the period schedules, run categories, pay groups, and payroll companies defined
above to create the payroll processing framework.

PAYMENT ELECTION RULES

Payment election rules must be configured for each run category defined in Workday. They are
used to control how to pay workers for each type of pay they receive. They define:
 The payment types (e.g., check and direct deposit)
 The number of elections allowed for each pay type
 How payments are distributed among split payment elections

If the rules for a run category are not defined, payroll cannot be completed. An error message
will appear when payees in the run category are processed.

EXTERNAL PAYROLL EARNINGS

Earnings include direct compensation such as salary, bonuses, and allowances, as well as
indirect compensation (taxable benefits) such as health care costs paid by the employer that
are categorized as taxable. The Maintain External Payroll Earnings task allows for configuration
of the earnings code used internally by Workday and externally by the payroll system.

EXTERNAL PAYROLL DEDUCTIONS

Deductions include employee contributions to health care or life insurance plans. The Maintain
External Payroll Deductions task allows for configuration of the deduction code used internally
by Workday and externally by the payroll system.
LEAVE SETUP
Employee leaves, such as medical, family, jury duty, and bereavement may have a payroll
effect. A leave type defines the set of rules that apply to a specific type of leave. It identifies the
unit of time for leave requests, employee eligibility rules, validation rules, whether to track
balances, and other rules. Leave types are organized into Leave Families, or categories.

ASSIGN EMPLOYEE TO PAY GROUP

After the pay groups, schedules, and run categories are created, employees are assigned to a
pay group to be set up for payroll. Moving the employee to a different pay group can be
accessed from the employee record.
Note that the Effective Date of the Pay Group assignment must be in the past or Payroll
Interface will not recognize the employee.

INTEGRATION SYSTEM

An Integration System is an object in Workday that stores the configuration of the integration.
The following diagram shows the flow of configurable features and services used to set up and
manage the system.

INTEGRATION SYSTEM ATTRIBUTES

Referring back to our earlier diagram of the Integration System, typically the first step once we
have selected the template is to set the Integration System Attributes. The following Attributes
are required to launch Payroll Interface:

Attribute Description
VERSION Indicates the Workday version of your
environment.
PAYROLL VENDOR Indicates the third-party payroll vendor for
the integration.
PRIMARY PAYROLL INTEGRATION Identifies the integration as an Ad-hoc or
Primary Integration.

PICOF(Payroll Interface):

The Extract All Payee Data attribute allows you to bypass change detection and get a full file of
employees in the pay group specified. In the next activity, observe how this setting returns a
Summary extract without any additional fields enabled. Note which fields are included as part
of the Summary section for each employee record.

Note: Alternatively, the PI Full Extract with No Diff Launch Parameter integration service can
be enabled. Check the box for this parameter when launching the integration to return a full
extract.

INTEGRATION LAUNCH
Payroll Interface can be launched as a Primary or Ad-Hoc integration. Both types are required
for implementation of a Payroll Interface connector. The two systems are essentially clones of
each other, functionally similar, that are used for different purposes.

Integration Type Definition

AD-HOC INTEGRATION Used for manual runs, debugging, and
testing. Maintained in the Production
environment to be run as needed.
PRIMARY INTEGRATION Configured with a schedule to be run
regularly. It is not used for testing and is
essentially

For Payroll Interface, whether an integration is Primary or Ad-Hoc is controlled by an

Integration Attribute.

REQUIRED LAUNCH PARAMETERS

Only two launch parameters are required to launch a Payroll Interface integration: Pay Group
and Pay Period Selection Option. Additional launch parameters become available when the
Change Detection Launch Parameter integration service is enabled. These will be covered in
detail in the Change Detection chapter.

Field Definition and Value

PAY GROUP Groups of employees who are paid the same
way.
Select one or more pay groups at the
prompt to extract pay period data for all pay
group members.
PAY PERIOD SELECTION OPTION The Pay Period is the date range employees
are paid. Specify how to select the pay
period:
  Use Earliest Open Pay Period: Selects
the first open pay period based on
the pay group's period schedule and
period calculation status.
 Use Pay Period for Current Date:
Selects the pay period for the current
date.

Earliest Open Pay Period

When Use Earliest Open Pay Period is selected, the integration looks at the status of the
pay periods defined in the Schedule for the Pay Group(s). It will process the next pay
period with a Calculation Status of Not Yet Started or In Progress that follows a previous
pay period of Complete. This is often what is used in a scheduled integration; once it is
configured, the integration automatically picks up the next open pay period to determine
if any changes happened in that period.

Important! The integration requires at least one pay period to be completed to define
where to begin change detection.

Pay Period For Current Date

Pay Period for Current Date selects the most current pay period regardless of the period status.
This option is useful for manual run tests.

PAY PERIOD CALCULATION STATUS

There are three Pay Period Status values:

 Not Yet Started
 In Progress
 Completed

Pay Period Status is updated automatically when a Primary integration is successfully

run.The open pay period changes from a status of Not Yet Started to In Progress. The Pay
Period Status must then be set to Complete to finish Payroll for that period.

Note: Pay Period Status can be manually updated for testing your integration configuration
by using the Edit Organization related action off of the Pay Group.

CHANGE DETECTION RULES

The change detection logic uses two rules to compare entry and effective dates with last
successful run and pay period start and end dates. See the diagram below to understand how
the algorithm uses these rules to ensure changes are captured in the output.
Rule 1: When the event entry date is after the LSRD, the change is picked up if the event is
effective in the current or prior period.

Rule 2: When the event entry date is before the LSRD, the changed is picked up if the event is
effective in the current period AND the change detection method is All Effective.

PRIMARY INTEGRATIONS AND CHANGE DETECTION

As mentioned previously, Primary integrations do not use the Change Detection launch
parameter, but apply a change detection method automatically.
If it is the first run of the Pay Period for the Pay Group specified (calculation status of Not Yet
Started), the integration applies the All Effective method.
The Pay Period status is then automatically updated to In Progress and the Last Successful Run
date is saved for that Pay Group. Any subsequent runs for that Pay Group while the Pay Period
is still In Progress will apply the Changes Only method.

PRIMARY INTEGRATION SETUP

For Payroll Interface, the Primary Payroll Integration attribute must be set to “yes” and the
Change Detection Launch Parameter service must be disabled.
Schedule the integration to run based on customer requirements. The only parameters that
require configuration are Pay Group and Pay Period Selection Option. The Pay Period Selection
Option should be set to “Use Earliest Open Pay Period.”

1. What is the difference between CCW and PI?

CCW and PI are having same working environment and look and feel, but slightly differences
are there.CCW mainly concentrates on Worker operations and managing employee data
operations based on Worker Business object. It usually performs operations on worker personal
information, worker positions and worker compensation.

Payroll interface explain about payroll information and it allows you to manage payroll related
data and send it to a third party payroll provider, And it provides data changes, promotion,
address change, Hire, Transfer, leave of absence and payment process are can be processed in
the payroll system.

Lunching parameters are different of PI and CCW.

2. Can you generate multiple files in Connector?

Yes. For example if you need to create 3 files separately, then create 3 DT and separately write
3 xslt for each file and then each xslt you attach in individual DT. Then finally these 3 DT you
attach to the Connector by business process.

3. What is the core connector in Workday?

Core connectors extend the workday functionality to external systems for Payroll Interface,
Payroll, HCM (Human Capital Management), Speed Management and Financial Management.
All the integrations are managed and hosted by Workday.

4. What is the use of Workday cloud-connect?

The Workday Cloud Connect Benefits an enterprise management suite that gives a single
system to manage the benefits of your employee. The Workforce Cloud Connect for Benefits
helps companies design, implement, and manage various benefits plans and opportunities.

5. What do you know about packaged connectors?

Packaged connectors are also called delivered ports, are the integration adapters developed for
a particular vendor. We just need to perform some fundamental configuration to launch them,
and no extra coding is required.

6. Why do we use “Field Override Solution”?

Filed Override Solution is used to add additional fields in the connectors.

7. What are The Lunch parameters in CCW?

The Data parameters extract the records that what are the data needed current as of specified
parameters in The Lunching an Integration System.

The CCW has four lunch parameters in Workday ,They are 1)As Of Entry Moment ,2)Effective
Date,3)Last Successful As of Entry Moment,4)Last successful Effective Date

As Of Entry Moment enables you to search for and retrieve future-dated data changes where
the changes has been entered in workday ,but the effective date has not passed yet.

Effective Date defines the end of date range during which changes became effective. The
integration extracts all changes with effective dates on or before this date.
Last Successful as of Entry Moment default to the last moment at which the Integration system
was successfully lunched. You can override this date and time in order to force the Integration
to search for and retrieve data changes over a wider period.

Last Successful Effective Date defines the beginning of a date range during which changes
became effective. The Integration extracts all changes with effective dates after this date

8. Tell me about a core connector / EIB / Studio that you have created.

I created integration system using pi which we discussed in later document using ccw we

9. How do you convert the file format of a core connector and studio output, do they use
same process or different process. Describe in detail.

In ccw and pi in the same process where we select the services required for them and
configure them in the integration attributes and we mention that in xslt.

10. Explain Area Override Solution?

Area override solution is utilized to insert extra fields like calculated fields within the
output as those fields are not readily available under any kind of solution.

11. How or where can you test Core connector worker integration?

We completed implementation part of integration, we check the execution in tenet of

workday, and mostly prefer for testing in sandbox. Then we move the production environment.

12. What are DT and CCW? What is the relation between these two?

Document transformation integration system template is part of the cloud connect

catalog. It is using only the attach XSLT file for transformations and we can use specific
attributes, mapping values for specific process of integration in the workday. After
transformation DT generates the output.

CCW mainly concentrates on Worker operations and managing employee data operations
based on Worker Business object. It usually perform operations on worker personal
information, worker positions and worker compensations. and TO get the output using DT in
CCW for XML attachments. CCW can’t be proceed directly XML operations.

13. How many times Delivery attempts?

3 times by default.

14. Which editor you can use for XSLT editor?

We use editors are oxygen, notepad and notepad++ for XSLT in Workday.
15. How can you identify that requirement will be do in CCW, EIB and Studio?

When we require simplest integration system to build and requires little to no

programming and you can define one source, one transformation and one delivery point that
requirement we mostly prefers the EIB integration.

CCW mainly concentrates on Worker operations and managing employee data operations
based on Worker Business object. It usually perform operations on worker personal
information, worker positions and worker compensations that type of requirement need to
package, We prefers CCW template in the cloud connect catalog of connectors

If the integration has a high number of use cases, needs to make multiple calls to web services,
process large amount of data and multiple business objects at once, handling complex errors
that requires we can choose Studio.

Document Transformation:
1. What is document transformation and why it is used?
A. Document transformation (DT) if type of connectors. DT is used to apply transformation
on output files of Integration/reports. We attach XSLT document in DT. This XSLT doc
will have code to transform/process the output document of main/parent integration.
Once DT is created you need to attach it to parent integration.
So, when parent integration runs, output file of parent integration will come to DT as input and
then XSLT will apply on that input then you will get final output file which will be sent to
end user(vendor).

While using DT, keep the output format of parent integration as XML as DT needs XML
file as input.

2. Where we can apply DT?

A. We can apply DT on following.
a. EIB
b. Reports
c. Connectors

3. How many DTs we can apply on one Integration?

A. There is no limit for this. However, workday suggest using maximum 6 DTs in one
Integration for better functioning of Integration. This way the performance of
integration will not get affected.

4. How many XSLTs we can attach in one DT?

A. We can attach only 1 XSLT in 1 DT.

5. What are the steps in creating DT?

A. Search for task “Create Integration system”. Give the name to Integration. Select the
template as “Document transformation”. Click OK.

We will get the below Error to attach XSLT document as this is mandatory to upload XSLT
doc in DT.

To load XSLT document, click on integration system and then “configure integration
attachment service”.
Click on “create integration service attachment”.

Upload the XSLT document. Click OK.

Now you have to attach this DT to your main integration.

6. How to connect DT with parent integration?

A. First create parent integration and then create DT separately.
Now go to business process of parent integration like we saw in configuring delivery.

We need to attach DT here.

Add a step and give the order to that step. And in type select Integration.
 To configure, click on configure.

Select the already created DT here. Optionally you can give name to request.

Once this step is completed your parent integration is ready to run.

General
1. Vendor wants changes only data. Transformation is needed, and output should go to
SFTP location. Which type of integration you will create?
A. Core Connector.
Reason is in core connector we can send changes only data easily. Also, we can apply
transformation using Document transformation connector and we can send output file
to SFTP location using delivery service.
 2. Need to send only hire transactions in above scenario. What changes will need.
A. Enable Integration transaction log service and select hire BP only.

3. Which integration we should create to send all employees all information to vendor?
A. EIB.
For this scenario we can create EIB or core connector worker (with full mode). However, EIB will
be easy. So, the first choice will be EIB.

4. How to migrate Integrations, CF, reports etc. from one tenant to another?
A. For migration we can use “Object Transporter”.
To migrate, go to related actions -> select instance -> Migrate

Then click on “launch object transporter”. It will show source tenant and target tenant. Select
the target tenant and way to login to that tenant (with user id/password or SSO).

It will show differences on next screen. If there are no differences, you can move forward. If
there are differences between source and target tenant still you can move forward but
there are chances that the process will not complete properly. Some fields might miss.
You will get confirmation message.
 STUDIO
Studio Integration

I Have a requirement for project manager assign, which all project manager missing in projects.

ex:- we have a projects, each projects have a project manager role. based on this data project
related approvals goes to project manager.

we could observed that couple of projects didn't assign any project manager & few
projects managers are recently terminated. in this case the project approvals goes to no
assignable tasks. my business provided a list of alternate projects managers based on project
hierarchy.

we can use assign role web service to assign missing project managers with using EIB,
but our business team looking for a auto-machine process which run on daily basis to verify
missing project manager and auto assign manager role.

if you go with EIB, it is completely manual process. if you go with studio it is

automatically take care of all process.

Process Flow:- i create a custom report to verify the all projects which is missing project
managers as well as terminated managers details.
 Please make sure enable as web service to call in your studio Rass Report. i will take
workday-in component to specify my integration name. next i will take workday out rest
component to call above created rass report to extra path with report Alias name. next i will
take asynchronous mediation in store variable to see report out put data. the report out put
should be in an XML.

Next am going to take splitter component why because my 100 rows. we can not
directly pass 100 rows to web-service at a time. so we need to split each & every row by using
splitter. in splitter x-path I am going to select report data/report entry. each report data in
separate row.

after splitting data into row later take eval component to store my all row columns into
props variables

ex:- project name

props[project-name] = parts(0).xpath[report entry/project name]

Next iam going to take cloud log to see all my props variables getting values (or) not.

Next iam going to take asynchronous component with write component . in this write
component we prepared a soap request message based on assign roles web services with help
of schema explorer. Generally using schema explorer selecting my web service and creating a
soap message and tested with in web services tester.

above stored props variables dynamically assigned to write component soap message.
later i will call to workday out soap component by selecting web services category name
staffing & required version 31.2 .

and also iam using send error component at asynchronous mediation to capture all
my error details before calling the workday out soap component. Generally in asynchronous
mediation downstream error property to put integration message to capture my all error
details.

Workday Studio: It is power full Development tool enabling customers and partners to build
sophisticated and highly customized Integration tool from Workday. It has many functionalities
and preferred studio Integration little bit complex when compare to EIB integrations.

1. Why Should We Use Workday Studio?

 Complex Integration
 Complex Validation
 Call Multiple custom report at same time
  Generate multiple file at same time
When you need to developed any inbound integration which has to be schedule daily basis
You can incorporate java code in workday studio

2) How will you get data from Tenant to Studio?

We can get data from tenant data using web services call and Raas call.

3) How will you transfer data from Studio to Tenant?

We need to get the data from SFTP or Workday attachment as per customer
requirement and Need to call an appropriate web service to Load the data into tenant .

4) How will you send any custom report to client using studio?

We can get the custom report using Raas call according to client need we can
transform the report and we can sent the by email using email out component.

5) How will you declare variable in Studio?

Using eval component we can declare variable.

2. Name some MVEL variables that you can use in Workday Studio?

"lp" to access launch parameters.

"vars" to access MessageContextVariables
"props" to access message properties

3. Which Workday Studio component is used to translate a conditional if or a loop?

Route component is used to translate both conditional if or a loop depending on the routing
strategy.

Conclusion

So now, you have an idea of possible Workday interview questions you could come across. You
may not be explicitly asked these questions in exactly these words in your interview, but having
answers in mind for them makes you more prepared for anything that the interviewer throws
your way.
To master advanced concepts of Workday, join our comprehensive Workday Course, which
equips you with the necessary skills and more that you need and help you become job-ready
upon completion.

4. What is XPath?

XPath uses path expressions to navigate in XML documents and also XPath is the syntax
for defining parts of an XML document.

5. How can you identify that requirement will be do in CCW, EIB and Studio?

When we require simplest integration system to build and requires little to no

programming and you can define one source, one transformation and one delivery point that
requirement we mostly prefers the EIB integration.

CCW mainly concentrates on Worker operations and managing employee data

operations based on Worker Business object. It usually perform operations on

Worker personal information, worker positions and worker compensations that type of
requirement need to package, We prefers CCW template in the cloud connect catalog of
connectors

If the integration has a high number of use cases, needs to make multiple calls to web
services, process large amount of data and multiple business objects at once, handling complex
errors that requires we can choose Studio.

6. How do you select which solution to use?

When deciding over which tool to use we need to take into account some factors; whenever
you take in the design of an integration, from the requirements you should follow a roadmap,
here is an example of it:

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.

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 Nonexempt employees, calculate
deductions, etc. If yes, then most likely you need a Workday Studio Integration.

7. When to use the workday studio?

You have to use Workday studio when you have to do these:

When you have to deal with large sets of data.
Add Spring, Custom Java, or 3rd party capabilities.
When you have to include complex looping.
When you have to include branching logic based on external variables or dynamic data.
When you have to execute several reports and rules to get your data.

8. How would you describe your experience level with XML, XSLT, X-Path and web services?

I would tell good xslt is nothing but extensive style sheet of xml it is used for rendering
the xml document. It has tow attributes XTT and ETT transform

XML data to required output.

Xpath as we all know workday is object oriented. It use xml.xml store data using two
types of database formats. One we relational and other was hierarchy database where under
parent emit child be present, in those databases to extract data we use xpath to get the data.

XML is a markup language unlike html it does not present data rather it store the data in
any it was represented web services. There play crucial in integrations an deport generations.
Services like get_worker_payee help in retrieving the

Worker and payee details. Some be invoked automatically some by manually.

9. How to get the report by using the workday Studio components?

We get the report by using the web service URL link of the report, navigate to the report in the
tenant and use the related actions menu to view the Web Service URLs. And click on the
Workday XML link to view the report in a browser window. You can copy the extra path out of
the browser URL you will need to enter a user/password. We create new assembly project in
studio called as a report named and Workday IN transport, workday output Rest transport, and
async mediation with log step after we set the PutIntegrationMessage (PIM) - when the "Select
Parameter" dialog is displayed, click Finish.

Write the components together and configure the other components as necessary. we save
the project and lunch.

Name some MVEL variables you can use in Workday Studio and what are they used for:

“lp” to access launch parameters, “props” to access message properties, “vars” to access
MessageContextVariables

10. What Workday Studio component you can use to translate a conditional if or a loop?
What good practice you should add to your integration to get notified of any errors in your
Studio integration?
 The Route component can act both as a conditional if or a loop depending on the
routing strategy. Error handlers type send-error are used as a good practice to catch errors and
send them to either the integration event or another output method
via the out-transport.

Business Process
1. What do you understand about the term 'Business Process' in Workday?

In Workday, the business process is a collection of tasks that you can initiate, act upon,
and finish to accomplish the desired business objective as part of an HR procedure. Business
processes define Workday's core functionality. It describes how significant events flow and
allows the configuration of approvals, notifications, conditions, etc.

Examples of business processes are changing jobs, Hiring, Terminating Employees, Proposing
Compensation Change, and more.

2. Define Workday Business Process Framework.

The Workday Business Process (WBP) Framework enables you to improve process flows within
a company by inducing various activities. It allows customers to configure and manage core
flows within the Workday to connect people, apps, and services. In the Workday applications,
the business process framework is where all the transaction-related changes to data and events
originate.

3. What type of conditions defines Business Process Steps in Workday?

In Workday, Start Proxy is the task that gives all the details of the business processes involved in
the Organization. Business process steps involve validation condition, running condition, entry
condition, and exit condition.

4. Tell me, will business process events be impacted if you modify the business process
definition in Workday?

In Workday, to edit the business process definition, you need to search the business process
name  edit the definition of the related action.

By creating a new business process definition, the already running business process won't get
affected. It keeps running in the background without causing the event to overlap.
5. Which task helps you to test assigned steps in the business process in the organization?

'Start Proxy' is the task used to test the assigned steps in the business process. Proxy
policies are configured from the "Create Proxy Access Policy" task, and they cannot be executed
in production environments.

6. Which type of approvals can you configure in a review step in a Business Process?

Below mentioned Approvals are to configure in review step in a

Business Process
 Individual Approval
 Consolidated Approval Chain
 Consolidated Approval
 Mass Approval
 Approval Chain
7. What report provides the details of all the actions available for the specific Business
Process Type?
Business Process Configurations Options report

8. How can Organizations be tied to Business Processes?

Workday allows the configuration of Business Processes per Organization. While

implementing a business process with multiple Organization-dependent definitions, Workday
follows a hierarchy to check which definition to execute.

An example could be multiple hire business process definitions depending on departments.

E.g., Hire for Finance department, Hire for the HR department, Hire for the IT department, etc.

9. What is a Business Process Completion Step?

The business process is considered complete once the completion step finishes the execution.
All the actions depend on business process completion but do not depend on all the steps being
executed.

For example, an organization wants to hire a candidate, and that position requires background
verification. Suppose if you do not want to wait for all the information to come back from the
background check business process, you can set the completion step before the last step. That
will allow the pre-hire or hire business processes and enter the Background Check Business
Process before the Pre-Hire executes all the steps.

If no steps are marked as a completion step, then the last step will be the completion step by
default.

10. What actions can you do with a Business Process Event if you want to modify its behavior
in a running state?

You can use actions like cancel, reassign, correct, and delegate to modify the business process
event's behavior pattern. To search for events, you can use the prefix "event"

11. What is meant by the business process?

A business process is a set of tasks that users can create, act upon, and complete. These
business processes are created with a combination of actions, approvals, checklists, etc.

12. What are the business process steps in Workday?

Following are the steps involved in a business process:

 Entry Condition
 Exit Condition
 Running Conditions
 Validation Condition

13. What are the approval process steps in the Workday business process?
Below are the approval process steps of a business process,

 Individual Approval
 Approval Chain
 Consolidated Approval
 Consolidated Approval Chain
 Mass Approval
14. How can we check and mark a business process action behavior when it is already
running?

We can change the behavioral pattern of a business process using the below actions,

 Cancel
 Reassign
 Delegate
 Correct

15. Which report can help you get the details of all action types available in the Business
Process Type?
The report which can give business process details is Business “Process
Configuration Report”.

16. Explain Business Process Completion Steps and its importance.

Once the completion step finishes the “Complete step” final execution, it’s called a Business
Process Completion Step. As other actions depend on the completion step, it’s important to
major this step for Business Process Completion. But at the same time, it does not necessarily
depend on all the included steps to final their completion depending on this step.

Let’s take an example to understand this:

Similar to the organizations when they hire a new employee, it’s important to do the
background verification to onboard the resource. Though this is not part of the hiring business
process but it’s important for the onboarding process. It shows that the HR does not need to
wait for all the information to cross-check and verify before onboarding but there is certain
information related to educational qualification, other job authentications are important to get
verified. The rest keeps working in the latter stage of the verification process. Processes can be
set and priorities as pre-hire and post-hire based on their requirement.

In the process stream if no step is marked as completion step then the last step in the stream
will be “Completion Step” by default.
 WORKDAY SECURITY

It enables customers to modify or accept delivered default security groups and security policies
that control view and modify access to workday. It helps to answer questions like:

Can you run a task? For Whom? For Yourself? For What items?

Security Group represents one or more workers with similar access and modification needs,
such as HR partner. A Security Policy details the report fields, tasks, and views that the group
can access and or modify. A Domain or a Business Process is a collection of securable items
(Domain) or a specific Business Process type. Business Processes are separately secured from
Domains and Sub-Domains.

Security acts as a bridge between Workday-owned metadata and customer-owned tenanted

access to functionality, Security Groups and Security Policies are in the customer / tenanted
realm, with little developer involvement. Domains reside in the metadata realm, and are off-
limits to customers.

SECURITY LANDSCAPE

Workday has grouped parts of the Workday system into Functional Areas. These functional
areas contain Domains and Business Processes.

A functional area is a collection of related securable items. These items include actions, reports,
report data source or custom report fields. The Functional Areas report will display all
functional areas and included domains and business processes. Functional Areas can be
enabled and disabled for each tenant with the Maintain Functional Areas task.

Domains are pre-defined by Workday and cannot be modified by customers. Workday provides
customers the ability to specify security policies that govern permissions for the content of a
domain. A domain security policy grants a group of users access to the securable items
contained in the domain.

Business Process types are delivered by Workday. You cannot create new business process
types; however you can copy and modify definitions. A business process security policy controls
permissions to tasks and view capabilities for business process types.

BUSINESS PROCESS SECURITY POLICY

Business process security policies are collections of securable items related to business
processes, including initiation steps and step actions. They also are where you specify
permissions for actions on processes: view, approve, rescind, cancel, and correct.

Business process security policies contain such securable items as initiation steps, step actions,
and actions on the process as a whole: view, approve, rescind, cancel, and correct. A business
process security policy also allows you to specify whether the business process can be
delegated to others.

All definitions copied or linked are controlled by the Business Process security policy for the
type.

DOMAIN SECURITY POLICIES

Security Policies are the bridge between Domains and Security Groups. Security Policies are
assigned to Domains by the customer, and are therefore tenanted data. When creating a
Security Policy one of two types of access is granted. View access allows only View type
activities to be performed. Modify access allows both View and Update types of activities to be
performed. For each Domain, the Security Policy specifies which Security Groups may execute
View or Modify (which includes View) the Domain's Tasks. If a Security Group has no
permissions listed in the Security policy, by definition that Security Group has no access rights
to any of that Domain's content.

Sub-domains automatically inherit their super-domain's security policy; changing the policy on
the sub-domain automatically overrides the super-domain's policy, and cascades to any sub-
domains of the sub-domain.

The following graphic outlines the steps for configuring security. Users are added to or removed
from security groups. In many instances, new security groups will be created to meet your
needs. There are several types of security groups. You cannot create new types. Security groups
are added to or removed from security policies. When changes are made to a security policy,
those changes are saved, but are pending until the Activate Pending Security Policy Changes
task is run. Once you activate those changes, Test, Test, and Test!
HOW CHANGE CONTROL WORKS

Four elements make Workday security policy change control possible:

 Workday records the time of every security change.

 Workday evaluates security as of a timestamp, ignoring later changes, which are "pending."

 You can activate pending changes by time-stamping your current security configuration.

 You can tell Workday Security to activate a previous timestamp.

When you tell Workday Security to use a timestamp as the security evaluation moment,
changes made after that timestamp don't take effect until you activate them. Use the Activate
Pending Security Policy Changes task to create a new, current timestamp.

For example, if you activate security policy changes in March, June, and September and then
discover a serious error in the September security configuration, you can activate the March
timestamp using the Activate Previous Security Timestamp task. The changes from June and
September are considered pending changes along with whatever new changes you make to fix
the problems with the September security configuration. When you run the Activate Pending
Security Policy Changes task, it creates a new timestamp and activates all of the changes made
since March.

Workday no longer allows you to activate the September timestamp, which it deems a bad
configuration. It appears in the View All Security Timestamps report, but no longer appears on
the list for activating previous timestamps. We recommend that you edit the timestamp
comment to indicate that it is not a valid security configuration.
Security timestamps look at domain and business process security policies and functional areas.
They include changes made by adding or removing security groups from policies, enabling or
disabling domains or functional areas, and whether business processes can be delegated.

USER-BASED SECURITY GROUPS

A user-based security group is a group to which you directly add workers as members. When
the security group is used to grant workers permission to access items in a security policy, all
the users in the group have that permission. You can edit and create user-based security
groups.

This is the least restrictive group. It is not context sensitive, in that it makes no attempt to
match the context of the workers in the group (organization or ownership) with the context of
the secured item. Use user-based security groups for administrators who you want to have
global (enterprise-wide) access.

ROLE-BASED SECURITY GROUPS

Role-based security has two types of role-based context, constrained and unconstrained.

Constrained indicates that your access is limited by your relationship to the objects. For
example, access for the HR Partner is limited to the Supervisory Org or Locations that they
support.

Role-Based Security Group (Unconstrained) has no constraint based on organizations you

support. A manager in an unconstrained role-based security group would have security access
to all workers and not just workers in the organizations that they manage. This role is similar to
the user-based security group administrator roles but is dynamic.

JOB-BASED SECURITY GROUPS

Job-based security groups can be defined as either constrained or unconstrained. Membership

is based on criteria related to the job performed. System users in this group can only be
workers since they require job-relevant criteria. The selection will be made from currently
active workers.

CONSTRAINED VS. UNCONSTRAINED INTEGRATION SECURITY GROUPS

 An Integration System Security Group (Constrained) serves the same general purpose as an
Integration System Security Group (Unconstrained). The only difference is that the constrained
group type enables you to filter data results contextually based on Organization. For example,
you can set up an integration that exports data only for workers who are members of a specific
supervisory Organization. Filtering varies depending on how the data is accessed.

SEGMENT-BASED SECURITY GROUPS

A segment-based security group grants access to members of other security groups. It grants
access to selected components (a segment) of the secured item. The security group definition
specifies the segment to which it grants access. That is, you use this security group to control
access to policies whose secured items include components in the segment.

Create integration system users in Workday for scoped HR

Kingston
..

Configure two system user accounts in Workday for integration with the scoped version of HR. One
account is used for inbound integration, and the other is used for outbound integration.
1. Log in to Workday with the account that provides administrative privileges.
2. Create the users and add them to a group by completing the following steps.
a. Search for and open the Create Integration System User task.
b. Configure and save two integration system users.
c. Search for and open the Create Security Group task.
d. In the Type of Tenanted Security Group field, choose Integration System Security Group
(Unconstrained).
e. Enter a group name and click OK.
f. Select the users you created from the Integration System Users choice list and click OK, and then
click Done.
3. Add the integration security group to domains by completing the following steps.
a. Search for domain: manage org and open the Manage: Organization Integration domain.
b. Click the ellipsis (...) next to Manage Organization Information.
c. In the window that opens, point to Domain and select Edit Security Policy Permissions.
d. Under Integration Permissions, add the security group that you created and click OK.
e. Repeat the previous steps to add the security group to the following domains:
 domain: Worker Data: public worker reports
 domain: Worker Data: Current Staffing Information
 domain: Worker Data: gender
 domain: Worker Data: Contingent Worker Assignment Details
 domain: Worker Data: Personal Data
 domain: Worker Data: Worker ID
 domain: Worker Data: Home Contact Information
 domain: Manage: Location
 domain: Manage: Organization Integration
 domain: Organization: Cost Center
 domain: Job Information
4. Add the group to the business processes Contact Change and Name Change by completing the
following steps.
a. Search for contact change and click the ellipsis (...) next to Contact Change (Default Definition).
b. In the window that opens, point to Business Process Policy and select Edit.
c. Under Web Service Request, add the security group that you created and click OK.
d. Repeat the previous steps to add the security group to Name Change.
5. Activate Pending Security Policy Changes by completing the following steps.
a. Search for activate.
b. Click Activate Pending Security Policy Changes.
c. Enter a comment and click OK.

0.Can you pl. tell how the security is being done for Report or integration?

We need to create Integration system User (ISU) and security group. Assign this to ISU to the
Sec group and give the only necessary sec domain access to the created security group created
above. In case of Report: Directly make the ISU as the owner of the report. In case of
integration like Core connector, Studio, please adds the ISU as the workday account by going to
the related actions of the integration system.

Note: We can’t specify any ISU for EIB as we don’t have that options, only we can add it in
report level by making the custom report owner as ISU

1. What is difference Normal WD Account and ISU?

ISU used to have specific security access that exactly needed for the particular
Integration/Report.

Normal WD Account: Used to have all the security based on user profile and roles to perform
their day to day activity

1. What are the two types of security policies in Workday?

Business Process policies and Domain policies

2. What is the use of Domain Security Policies?

With domain security policies, you can modify which group can view or modify items in
a report/task, or GET or PUT transactions from an integration.
3. How do you manage access to integrations?

You need to create an Integration System User and an Integration Security Group. Next, assign
the Integration User to the Integration security group. Then finally, utilize that security group to
add security policy access.

4. How do you apply changes to security policies?

You need to run the Activate Pending Security Policy Changes to apply the security policy
changes.

5. To modify security in Workday, what groups do you need to be a part of?

Security Configurator or Security Administrator.

6. Explain about security policies in Workday

There are two types of security policies in Workday,

Business Process Policy - define which security group can view or modify data within domains
Domain Policy - indicate which security groups can participate in the business process

7. Name the report which is responsible to view all security groups assigned to users?
View Security Group for Users, Reports give the information of all security groups assigned to
particular users.

Compensation
The document contains some steps to enable you to create the Eligibility Rules and the Compensation
Grade, Plan and Packages.

Task 1 – Create Compensation Eligibility Rules

The following 3 Eligibility rules were created:

1. RK1910 All XYZ Motors Employees - For All employees of XYZ Motors
2. RK1910 All XYZ Management – For All Managers (and above) for XYZ Motors

3. RK1910 All XYZ Non-Management – For Non-Management employees

Task 2: Create Compensation Grade
Two Grades need to be created – One for Management and the other for Non-Management.

The Grades must be included in the Job profiles.

1. RK1910 XYZ Management

In the Grade Profiles, the available Eligibility rules: Country – United Kingdom and Country –
United States of America have been used.
2. RK1910 XYZ Non Management
Like the Compensation Grade for XYZ Management, the Eligibility rules: Country – United
Kingdom and Country – United States of America have been used.
Task 3: Create Compensation Plans
New Salary Plan and Car Allowance plan for XYZ Motors have been created.

1. RK1910 XYZ Salary Plan

 2. RK1910 XYZ Car Allowance
Since this Allowance is only for Managers and Above, the Plan Eligibility must be defined. The
Eligibility Rule for All XYZ Management has been used. For the Plan Profiles, the available
Eligibility rules: Country – United Kingdom and Country – United States of America have been
used

Compensation Package Definition:

The Compensation package has been created to include all the Compensation Plans and Grades.