Integration Core

SUPPLEMENTAL GUIDE – W26

This booklet is for the personal use of only the individuals who have enrolled in this specific workday training course. You may make copies
only as necessary for your own use. Any distribution, even within your organization, is strictly prohibited unless workday has authorized such
distribution in writing.

© 2016 Workday, Inc. All rights reserved. Workday, the Workday logo, Workday Enterprise Business Services, Workday Human Capital
Management, Workday Financial Management, Workday Resource Management and Workday Revenue Management are all trademarks of
Workday, Inc. All other brand and product names are trademarks or registered trademarks of their respective holders. Version 26, 2016.17
(April, 2016)
TABLE OF CONTENTS
SUPPLEMENTAL ACTIVITY - Calculated Fields (Design a Rehire Date)........................................................ 3

SUPPLEMENTAL ACTIVITY - Create an Integration System User .................................................................. 5

SUPPLEMENTAL ACTIVITY - Core Connector .............................................................................................. 15

SUPPLEMENTAL ACTIVITY - Change Detection (Part 1) .............................................................................. 17

SUPPLEMENTAL ACTIVITY - Change Detection Running On Day 2 (Part 2)............................................... 26

SUPPLEMENTAL ACTIVITY - Change Detection Scheduling (Part 3) .......................................................... 27

SUPPLEMENTAL ACTIVITY - Fields And Transactions For Change Detection ............................................ 31

SUPPLEMENTAL ACTIVITY - Exploring Reports as a Service ...................................................................... 35

SUPPLEMENTAL ACTIVITY - EIB.................................................................................................................. 41

EIB Data Source Report Details – Show Employee and Senority Range Calculated Field ............................ 42

SUPPLEMENTAL ACTIVITY - Exploring Workday Web Services .................................................................. 52

SUPPLEMENTAL ACTIVITY - Join Knowledge Sharing Group ..................................................................... 55

SUPPLEMENTAL ACTIVITY - Research Customer questions on Workday’s Integration Tools (Blank

Template) ......................................................................................................................................................... 56

SUPPLEMENTAL ACTIVITY - Research Customer questions on Workday’s Integration Tools (Sample

Template) ......................................................................................................................................................... 59

HCM Primer ..................................................................................................................................................... 63

Appendix ........................................................................................................................................................ 71

2
SUPPLEMENTAL ACTIVITY - CALCULATED FIELDS ( DESIGN A
REHIRE DATE)

Scenario: Logan McNeil has been asked to design the WICT CF Rehire Date field to the report. Our definition
of a Rehire for the purposes of this activity is if the Hire Date is not the same as the Original Hire Date. If the
Hire Date is not the same as the Original Hire Date, display the Hire Date as the WICT CF Rehire Date. But, if
the Hire Date is the same as the Original Hire Date, the WICT CF Rehire Date field should be 'blank'.

Use what you have learned from the previous activities to create a Rehire Date Calculated Field as defined
above. Begin by modifying the WICT CF Employee Report by adding the field, Original Hire Date so you can
view both the Hire Date and Original Hire Date in the results.

HINTS:

 If you find yourself using the word “If” to describe a Calculated Field, you most likely need to use an
Evaluate Expression CF.

 Recall from the pyramid that an Evaluate Expression CF needs a “Condition”. The condition needs to
be a T/F field.

 Q: Given the previous two hints, how many CFs are needed?
A: Two

 To handle the requirement of leaving the Rehire Date CF 'blank' for Workers who are not Rehires,
you can use an existing Global field called “Blank Date”.

 This picture shows one of the two CFs:

3
 Add the new field to your Employee report and run. Evelyn Welch should have a rehire date. (end
of Activity)

 If you completed Homework Activity 12, you applied a filter for employees with 12+ years of service.
Remove this filter to conduct this test and include Evelyn Welch's data.

4
 SUPPLEMENTAL ACTIVITY - CREATE AN INTEGRATION
SYSTEM USER

Business Case: You will create a new integration system user and integration security group. You will then
modify the security group to associate the appropriate domains required by the integration system.
Because setting up the correct security is a complex task, in the steps below we will use a simplified trial and
error approach.
This iterative approach begins by collecting a baseline snapshot of the data provided using a developer ID.
Since we are using the Core Connector Worker template, the ISU and ISG are created and assigned the
access rights needed to use the" Get Workers" web service call (see "Get Workers (Web Service)" under the
task "View Security for Securable Item" as well as call to other web services. Also, the ISU needs permission
to run the integration and that is provided through the "Integration Event" domain.
Once rights are assigned, activate the changes with the "Activate Pending Security Policy Changes" task.
This likely is not sufficient to collect all the data in the baseline set. Use the "Test Security for Document
Field Overrides" task to check this. Optionally, test access by running the Integration. If run, no data is
delivered, and the Diagnostic Audit file shows data not eligible to be included in the final output file. This
implies the Eligibility Criterion field may not be accessible.
Once this is corrected, some but all data is included in the output. Identify the missing fields. Find the
Business Object which holds those fields (using the "Business Object Details" report or by going directly to
the business object). Locate the field(s) and open view the security for the field(s). From the Available
Actions item on the field's Domain Security Policy, Edit Permissions and add the ISG to the Integrations
Permissions set.
When all permissions are updated, run the "Activate Pending Security Policy Changes" task to activate these.
Re-run the integration to determine if all the expected data is shown.

1. Before setting up security on the WICT_HCM_Workers integration system, we need output from an
unrestricted run as a reference. This may already be available from the initial runs of the integration.

2. If needed, obtain this file by launching the WICT_HCM_Workers integration system selecting the Full File
checkbox.

Note the number of workers in the output

5
 Notice the fields and the XML file structure for each worker:

3. Search for and select the Create Integration System User task
a. User Name: WICT-HCM-Workers-User
b. Password: Use the same password as that of "lmcneil"
c. Click OK then Done

4. Search for and select Create Security Group task

a. Type of Tenanted Security Group: Integration System Security Group (Unconstrained)
b. Name: WICT-HCM-Workers-Group
c. Click OK
d. Add the Integration System User created in Step 3 and click OK then Done

5. In a new browser tab, search Workday Community for Implement Core Connector Worker, click on the
matching link and locate the Set Up Integration System User Security section to identify the default
required domains.

As you can see, almost 30 domains are needed to access all the standard fields from the Core Connector:
Worker template, not including other Worker fields or new Calculated Fields.

6
However, in the WICT_HCM_Workers integration system we only selected the following fields:
 First Name / Last Name
 Address Line Data / Postal Code / Country
 Email Address
 Business Title
 Worker Type
 Business Site / Business Site Address Line Data / Business Site Region
 Total Base Pay / Base Pay Currency
It is likely that we don’t need access to all the domains to output theses few fields.
Let’s start by giving the ISU the right to launch Integration Systems and the access to most of the Worker’s fields.

7
6. Search, in the tenant, for "View Domain " and select the report.
a. From the report prompt, Select the Integration Event Domain

b. Click OK
c. Using the related actions menu of the Domain, navigate to Domain > Edit Security Policy
Permissions

d. Under Integration Permissions, click on the prompt in the get and put area.
e. Search for wict and select the WICT-HCM-Workers-Group security group and press OK and
Done
Through this action we have granted the ISU the right to launch Integrations Systems
7. Search for "View Domain " and select the report
a. From the report prompt, Select the Worker Data Public Worker Reports Domain (do not type
the colon!)

b. Click OK
c. Using the related actions menu of the Domain, navigate to Domain > Edit Security Policy
Permissions
d. Under Integration Permissions, click on the prompt in the get only area.

8
 e. Search for wict and select the WICT-HCM-Workers-Group security group and press OK and
Done
Through his action we have granted the ISU the access to most of the worker’s data.
8. Search for and select the Activate Pending Security Policy Changes task
a. Enter a Comment and click OK
b. Verify that all the domains for which you have changed the security setup appear in the list.
Select the Confirm check box
c. Click OK.

9. Search for and select the WICT_HCM_Workers integration system

a. Using the related actions menu, navigate to Workday Account > Edit
b. Enter the user, WICT-HCM-Workers-User, in the Workday Account field
c. Click OK twice.

10. At this point we should have rights to access data from the standard Data sections selected. Next, consider if
we have access to data which is NOT part of one of those sections. Specifically, can this integration access
the data referenced in the Field Overrides?

11. To check this, run the "Test Security" option

Using the related actions menu, navigate to Integration Field Override>Test Security. Click OK

12. The response will show the field used for the Eligibility Criterion, "Active Status" and the “User Name” field
are not accessible by the ISU User:

9
 Optionally, test your Integration System User's access rights. Launch the integration system using the Full
File option. Refresh the event until the integration completes and notice the number of workers output:

No workers are included in the output despite having access rights to some Worker data. This implies the
ISU does not have access rights to the Eligibility Criterion field: "Active Status". We can infer this since we
were able to obtain all records on the baseline run (the 367 workers selected). However, they are not
eligible for the output file, as described in the Diagnostic Audit output file.

13. Setting up security for Integration Field Overrides

a. Using the related actions menu of the Active Status field, navigate to Security > View Security.
To preserve the Test Security for Document Field Overrides results, right click to see in new tab

b. Note the domain referenced, "Worker Data: Current Staffing Information". Using the related actions
menu of the Domain column, navigate to Domain > Edit Security Policy Permissions
c. Under Integration Permissions section, click on the add button to create a new row.
d. In that row, check only the “Get” checkbox.
e. In the new “Get” only area, search for wict and select the WICT-HCM-Workers-Group security
group and press OK and Done.

10
 f. Using the related actions menu of the User Name field, navigate to Security > View Security. To
preserve the Test Security for Document Field Overrides results, right click to see in new tab

g. Note the domain referenced, "Workday Accounts” Using the related actions menu of the Domain
column, to navigate to Domain > Edit Security Policy Permissions
h. Under Integration Permissions, click on the prompt in the "Get" only area.
i. Search for "wict" and select the WICT-HCM-Workers-Group security group and press OK and
Done

14. Search for and select the Activate Pending Security Policy Changes task
a. Enter a Comment and click OK
b. Verify that all the domains for which you have changed the security setup appear in the list. Select
the Confirm check box
c. Click OK.

15. From the integration system Related Actions select Integration Field Override>Test Security.

16. The response will show the field used for the Eligibility Criterion, "Active Status" and the “User Name” field
are now accessible by the ISU User:

11
17. Launch the integration system using the Full File checkbox to test your Integration System User and verify
that the integration system has all required permissions. Refresh the event until the integration completes,
notice the number of workers output:

The security issue with the Eligibility Criterion field is resolved. Let’s have a look at the output file itself:

When comparing this output for Logan McNeil with our “non-ISU secured” run, we find that the
Compensation section including the Total Base Pay and Base Pay Currency, fields is missing from the
output
18. Return to the tab or re-run the Business Object Details report
a. Enter Worker for the Business Object and press OK

12
 b. Click on the Field Name column heading, search and select Total Base Pay - Amount and
Total Base Pay - Currency for Value, press Filter
c. Using the related actions menu of each field, navigate to Security > View Security. To
preserve the Business Object Details report results, right click to see in new tab

The Total Base Pay – Amount and Total Base Pay - Currency fields are secured by the same domain:
"Worker Data: Compensation by Organization", so giving access to the domain will enable access to both
fields
d. In one of the View Security for Securable Item tab, use the related actions menu of the Domain
column and navigate to Domain > Edit Security Policy Permissions
e. Under Integration Permissions, click on the prompt in the "Get" only area.
f. Search for "wict" and select the WICT-HCM-Workers-Group security group and press OK
g. In the View Security for Securable Item for User Name, use the related actions menu of the
Workday Accounts Domain column to navigate to Domain > Edit Security Policy
Permissions
h. Under Integration Permissions, click on the prompt in the "Get" only area.
i. Search for "wict" and select the WICT-HCM-Workers-Group security group and press OK

19. Search for and select the Activate Pending Security Policy Changes task
a. Enter a Comment and click OK
b. Verify that all the domains for which you have changed the security setup appear in the list. Select
the Confirm check box
c. Click OK.

13
20. Launch the integration system using the Full File checkbox to test your Integration System User and
verify that the integration system has all required permissions. Refresh the event until the integration
completes, notice the number of workers output and the structure of the output file

The Compensation section including the Total Base Pay and Base Pay Currency fields, previously missing is
now output as expected. The ISU can access all required data.

<END OF ACTIVITY>

14
SUPPLEMENTAL ACTIVITY - CORE CONNECTOR

Scenario: You have been tasked by the Human Resources department to create an integration system that will
pick up changes in a worker’s business title for workers who have a management level of manager or above.
This file will be used to notify the procurement department that new business cards will need to be ordered.

Configure the integration system with the following high level requirements:

 Core Connector Worker (CCW) will be configured to generate the required output file.

 Configure the Integration Field Override Eligibility to use a calculated field that returns true for workers
with a management level of manager or above. (This calculated field will need to be created)

 The following fields (as well as their prior values) should be contained in the output:
o First Name
o Last Name
o Business Title
o Gender - Map the Workday Value to the third party system value. See below.
 Hint: Use the Related Actions item “Configure Integration Maps” under "Integration
System"

Workday Internal External Value

Value
Male M
Female F
Not Declared Other

o Compensation Level - Configure a custom integration service to output an Integration Field

Override with the value of the previously created “WICT CF Eval Comp Level” calculated field.

 Trigger notifications to the Integration Administrator when the “Failed” or “Completed with Errors”
o Subject: “Integration Failed or Completed with Errors”
o Body: “This integration failed or completed with errors. Please follow-up.”

 Configure Sequence generator so the output file follows the pattern described on the following page.

 Since this application is still in a test phase, the output does not yet need to be sent outside Workday

 Run the application, setting the:

o As Of Entry Moment to the default date and time.
o Effective Date to default date and time.
o Last Successful As Of Entry Moment to two days prior to today at 12:00:00 AM.
o Last Successful Effective Date to two days prior to today.

15
  After configuring the integration system and testing with the specified data, make the following additional
configuration test:
o Add the Worker Transaction Log Service and configure with the following setting:
 Subscribe to specific Transaction Types: Title Change – Business Title Change Event
o Re-run the application using the same date parameters as described in the previous run step

 How has the output data changed, if at all? Are there any differences in the two test runs?

Setting Value

Integration System (Core WICT_Business_Title_Change

Connector Worker)

File Output Format Default XML File

Core Connector – Worker WICT_BusinessTitleChange_ monthinyear _ dayofmonth _ year_ Seq.xml

Output File Name Where:

 monthinyear – Two Digit Month i.e. 01, 12

 dayofmonth – Two Digit Day of month i.e. 01, 29
 year – Four Digit Year i.e. 2011, 2012
 Seq - Sequence Number starting beginning from 1.

Integration Attributes Version 25.0 for Web Service calls

Include Prior Values is enabled to display current and prior Business Titles

Test Scenarios  Logan McNeil – Change Business Title to Chief HR Officer, effective
as of the current date.
 Pedro Santiago – Change Business Title to Workforce Planning
Director, effective as of the current date + 1.
 Henry Lynch – Change Business Title to Payroll Operations Director,
effective as of the current date -1.
 Norman Chan – Change Business Title to Senior Staff Payroll
Specialist, effective as of the current date -1.

16
 SUPPLEMENTAL ACTIVITY - Change Detection ( Part 1 )

Business Case: Core Connector Worker has the ability to generate an output file that only shows changed
data within a selected time frame.
To demonstrate the concept of capturing “Current Dated Data”, four workers will be hired and the
integration process run
From the output file generated, students will be able to understand how Change Detection is performed by
looking at the hires included and excluded.
The main steps are:
 Create the Integration System using the Worker Core Connector template.
 Configure Integration Attributes to define how this Integration System will behave.
 Select the Data Fields to include in the output file coming out of the Worker Core Connector
Integration System.
 Hire workers with different effective dates
 Run the integration to see how those effective dates interact with the date criteria selected

TASK #1 CREATE INTEGRATION SYSTEM

Sign in as Logan McNeil (lmcneil)

1. Search "create int sys" and select the link Create Integration System.

2. System Name

Field Name Entry Value

System Name WICT-HCM-Sync
New Using Template Core Connector: Worker

3. Select OK on Configure Integration Services Page

4. Look for an item named Core Connector Worker / Worker Personal Data Section Fields.

17
 5. Select the check box under the section Enabled.

6. Look for an item named Core Connector Worker / Status Data Section.

7. Select the check box under the section Enabled.

8. Also, look for an item called Core Connector Worker / Worker Transaction Log Service.

9. Select the check box under the section Enabled.

10. Click OK

11. Notice the error at the top of the page. We will fix this error next.

Sign in as Logan McNeil (lmcneil)

TASK #2 SETUP INTEGRATION ATTRIBUTES

1. From WICT-HCM-Sync.

2. Click the Related Action of the WICT-HCM-Sync Integration System.

3. Select Integration System -> Configure Integration Attributes.

4. Look for an Attribute named Version.

5. Under Attribute Values, click the + icon. A new row will show up.

6. Click the Prompt next to the field and select latest version.

7. Click OK.

8. Observe the error message box is now gone.

18
Additional items marked as Alerts will still be there.

TASK #3 SET STATIC FILENAME

1. Click the Related Action of the WICT-HCM-Sync Integration System.

2. Select Integration System -> Configure Integration Attributes.

3. Look for an Attribute named Output Filename.

4. Under Attribute Values, click the + icon. A new row will show up.

Field Name Entry Value

Attribute Value WICT-HCM-SyncFile.xml

5. Click OK

TASK #4 SET ELIGIBILITY CRITERION

1. Select Integration System -> Configure Integration Field Overrides.

2. Look for a field named Eligibility criterion.

3. Select the prompt field under the Override External Field column.

Field Name Entry Value

Override External Field Is True (CRF)

4. Click OK

TASK #5 CONFIGURE INTEGRATION FIELD ATTRIBUTE

1. Click the Related Action of the WICT-HCM-Sync Integration System.

2. Select Integration System -> Configure Integration Field Attributes.

3. In the “WICT-HCM-Sync / Worker Personal Data Section Fields” section, look for the item named
Name Data / First Name.

19
 4. Enter the field values.

Field Name Entry Value

Include in Output Check
Maximum Length 15

5. Look for the item named Name Data / Last Name.

6. Enter the field values.

Field Name Entry Value

Include in Output Check
Maximum Length 15

7. In the “WICT-HCM-Sync / Worker Status Data Section Fields” section, look for the item named
Active.

8. Enter the field values.

Field Name Entry Value

Include in Output Check
Maximum Length 1

9. Click OK

Hire Process Overview

Jack Taylor, a manager, will perform the following actions:

1. Initiate and complete 4 hires, one effective in the past, one effective today, one effective tomorrow and
one effective the day after tomorrow.
2. Create the compensation package for each hire

TASK #6 FUTURE HIRE OF A WORKER

Sign in as Jack Taylor (jtaylor) – USE THE SAME PASSWORD AS USED FOR LOGAN McNEIL

Search for Dion – You may have to use the "All of Workday" search category

1. Click on the Related Action off of Dion Jackson’s name. Select Hire > Hire Employee

20
 Field Name Entry Value
Supervisory Organization IT HelpDesk Department (search for IT Help)
Existing Pre-Hire Dion Jackson

2. Click the OK button

3. Complete the hire information (leaving the Work Space field empty):

Field Name Entry Value

Hire Date tomorrow
Reason Select reason New Position - Fill Vacancy
Position IT HelpDesk Specialist
Employee Type Regular (selected as default value)
Job Profile IT HelpDesk Specialist (selected as default
value)
Time Type Full time (selected as default value)
Business Site San Francisco (selected as default value)
Pay Rate Type Salaried

4. The remaining fields (under Additional Information) are not required, so click the Submit button
5. Click the Open button under Next Steps on the confirmation page to Propose Compensation
6. On the Propose Compensation page, click the “Add” button in the under the green ‘+’ for Salary Plans
7. Choose General Salary Plan from the “All Compensation Plans” category.
8. For Amount, enter 60,000.00
9. Leave the default of USD for Currency, and Annual for Frequency
10. Click the Submit button
11. Verify the amount of 60,000.00 USD Annual appears under Salary Plans
12. Click the Submit button. Observe the Process Successfully Completed “check icon” appears.
13. Click the Done button on this “Success! Event submitted” page.
14. Based on the business process defined for the IT HelpDesk Department, the hire is complete.

TASK #7 CURRENT HIRE OF A WORKER

As Jack Taylor (jtaylor)

Search for Jackie

21
 1. Click on the Related Action off of Jackie Wilson’s name. Select Hire > Hire Employee

Field Name Entry Value

Supervisory Organization IT HelpDesk Department
Existing Pre-Hire Jackie Wilson

2. Click the OK button

3. Complete the hire information (leaving the Work Space field empty):

Field Name Entry Value

Hire Date current date
Reason Select reason New Position - Fill Vacancy
Position IT HelpDesk Specialist
Employee Type Regular (selected as default value)
Job Profile IT HelpDesk Specialist (selected as default
value)
Time Type Full time (selected as default value)
Business Site San Francisco (selected as default value)
Pay Rate Type Salaried

4. The remaining fields (under Additional Information) are not required, so click the Submit button
5. Click the Open button under Next Steps on the confirmation page to Propose Compensation
6. On the Propose Compensation page, click the “Add” button in the under the green ‘+’ for Salary Plans
7. Choose General Salary Plan from the “All Compensation Plans” category.
8. For Amount, enter 60,000.00
9. Leave the default of USD for Currency, and Annual for Frequency
10. Click the Submit button
11. Verify the amount of 60,000.00 USD Annual appears under Salary Plans
12. Click the Submit button. Observe the Process Successfully Completed “check icon” appears.
13. Click the Done button on this “Success! Event submitted” page.
14. Based on the business process defined for the IT HelpDesk Department, the hire is complete.

TASK #8 PAST DATED HIRE WORKER

As Jack Taylor (jtaylor)

Search for Andrew

1. Click on the Related Action off of Andrew Shea’s name. Select Hire > Hire Employee

Field Name Entry Value

Supervisory Organization IT HelpDesk Department

22
 Existing Pre-Hire Andrew Shea

2. Click the OK button

3. Complete the hire information (leaving the Work Space field empty):

Field Name Entry Value

Hire Date 03/24/2015
Reason Select reason New Position - Fill Vacancy
Position Senior IT Analyst
Employee Type Regular (selected as default value)
Job Profile Senior IT Analyst (selected as default value)
Time Type Full time (selected as default value)
Business Site San Francisco (selected as default value)
Pay Rate Type Salaried

4. The remaining fields (under Additional Information) are not required, so click the Submit button
5. Click the Open button under Next Steps on the confirmation page to Propose Compensation
6. On the Propose Compensation page, click the “Add” button in the under the green ‘+’ for Salary Plans
7. Choose General Salary Plan from the “All Compensation Plans” category.
8. For Amount, enter 60,000.00
9. Leave the default of USD for Currency, and Annual for Frequency
10. Click the Submit button
11. Verify the amount of 60,000.00 USD Annual appears under Salary Plans
12. Click the Submit button. Observe the Process Successfully Completed “check icon” appears.
13. Click the Done button on this “Success! Event submitted” page.
14. Based on the business process defined for the IT HelpDesk Department, the hire is complete.

TASK #9 FUTURE HIRE OF A WORKER – 2 DAYS FROM NOW

As Jack Taylor (jtaylor)

Search for Barry

1. Click on the Related Action off of Barry Sikes’s name. Select Hire > Hire Employee

Field Name Entry Value

Supervisory Organization IT HelpDesk Department
Existing Pre-Hire Barry Sikes

2. Click the OK button

23
 3. Complete the hire information (leaving the Work Space field empty):

Field Name Entry Value

Hire Date 2 days from today
Reason Select reason New Position – Fill Vacancy
Position Senior IT Analyst
Employee Type Regular (selected as default value)
Job Profile Senior IT Analyst (selected as default value)
Time Type Full time (selected as default value)
Business Site San Francisco (selected as default value)
Pay Rate Type Salaried

4. The remaining fields (under Additional Information) are not required, so click the Submit button
5. Click the Open button under Next Steps on the confirmation page to Propose Compensation
6. On the Propose Compensation page, click the “Add” button in the under the green ‘+’ for Salary Plans
7. Choose General Salary Plan from the “All Compensation Plans” category.
8. For Amount, enter 60,000.00
9. Leave the default of USD for Currency, and Annual for Frequency
10. Click the Submit button
11. Verify the amount of 60,000.00 USD Annual appears under Salary Plans
12. Click the Submit button. Observe the Process Successfully Completed “check icon” appears.
13. Click the Done button on this “Success! Event submitted” page.
14. Based on the business process defined for the IT HelpDesk Department, the hire is complete

TASK #10 TEST INTEGRATION PROCESS "WICT-HCM-SYNC"

Sign in as Logan McNeil (lmcneil)

1. Click the Related Action of the WICT-HCM-Sync Integration System.

2. Select Integration -> Launch / Schedule.
3. Launch Schedule Integration page is displayed

Field Name Entry Value

Integration WICT-HCM-Sync
Run Frequency Run Now
Run as Current User Select

24
4. Click the OK button
5. On the “Schedule and Integration” panel provide these parameters:

Field Name Entry Value

As Of Entry Moment Current Date and Time – NOTE THIS FOR
PART 2 OF THE BONUS ACTIVITY!
Effective Date Today’s Date
Last Successful As Of Entry Moment 2 days ago at 12:00:00 am midnight
Last Successful Effective Date 2 days ago
Workers <Blank>
Full File Unchecked

6. Click OK.

7. View Background Process page is displayed.

8. Click the button to refresh the status of the process.

9. The Percent Complete will show the progress each time the Integration Event name hyperlink is clicked.

10. When complete, select the “Output Files” tab and select the “WICT-HCM-SyncFile.xml” file.

11. From the file contents, select which newly hired Worker showed up on the output file.

Worker In Output File? Why?

DION JACKSON
JACKIE WILSON
ANDREW SHEA
BARRY SIKES

25
 SUPPLEMENTAL ACTIVITY - Change Detection Running On
Day 2 (Part 2)

Business Case: This activity simulates a scheduled process running daily. The previous day’s process
picked up some Employees and ignored others. Running the process with a new Launch Parameter dates
should show students who gets picked up and who doesn’t.
Run this one day AFTER running PART (1) of the Bonus Activity

TASK #1 PROCESS HCM-SYNC TO DETERMINE OUTPUT

Sign in as Logan McNeil (lmcneil)

1. Run this Activity 1 day after running “BONUS ACTIVITY PART (1)”
2. Launch the process.

Field Name Entry Value

Last Successful Launch Moment Date and Time of As Of Moment field used on
the previous day’s process. (Saved from Step 5
of Task 11 above)
As Of Moment Current Date and Time
Workers <Blank>
Full File Unchecked

3. List out which newly hired Worker showed up on the output file.

Worker In Output File? Why?

DION JACKSON
JACKIE WILSON
ANDREW SHEA
BARRY SIKES

4. Click the OK button

26
SUPPLEMENTAL ACTIVITY - Change Detection Scheduling (Part 3)

Business Case: Schedule Change Detection and the security requirements associated with it.
Integration Systems are associated with Integration System Users (ISUs) and ISUs are associated with a
Security Group.
Permissions are assigned to Security Groups.
Processes are assigned an ISU and run with the ISU’s security permissions
Scheduling a Process allows the process to run at a scheduled dates and times.
Demonstrate how the process dates should change automatically as the scheduled Process runs.

TASK #1 CREATE INTEGRATION SYSTEM USER

Sign in as Logan McNeil (lmcneil)

1. Search for Create Int Sys User and select the task Create Integration System User.

2. Set Username as WICT-hcm-sync-user

3. Assign a password to this user. Use the same password as that of Logan McNeil

4. Do not check the “Require New Password at Next Sign in”; do not set the “Session Timeout Minutes”
value.

5. Click on “Ok”, then “Close”.

6. Search for Create Sec Group and select the task Create Security Group.

7. Select Integration System Security Group (Unconstrained) under “Type of Tenanted Security
Group”.

8. Set Name as WICT-hcm-sync-grp

27
 9. In the “Integration System User” field, select WICT-hcm-sync-user to associate this Integration
System User with the Security Group WICT-hcm-sync-grp.

10. Click on “Ok”, then “Close”.

11. Refer to SUPPLEMENTAL ACTIVITY - Create an Integration System User, page 5, for a
refresher on how to configure permissions for the security group. Be sure to Activate Pending
Security Policy Changes.

TASK #2: ASSOCIATE THE ISU TO THE INTEGRATION SYSTEM AND TEST

1. Search “view int sys” and select the link View Integration System.

2. Select WICT-HCM-Sync.

3. Select Related Action, Workday Account >> Edit.

4. Select Integration System User WICT-hcm-sync-user

5. Click OK then Done

6. Search for and select the WICT-HCM-Sync integration system

7. Launch the integration system using the Full File checkbox to test your Integration System User and
verify that the integration system has all required permissions. Refresh the event until the
integration completes and verify workers are being output.

TASK #3: SCHEDULE THE WICT-HCM-SYNC INTEGRATION SYSTEM

1. Launch the WICT-HCM-Sync process.

2. Run Frequency – Select Daily Recurrence.

3. Click on “Ok”.

28
 4. Define Request Name. Select “Static Text” option

Field Name Entry Value

Static Text Class-Activity-HCM-Sync-Scheduled.

5. Under Integration Criteria tab

Field Name Value Type Value

As Of Entry Moment Determine Value at Current Moment (Date Time)
Runtime
Effective Date Determine Value at Current Moment (DateTime)
Runtime
Last Successful As of Entry Determine Value at As Of Entry Date & Time of Last Completed
Moment Runtime Integration Event
Last Successful Effective Date Determine Value at As Of Effective Date of Last Completed Integration
Runtime Event
Full File Unchecked

6. Open the Schedule tab

Field Name Entry Value

Start Time 1 hour from current time
Start Date Today’s Date
End Date December 31 of following year

7. Click “Ok”, then “Close”.

29
8. Run the WICT-HCM-Sync process once more, manually, before the next scheduled process will kick-off.

Field Name Entry Value

As Of Entry Moment 3 days ago.
Effective Date 3 days ago
Last Successful As of Entry Moment 4 days ago.
Last Successful Effective Date 4 days ago.
Full File Unchecked

These selections set the starting date and time for the scheduled runs. If the integration has not been run
manually at least one time, the scheduled process will not have a valid “Last successful run” from which to
start.

9. To view the list scheduled processes, including this one, access the Scheduled Future Processes
report.

10. After the scheduled report runs, observe the output file from the “Integration Events” collection under
“Related Actions” and “Integration System”. List below which newly hired Worker(s) appear(s) in the
output file.

Today: <list date here>

Worker In Output File? Why?
DION JACKSON
JACKIE WILSON
ANDREW SHEA
BARRY SIKES

Tomorrow: <list date here>

Worker In Output File? Why?
DION JACKSON
JACKIE WILSON
ANDREW SHEA
BARRY SIKES

2 days from first process run: <list date here>

Worker In Output File? Why?
DION JACKSON
JACKIE WILSON
ANDREW SHEA
BARRY SIKES

11. Analyze your data. What happens and why?

30
 SUPPLEMENTAL ACTIVITY - Fields And Transactions For
Change Detection

Business Case: Fields and Transactions selected in the CCW Integration System affects what is included in
the Change Detection process.
For a data change to be included, three criteria should be met:
1. The data change should be within the date range set as the Process run parameters.
2. The Transaction should occur.
3. A change should have occurred on the selected Field’s data value.

Sign in as Logan McNeil (lmcneil)

Lab Setup:

 Search for the integration system WICT-HCM-Sync.

 Optional: If you would like to leave the WICT-HCM-Sync Integration schedule undisturbed, clone
the integration and perform this Activity on the clone.
 Select Integration System -> Configure Integration Services.
 Look for the Service Worker Status Data Section Fields
o Go to the column marked as Enabled and unselect the checkbox
 Look for the Service Worker Transaction Log Service
o Go to the column marked as Enabled and unselect the checkbox
 Click “OK” and “Close”.

TASK #1 SELECTING DATA CHANGE FIELD FOR CHANGE DETECTION

1. Run the WICT-HCM-Sync process.

Field Name Entry Value

As Of Entry Moment Current Date and Time
Effective Date Current Date
Last Successful As Of Entry Moment Date: 01/01/2011
Time: 12:00:00 am midnight
Last Successful Effective Date Date: 01/01/2011
Workers <Blank>
Full File Unchecked

Worker In Output File? Why?

LEIGH HASTINGS (21057)

31
2. Search “view int sys” and select the link View Integration System.

3. Select WICT-HCM-Sync.

4. Click OK.

5. Select Integration System -> Configure Integration Services.

6. Look for the Service Worker Status Data Section Fields.

7. Select the check box under the column marked as Enabled.

8. Click “OK” and “Close”.

9. Click on Related Action of the WICT-HCM-Sync Integration System.

10. Click on Integration System -> Configure Integration Field Attributes link.

11. Notice how there will be multiple sets of Data Sections on the page.

Pay close attention to the scroll bar to the right of the page as you might need to scroll further down
to see the other Data Section.

12. Scroll down to the Worker Status Data Section Fields

13. Look for a Field Employee Status and click on the check box under Include in Output column.

14. Click “OK” and “Close”.

15. Run the WICT-HCM-Sync process as the current user with the following criteria.

Field Name Entry Value

As Of Entry Moment Current Date and Time
Effective Date Current Date
Last Successful As Of Entry Moment Date: 01/01/2011
Time: 12:00:00 am midnight
Last Successful Effective Date Date: 01/01/2011
Workers <Blank>
Full File Unchecked

Worker In Output File? Why?

LEIGH HASTINGS (21057)

32
TASK #2 SELECTING TRANSACTIONS FOR CHANGE DETECTION

16. Search “view int sys” and select the link View Integration System.

17. Select WICT-HCM-Sync.

18. Click “OK”.

19. Select Integration System -> Configure Integration Services.

20. Look for the Service Worker Transaction Log Service.

21. Select the check box under the column marked as Enabled.

22. Click “OK”.

23. Click on Related Action of the WICT-HCM-Sync Integration System.

24. Click on Integration System -> Configure Integration Transaction Log link.

25. Select the radio button next to Subscribe to specific Transaction Types.

26. Click on the Prompt. Select Hire – Hire Employee Event transaction.

27. Click “OK”

28. Run the WICT-HCM-Sync process as the current user with the following criteria.

Field Name Entry Value

As Of Entry Moment Current Date and Time
Effective Date Current Date
Last Successful As Of Entry Moment Date: 01/01/2011
Time: 12:00:00 am midnight
Last Successful Effective Date Date: 01/01/2011
Workers <Blank>
Full File Unchecked

Worker In Output File? Why?

LEIGH HASTINGS (21057)

29. Go back to Integration System.

30. Click on Related Action of the WICT-HCM-Sync Integration System.

33
31. Click on Integration System -> Configure Integration Transaction Log link.

32. Select the radio button next to Subscribe to specific Transaction Types.

33. Click on the Prompt. Select Termination – Terminate Employee Event transaction.

34. Run the WICT-HCM-Sync process as the current user with the following criteria.

Field Name Entry Value

As Of Entry Moment Current Date and Time
Effective Date Current Date
Last Successful As Of Entry Moment Date: 01/01/2011
Time: 12:00:00 am midnight
Last Successful Effective Date Date: 01/01/2011
Workers <Blank>
Full File Unchecked

Worker In Output File? Why?

LEIGH HASTINGS (21057)

34
SUPPLEMENTAL ACTIVITY - EXPLORING REPORTS AS A SERVICE

Scenario: In this activity you will build an advanced custom report that will be enabled as a web
service to explore some unique aspects of RaaS (Reports As A Service).

Part 1: Create an advanced custom report

1. Create an advanced custom report called WICT_RaaS_Demo using the All Active and
Terminated Workers data source.

2. Include the following fields:

a. Legal Name - Last Name
b. Legal Name - First Name
c. Hire Date
d. SSN

35
3. To enable the report as a web service, edit the report and navigate to the advanced tab. On the
advanced tab, select Enable As Web Service. Shown below is the view once the changes
have been saved.

When you enable a custom report as a web service, Workday generates a unique RaaS
namespace for the report, using the following format:

urn:com.workday.report/Report_Name

In this example, the namespace was defined as urn:com.workday.report/WICT_RaaS_Demo.

This namespace is very important to note, as it is required when using XSLT to transform the
report output.

4. Now that the report has been enabled as a web service, notice that on the columns tab there is
a new setting called Column Heading Override XML Alias as seen below.

36
 The values have been prepopulated for you based upon the fields on the report.

5. Next, let’s take a look at the XML output of the report. To do this, click on the related action of
the report and select Web Service  View URLs. If you are prompted to re-enter your login
credentials to access the Web Service URLs, log in as Logan McNeil.

6. There are multiple versions of the output available, however for the purpose of this exercise,
click on the link labeled Workday XML as seen below:

7. Notice in the XML that the Column Heading Override XML Alias values show up as the
names of the XML elements. Also notice the namespace that is being output in the XML, this
namespace matches the namespace that was generated when the report was enabled as a web
service. (Note that not all browsers display the namespace, Firefox does not, while IE does.)

37
38
 8. To get a better sense of the impact that the Column Heading Override XML Alias setting has,
edit your custom report and set the Column Heading Override XML Alias to the following
values:
a. Last
b. First
c. HireDt
d. Social_Security_Number

9. Following the previous steps, generate the Workday XML and notice the impact that changing
the Column Heading Override XML Alias values has had.

In closing, Workday enables you to expose advanced custom reports as web services that can be
called in an integration. When you enable a custom report as a web service, Workday generates a
unique RaaS namespace and provides settings to customize the XML that is output by the report. To
dig a bit deeper, here are a few questions to research.

1. What happens to the RaaS namespace if you change the name of the report? ______________
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________

2. Can you change the RaaS namespace? How did this change impact the output XML? _______

39
 ____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________

3. Are there any special considerations when specifying the Column Heading Override XML
Alias values? Are there any characters that aren’t allowed? ____________________________
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________

4. What is the impact on the XML if you include an RBO (Related Business Object) on the report?
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________

40
SUPPLEMENTAL ACTIVITY - EIB

Scenario: You have been asked to create a new CSV file from an EIB. The file will be used in an employee
benefits integration application. It will be used to help determine what type of service award should be given to an
employee on the anniversary of his or her hire date. The file should display the employee’s name and seniority
per the requirements defined below. The seniority rank will be a new Calculated Field defined as follows:

If the employee’s Hire Date is more than 10 years ago (from today’s date), show “10+ years” in the
seniority field,

Else if between 5 and 9 years ago (from today’s date), show “5-9 years” in the seniority field,

Else if between 1 and 4 years ago (from today’s date), show “1-4 years” in the seniority field,

Else if less than 1 year ago (from today’s date), show “less than 1 year” in the seniority field

Else show ‘unexpected error’

Design your calculated field (Seniority) from the top down and build it from the bottom up with needed pre-
requisite fields.

Details about how to build the report follow in the "EIB Data Source Report Details" section

As you construct the report, remember:

 Configure the Custom Report it with the ultimate goal in mind.

 Since you need to create an EIB-based integration from this report, you may need to include a setting that
allows the report to be used by an EIB web service.

 The CSV output will have the names of the respective columns included in the first line of the output.
Label the column that includes the seniority range “Seniority”.

 Since this application is still in a test phase, the output does not yet need to be sent outside Workday.

Once you run the EIB and view the output, there may be an issue:

 It contains a few rows where the Employee column is blank.

The customer is concerned about that. She asks:

 Why does that happen?

 How can I be sure that the data only lists workers who are actual GMS employees?

How would you adjust the integration to address these questions? (You don’t need to implement solutions now,
but consider these questions and be prepared to discuss possible ways to answer them.)

41
EIB Data Source Report Details – Show Employee and Senority
Range Calculated Field

Scenario: Logan McNeil has been asked to create a new employee report showing the employee’s seniority
per the requirements defined below. The field “Seniority” will be a new Calculated field defined as follows:
If the employee’s Hire Date is more than 10 years ago (from today’s date), show “10+ years” in the
seniority field,
Else if between 5 and 9 years ago (from today’s date), show “5-9 years” in the seniority field,
Else if between 1 and 4 years ago (from today’s date), show “1-4 years” in the seniority field,
Else if less than 1 year ago (from today’s date), show “less than 1 year” in the seniority field
(else show ‘unexpected error’)
Remember to design your calculated field (Seniority) top down and build it bottom up with needed pre-
requisite fields.

CREATE A NEW CUSTOM REPORT

 Run the Create Custom Report task and create a new report as follows:

Field Name Entry Value

Report Name WICT CF Employee Seniority Report

Report Type Advanced

Data Source All Workers

Web Service Enable Checked On

Click the OK button to initiate the Report Writer editing page.

Add the fields by clicking on the add row icon:

a. Employee
b. Hire Date

Click OK to save your report and Run the report. Note the range of hire dates.

42
DESIGN YOUR CALCULATED FIELD(S) (ANSWERS ON THE FOLLOWING PAGE IF NEEDED)

What Calculated Field function does the Seniority calculated field need to ultimately use?

What pre-requisite calculated fields do we need?

Any Constants?

Any True/False Conditions?

Any other Calculated Fields?

43
DESIGN QUESTION AND ANSWERS

 What Calculated Field function does the Seniority calculated field need to ultimately use?

Answer: Evaluate Expression

 What pre-requisite calculated fields do we then need?

Any Constants?
o Answer: 5 Text Constants (Global):
 “10+ years”
 “5-9 years”
 “1-4 years”
 “less than 1 year”
 “Unexpected Error” (for the default condition)
Any True/False Conditions?
o Answer: 4 True/False Conditions:

 Date Difference (in years) between Employee’s Hire date and Today is greater than or
equal to 10

44
  Date Difference (in years) between Employee’s Hire date and Today is greater than or
equal to 5 AND less than or equal to 9

 Date Difference (in years) between Employee’s Hire date and Today is greater than or
equal to 1 AND less than or equal to 4

 Date Difference (in years) between Employee’s Hire date and Today is less than 1

Any other Calculated Fields?

 Date Difference (in years) (Today – Hire Date)

Note: The numeric constants 10, 9, 5, 4, and 1 exist as Global in the tenant.
Now, build your calculated fields from the bottom up:
- Create your Global Text Constants
- Create your Date Difference field*
- Create your True/False Conditions*
- Create the Seniority Calculated field using Evaluate Expression*
*Though the report is based on the Employee Business Object (All Active Employees data source), it is best
to create the needed Calc Fields on the Worker BO (higher level) so that the Calc Fields will be easily
available from both the Worker and Employee Business Objects and data sources.

If you need detailed steps, the next few pages will walk you through the steps. We encourage you
to try this activity using only the design steps above to enforce your learning.

45
CREATE YOUR GLOBAL TEXT CONSTANTS

Select the Create Calculated Field task.

 Define the field as follows:

Field Name Entry Value

Field Name WICT CF 10+ years

Business Object Global

Function Text Constant

 Enter value: “10+ years”

 Click OK.

 Create Another Calculation (or Copy the calculated field you just saved)

 Define the field as follows:

Field Name Entry Value

Field Name WICT CF 5-9 years

Business Object Global

Function Text Constant

 Enter value: “5-9 years”

 Click OK.

 Create Another Calculation (or Copy the calculated field you just saved)

 Define the field as follows:

Field Name Entry Value

Field Name WICT CF 1-4 years

Business Object Global

46
 Function Text Constant

 Enter value: “1-4 years”

 Click OK.

 Create Another Calculation (or Copy the calculated field you just saved)

 Define the field as follows:

Field Name Entry Value

Field Name WICT CF less than 1 year

Business Object Global

Function Text Constant

 Enter value: “less than 1 year”

 Click OK.

 Create Another Calculation (or Copy the calculated field you just saved)

 Define the field as follows:

Field Name Entry Value

Field Name WICT CF Unexpected Error

Business Object Global

Function Text Constant

 Enter value: “Unexpected Error”

 Click OK.

CREATE YOUR DATE DIFFERENCE

Create Another Calculation

Define the field as follows:

47
 Field Name Entry Value

Field Name WICT CF Date Difference Hire Date to

Today

Business Object Worker

Function Date Difference

 Configure as follows:

a. Start Date: Hire Date

b. End date: Today

c. For value returned, select ‘in years’

 Click OK.

CREATE YOUR TRUE/FALSE CONDITIONS

Create Another Calculation

Define the field as follows:

Field Name Entry Value

Field Name WICT CF 10+ years TF

Business Object Worker

Function True/False condition

 Click OK.

 Configure the calculation as follows:

48
 Click OK.

 Create Another Calculation

Define the field as follows:

Field Name Entry Value

Field Name WICT CF 5-9 years TF

Business Object Worker

Function True/False condition

 Click OK.

 Configure the calculation as follows:

 Click OK.

 Create Another Calculation

Define the field as follows:

Field Name Entry Value

Field Name WICT CF 1-4 years TF

Business Object Worker

Function True/False condition

 Click OK.

 Configure the calculation as follows:

49
  Click OK.

 Create Another Calculation

Define the field as follows:

Field Name Entry Value

Field Name WICT CF less than 1 year TF

Business Object Worker

Function True/False condition

 Click OK.

 Configure the calculation as follows:

 Click OK.

CREATE YOUR EVALUATE EXPRESSION

Create Another Calculation

Define the field as follows:

Field Name Entry Value

Field Name WICT CF Seniority

50
 Business Object Worker

Function Evaluate Expression

 Click OK.

 Configure calculation as follows:

ADD YOUR CALCULATED FIELD TO THE REPORT AND TEST

Add field to report and test. Use the Report Filter (available on the "funnel" icon) to help to determine if
workers are selected in the correct ranges.

51
SUPPLEMENTAL ACTIVITY - EXPLORING WORKDAY WEB
SERVICES

Business Case: To become familiar with the services available in Workday and their security policies, login to
your tenant and view the Public Web Services.

Sign in as Logan McNeil (lmcneil)

TASK 1 VIEW PUBLIC WEB SERVICES IN THE TENANT

 Search for 'Public Web' in your tenant.

 Select Public Web Services from the Report results.

 Review the list of available web services.

TASK 2 VIEW THE WSDL

Use the related actions menu off of Staffing to navigate to Web Service >> View WSDL (a new browser
window will open)

 Using the browser Find, search for 'Hire Employee'. Click "Enter" three times. What is the
description of this web service operation?
________________________________________________________
This web service operation is designed to hire an existing applicant into an Employee position, headcount, or job using the Hire Employee
business process
 Close that browser window.

TASK 3A VIEW SECURITY FOR HIRE EMPLOYEE WEB SERVICE

 Return to your main browser window and use the related actions menu off of Staffing to navigate to
Security >> View Web Service Operations Security Groups

 Scroll down the list of operations and review Hire Employee

 Which Security Groups are needed?

___________________________________________________________________________
HR Administrator, HR Partner, HR Partner (By Location), HR System, Implementers, Information Administrator, Recruiting System

__________________________________________________________________________

 Is this Hire Employee Web Service secured under domain security or business process security?
_____________
Business Process

 Search for 'view security for securable item' and run the report

 In the Domain Item prompt, search for Hire Employee

52
  Select Hire Employee (Web Service) (Web Service Task) then click OK to run the report

 Review the results (another way to view security required for this web service operation)

TASK 3B VERIFY LOGAN MCNEIL COULD LAUNCH AN INTEGRATION USING THE HIRE
EMPLOYEE WEBSERVICE

 Search for Logan McNeil and select the Employee Object from the Business Data tab

 Use the related action menu to navigate to Security Profile >> View Security Groups
* use the Filter icon in the report to look for the security groups needed to initiate the Hire Employee
business process.

 Does Logan have access? _____________________________________

Yes

TASK 4A VIEW SECURITY FOR THE ADD WORKDAY ACCOUNT WEB SERVICE

 Return to your main browser window and use the related actions menu off of Human Resources to
navigate to Security >> View Web Service Operations Security Groups

 Scroll down the list of operations and review Add Workday Account

 Which Security Groups are needed?

___________________________________________________________________________
Corporate Directory System,Implementers, Security Administrator, Security Partner, WICT-hcm-sync-grp, WICT Security Group

__________________________________________________________________________

 Where is the Add Workday Account secured: domain security or business process security?
______________
Domain

 Search for 'view security for securable item' and run the report

 In the Domain Item prompt, search for Add Workday Account

 Select Add Workday Account (Web Service) (Web Service Task) then click OK to run the report

 Review the results (another way to view security required for this web service operation)

TASK 4B VERIFY LOGAN MCNEIL COULD LAUNCH AN INTEGRATION USING THE

ADD WORKDAY ACCOUNT WEBSERVICE

 Search for Logan McNeil and select the Employee Object from the Business Data tab

 Use the related action menu to navigate to Security Profile >> View Security Groups
* use the Filter icon in the report to look for the security groups needed to launch an integration
using the Add Workday Account web service

53
 Does Logan have access? _____________________________________
Yes

54
SUPPLEMENTAL ACTIVITY - Join Knowledge Sharing Group

Note: The “Professional Services – Integration” Knowledge group provides consultants with key information
important to integration implementations. This is a private group. Therefore, customers do not have access
to this page. Students should join this group and add the knowledge sharing session calls to your calendar.

TASK #1 ADD “WORKDAY INTEGRATION” AS AN AREA OF INTEREST

Sign into Workday Community

1. Click on your account link in the top right corner

2. Check if “Workday Integration” is an area of interest

a. If not, click on the edit tab and go to the area of interest tab

i. Check the box for Workday Integration

ii. SAVE

TASK #2 VERIFY MEMBERSHIP IN THE “PROFESSIONAL SERVICES – INTEGRATIONS”

GROUP

Go to Collaborate > Groups > My Groups

1. Check to see if “Professional Services – Integration” is listed

Task #3 add knowledge sharing sessions call to your calendar

Click on the “Professional Services – Integration” hyperlink

1. Click on the “Integrations KSS.ics” attachment

2. Go to your external email and look to see if an entry

55
SUPPLEMENTAL ACTIVITY - Research Customer questions on
Workday’s Integration Tools (Blank Template)

General Information
Consultant Name: <Enter your name >

Consultant Company: <Enter your company’s name >

Workday Product Version: Workday XX

Customer Issue

<Enter your customer’s issue >

Consultant Research Summary

<Enter a high level summary of your response/answer to customer’s issue >

56
Consultant Research Detail-Test Objects

Name of Test Objects Tenant Description Navigation

Consultant Research Detail-Source Documentation

Source Navigation/Links Comments

57
Consultant Research Detail-Screenshots

Screenshot 1

<Paste Screenshot>

Screenshot 2

<Paste Screenshot>

58
SUPPLEMENTAL ACTIVITY - Research Customer questions on
Workday’s Integration Tools (Sample Template)

General Information
Consultant Name: Harry Potter

Consultant Company: Hogwarts Consulting

Workday Product Version: Workday 25

Customer Issue

How do I create a simple custom report in Workday?

Consultant Research Summary

To create a simple report do the following:

 Search for the task “Create Custom Report”

 Enter the Report Name
 Select “Simple” as the Report Type
 Enter your data source (i.e. All Active and Terminated Workers)

59
Consultant Research Detail-Test Objects

Name of Test Objects Tenant Description Navigation

Login as Logan McNeil and

search for the custom
Test_Simple_Report GMS Created simple report
report
“Test_Simple_Report”

Consultant Research Detail-Source Documentation

Source Navigation/Links Comments

Custom Reports and Analytics >Define

Workday Online User Guide
Simple Reports

60
Consultant Research Detail-Screenshots
Screenshot 1

61
Screenshot 2

62
HCM PRIMER

Supervisory Organization
The primary organizational structure within Workday is the supervisory organization, which designates who
reports to whom. Workers are grouped and tracked within supervisory organizations. Other organizational
structures can be put into the system to represent multiple organization views, but the primary structure is the
supervisory organization.

There are a number of key characteristics unique to a supervisory organization:

 Employees can only be hired into a supervisory organization.

 Organizational roles have responsibilities within a supervisory organization.
 Unique business processes can be assigned to a supervisory organization.

ORGANIZATION SET UP DATA

At least one location must be entered into the system prior to creating a supervisory organization because
Location is a required field when creating a supervisory organization. A location represents:

 A physical location.
 Address, email, and any associated phone numbers.
 Time Profile—defines the standard number of hours worked in that location each week. Usually this is 40
hours (8 hours per day), but in locations such as Paris the work week might be defined as 35 hours. The
time profile is created prior to creating the location.

63
Defining Business Processes
Workday's Business Process Framework lets you define and implement business processes to suit the way a
customer’s company works. You choose the tasks that compose a business process, who must complete them,
and in what order they must be completed. You can create different versions of the same business process for
different organizations. You can define custom business processes for any supervisory organization. The
business process logic is inherited, so subordinate organizations automatically use a business process defined for
a superior organization, unless the subordinate organization has its own version of the process.

The Business Process Framework uses roles to control who performs the tasks that make up a business process.
Because tasks are associated with specific roles, and not with specific people, workers can move into and out of
those roles without disrupting the business process logic.

Business Process Definitions determine:

Business processes are created using a combination of Actions, Approvals, Approval Chains, To Dos, and/or
Checklists. An Action can be a single task or it can be a sub process which is also a combination of Actions, To
Dos, and/or Checklists. Within the process, conditions can be defined which will define whether a step will be
initiated. Notifications can also be defined to notify a Workday user that a step has begun, completed, or that a
particular review response was selected, e.g., Deny.

The difference between Actions, Approvals and To Dos:

 Action – Tasks or event within Workday

 Approvals – Approval of a task or event within Workday
 To Do – Reminder to do something that happens either inside or outside of Workday

For our class, we recommend you create a business process with only an initiation step when testing. See
below:

64
Security Groups
Workday data is accessible only through the configurable security structure that is enforced by the Workday
Object Management System (OMS). No Workday user can view data that is not granted with his or her security
group. For example, a person in the Security Administrator security group can grant passwords to gain access to
the Workday system, but the Security Administrator cannot see compensation data unless he or she also has the
role of Compensation Partner.

Roles are also used to drive business process management. With Workday, you can configure which security
groups and roles participate in a business process, and which security groups can grant access to tasks and
reports.

Rules of security groups:

 Assigned two ways:

o Security groups can be assigned by the system based on a process
o Security groups can be assigned manually

Security groups:

 Control what you can do

 Control what you can access
 Are used in business processes

SECURITY GROUPS AND WORKERS

A security group is a collection of system users. Users can either be grouped explicitly (user-based security
group) or by deriving group membership from other relevant information about the user. The types of security
groups are:

 User-based
 Job-based
 Role-based (constrained)
 Organization Membership
 Location Membership
 Aggregation
 Intersection
 Segment- Based
 Integration System (constrained)
 Integrations System (unconstrained)

65
Create Applicants/Pre-Hires
The hire process is initiated off of an applicant record. If you chose to manually enter your applicants, you can
enter contact information such as name, address, phone, and email address. Things to know when entering an
applicant:

 An applicant must have at least one piece of contact information: a phone number, email address or a
street address.

 Applicant status applies to a specific position, not the applicant as a whole.

66
Staffing Models and the Hire Process
We will briefly review staffing models, which are used, at their simplest, to determine how positions are defined
and filled, provide different levels of control over staffing, and support different staffing goals. Every supervisory
organization must be associated with a single staffing model. This chapter provides specific information about the
differences between the two primary staffing models available within Workday.

Position Management

Job Management

67
Staffing Models and the Hire Process
A position consolidates key job information, such as job family, job profile, worker type and location, as well as
whether the worker is full-time or part-time. You may also define required qualifications, experience, and
education level for positions.

The two primary types of staffing models are Position Management and Job Management. Each of these staffing
models provides a different level of control over staffing and supports different staffing goals.

Position Management:

 A single position is created to be filled

 Hiring restrictions are established
 To hire, promote, demote, or transfer into a position, the position must be approved and available as of
the worker’s start date
 Positions remain open after a transfer, demotion, promotion or termination
 Positions can be moved from one supervisory organization to another as part of a job change
 A position must be closed if it is no longer needed

Job Management:

 Hiring restrictions are established

 No quantity is defined
 Position no longer exists after a worker is transferred, demoted, promoted or terminated unless moved
with the employee

Hire Process
Hiring an employee includes recording information about the worker, assigning the worker to a position or job and
defining terms of employment such as location, hours or compensation. When hiring, you can use an Existing
Pre-Hire or add a new applicant. Either way, you have an opportunity to record applicant source information.

Information required to complete an employee hire includes:

 Hire Date  Time Type (full or part time)

 Position  Location
 Job Profile  Scheduled Weekly Hours

68
Quick Sheet of Key HCM Tasks

 NOTE: Please be aware that there are Open Positions in the Global Modern Services organization. You may be able to
use these for testing, etc. Run the Open Positions Report to review them.

 Creating an Applicant
1. Type “Create Applicant” task in the search bar
2. Enter all required information (i.e. name and at least 1 piece of contact information)
3. Click the submit button

 Creating a Supervisory Organization

1. Type “Create Supervisory Organization” task in the search bar
2. Choose the reorganization event “Initial Implementation (01/01/2000)”
3. Enter all required information
4. Enter an Organization Name
5. Choose any organization subtype
6. Choose any organization visibility as “Everyone”
7. Choose either “Position Management” or “Job Management” staffing model
8. Click the submit button
9. Assign the necessary role based security (i.e. manager, HR Partner etc..)
Click on the related action Roles>Assign Roles

 Creating a Position (Position Management Staffing Model)

Note: This task invokes a business process. For this class ONLY, we recommend you use a business process with just an
initiation step. You may have to strip an existing business process or create a new one.

1. Type “Create Position” task in the search bar

2. Select your Supervisory Organization
3. Enter all required information. For this class ONLY, the availability and earliest hire date should be set to 01/01/2000.
4. Click the submit button

 Setting Hiring Restrictions (Job Management Staffing Model)

Note: This task invokes a business process. For this class ONLY, we recommend you use a business process with just an
initiation step. You may have to strip an existing business process or create a new one.

1. Navigate to your Supervisory Organization

2. Click on the related action button and choose Organization> Set Hiring Restrictions
3. Enter all required information. For this class ONLY, the availability and earliest hire date should be set to 01/01/2000.
4. Click the submit button

 Hire Employee
Note: This task invokes a business process. For this class ONLY, we recommend you use a business process with just an
initiation step. You may have to strip an existing business process or create a new one.

1. Navigate to your Supervisory Organization

2. Click on the related action button and choose Hire > Hire Employee
3. Choose an Existing Pre-Hire or create a new applicant

69
4. Enter all required information.
5. Click the submit button

70
APPENDIX

 8 Steps to Building A Connector

 Change Detection two conditions

 What the Dates mean

 Change Detection Terminology Inconsistencies

 Change Detection Flowcharts

 Troubleshooting Core Connector

 Key Resources and Links

71
72
73
74
75
76
77
Key Resources and Links
Learn On-Demand (Security)

 Search for the course names in the Learning Center

o Configurable Security Overview (2 minute overview)
o Integration Security Overview (10 minutes)
o Application Security Training (7 course series)

Workday Community (Security)

 Security-related Presentations from Workday’s annual Professional Services conference, Altitude

(recordings):
o Introduction to Configurable Security - https://community.workday.com/node/43538
o Integration Security Deep Dive - https://community.workday.com/node/62925
o Integration Security References on Community:
 Workday Documentation: Security for Integrations -
https://community.workday.com/doc/itadmin/dan1370797425079_sh-13_sh-13
 Integration Security Cheat Sheet -
https://community.workday.com/services/tools/61938
 Integration Security – Basic
https://community.workday.com/services/tools/62595
 How to exempt ISUs from password expiration
https://community.workday.com/services/tools/60494

Workday Community (General Links)

• Deployment Guide: https://community.workday.com/private/pro-services/Default.htm

• Delivery Assurance Integration Approach Review Workbook

https://community.workday.com/services/tools/85402

• Integration Approach FAQ https://community.workday.com/services/tools/84051

• Delivery Assurance Integration Build Template

https://community.workday.com/services/tools/60055

• Glossary of Terms Acronyms for Integration Consultants

https://community.workday.com/services/tools/109469

• Issue Resolution Guide: https://community.workday.com/services/tools/88553

78