Integration Core - Exam 1

Overview:
This exam tests your skills at developing scheduled, Core Connector integrations. To be successful, you must:

• Build two Core Connector Integrations to deliver specific, formatted Worker data
• Use CCW Change Detection services to select appropriate data for each of the integrations
• Build and apply XSLT transformations
• Use the specified names and test data for the required artifacts
• Construct the output integration files to conform to the defined formats
• Schedule the execution of the integrations at the specified times
• Direct the integration output to the specified targets
• Use the test data provided and submit your results in the supplied spreadsheet

Your instructor will advise you about the due date of the exam. Please use this link to help convert that time to
your local time: http://www.timeanddate.com/worldclock/converter.html

The details for completing the exam are below. It models the format of an integration specification you may be
given on a project

Page 1 of 16
Name: INT-002, Security Updates for New Workers
Client: Global Modern Services Corporation

Interface: Workday to Microsoft Active

Directory Server
Overview
Workday is Global Modern Services’ system of record for Worker data. When new Workers are added to
the Workday HCM system, the corporate security system must be informed so that security accounts can be
created for those workers.

An integration system must be built to feed data about new Workers to a Microsoft Active Directory
Kerberos Server called Kerbie. This integration is not direct. The Workday system will deliver the data to
an SFTP server location and the AD system will retrieve the data from there. This data is used by Kerbie to
create Active Directory security accounts for the new workers

The integration application must subscribe to new hire events through the Core Connector Worker Change
Detection process for New Hire Events. When it runs, it will collect appropriate data about the new hires,
collect that data into a formatted text file and send it to the designated SFTP server.

A new hire record for the current hire network account file will be created by the Core Connector Worker
integration process when a Worker is active within the Entry/Effective date selection range specified on
the integration run.

For example, if a new hire was entered in the past (Past-Dated) in Workday and activated, the data should
be included in that file, if the entry was within the selection date range. Also, if a new hire and immediately
made an active Worker, that data should show up in the file.

However, if a new hire is set to be active in the future (Future Dated), it should not show up in the file until
that Worker’s effective hire date is reached. As soon as a Future Dated Hire becomes ‘Current’ and Active,
the record should be collected in the next integration run.

The integration will be scheduled to run daily. When used with Change Detection and a properly
configured entry/effective date range, the integration will report data about those new hires which have
become effective in the last day.

Page 2 of 16
 An overview of Integration 1 system components

Technical Description
This section defines how the process should execute

Category Value

Core Connector Worker, Version 25.0

Integration Type
Output File out of Core Connector Worker – XML format, to be input to an
XSLT step for final formatting.
Include data for the workers who have a hire date which has become effective
Data Selection Criteria since the last run of the integration. Since the integration will run daily, this
will select the workers who have an effective hire date within the last day.
Eligibility criterion Is True (CRF)
Daily, including weekends at 4:30 PM, Pacific Time (this can be adjusted to
Schedule coincide with the time the test data was entered), with a unique name for each
output file.
Deliver the integration output to the SFTP folder assigned for your use in this
class.
• Host: sftp://wd2-sales-sftp.workday.net:3022
Integration Delivery
• Directory: /home/<your><name>
• Username: As provided in class
• Password: As provided in class

Page 3 of 16
 The format of the output will be in vertical bar (‘|’) delimited text.

The first row of the output file will be a header row, using the names of the
data fields. This row will also be delimited with vertical bars.

The last row of the output file will be a footer row consisting of the following
two fields that are vertical bar (‘|’) delimited.
File Format • The first field must be a fixed width of 10 characters. Left aligned in
the field will be word ‘COUNT’ (upper-case) while the numeric count of
the records in the file must be right aligned.
• The second field must contain the current date and time of the XSLT
transformation. This timestamp must be brought in dynamically via an
XPath function and not retrieved from the XML output.

An example is included further on in the specification

Document Retention
30 Days
Period

Process Overview
This section defines how the integration will be configured

Category Value

Core Connector
Worker Integration EXAMONE_CCW_HIRE_ACCOUNT
System

Document
Transformation EXAMONE_CCW_HIRE_ACCOUNT_DT
Integration System

DT XTT/ETV File
Name EXAMONE_CCW_HIRE_ACCOUNT_DT_XSL.xsl
Attachment Name

EXAMONE_ HIRE_ACCOUNT_USR – For CCW

Integration System
Users
EXAMONE_ HIRE_ACCOUNT_DT_USR – For DT Integration System

Page 4 of 16
 Process Request
EXAMONE_CCW_HIRE_ACCOUNT – regular scheduled process
Name

File Output Format Text File - “|” - Vertical Bar Delimited, no quotes around the bar

Core Connector –
Worker examone_hire_account.xml
Output Filename

Customization To
CCW Output Yes - Use XSLT to create the formatted text integration file
Required?

(Sequence Generated File name applies to file produced from the DT transformation)

examone_hire_account_monthinyear_dayofmonth_year_hour_minute_seconds_Seq.txt
Document
Transformation where:
Output File • monthinyear - Two digit month i.e. 01, 12
Sequence • dayofmonth - Two-digit day of month i.e. 01, 29
Generated Name • year - Four-digit year i.e. 2011, 2012
Pattern • hour - Two-digit hour of day i.e. 01, 23
• minute - Two digit minutes i.e. 57
• seconds - Two digit second i.e. 49
• Seq – unique sequence number starting from 0 and increment by 1.

Current and Past-Dated Hires should be shown in the output file as it is entered and
approved in Workday.

Future Dated Hires are not included in the file. They are only included when their
Effective Hire Date is reached.
Records to Include
For each Hired Worker matching these criteria, one row will be created in the Kerbie
in Output File
Interface file formatted as defined below.

No other updates done to other Field data on existing Workers should be included in the
output integration file. No other transactions entered will result in a record in the
output file.

Page 5 of 16
 Current and Past-Dated Hires should be shown in the file as they are entered, approved
and are their hires become effective in Workday.

For the first scheduled run –

- Both Current and Past-Dated Hires should be included once in the output file.
o “ExamOne PastDated” will be in the output file
o “ExamOne Current” will be in the output file

- Future Dated Hires will not be included in the file.

o “ExamOne Future” will not be in the output file

For the second and subsequent runs -

Test Scenarios for
- Future Dated Hires should only be included in the file on the day Hire Date
the data supplied
becomes current.
with the exam
o “ExamOne FtoCurr1” will be in the output file, when the Hire Date
becomes effective.
o “ExamOne FtoCurr2” will not be in the output file, and will only be
included once the Hire Date becomes effective.
o Workers reported in previous runs will not be in the output file

Updates done to other data on existing Workers should not be in the output
- Kevin Gibson’s marital status change will not be in the file
- Meg Saunders’ Gender change will not be in the file

Any other transaction will not result in a row in the output file.
- Aidan Mitzner’s termination will not be in the output file

Page 6 of 16
 Interface File Row Record Format
This describes the data sent to Kerbie for each qualifying New Hire. Note the formatting specifications and
the field names. Examples of the header, data and footer row follow.

Column Name Workday Examples of Build Instructions

Description
Field Valid Values

Employee ID value is found under Summary

21001 section of CCW XML output. Fixed Width of
EMPLOYEEID Employee ID Employee ID
22005 10 characters. Must use XSLT to build the
final field.

Legal Name - LOGAN Convert to Upper Case, Fixed Width of 5

FNAME Legal First Name
First Name JACKI characters. Must use XSLT to build the field.

Legal Name - MCNEIL Convert to Upper Case, Fixed Width of 15

LNAME Legal Last Name
Last Name WILSON characters. Must use XSLT to build the field.

If the “User Name” CRF is not empty then

concatenate the string 'ad_' and “User
name”.
“User Name”
Otherwise, concatenate the string 'ad_', the
or,
Username to be First Name’s Initial and the full Last Name.
“Legal Name -
ADUSERNAME created in Kerbie ad_lmcneil In all cases convert the result to lower case,
First Name”
Active Directory ad_jwilson fixed width of 15 characters.
and
System You can achieve this using a calculated field
“Legal Name -
or do it in the Document Transform XSLT
Last Name”
code.
The 'ad_' string may be brought in the XSLT
via an Integration Attribute.

Effective Date Effective Hire Date of Integration Field Attributes  Worker

EFFECTDATE 2016-10-03
of Hire the Employee Status Data Section Fields  Hire Date

Output Example
EMPLOYEEID|FNAME|LNAME |ADUSERNAME |EFFECTDATE|ENTRYDATE
21001 |LOGAN|MCNEIL |ad_lmcneil |2013-10-03|2013-10-03T13:46:48.531
22005 |JACKI|WILSON |ad_jwilson |2013-10-03|2013-10-03T15:05:02.648
COUNT 2|2014-05-12T18:17:52.498-07:00

End of Integration 1 Specification

Page 7 of 16
Name: INT-003, HR Announcements System
Client: Global Modern Services Corporation

Interface: Workday to HR Announcements

System
Overview
Workday is Global Modern Services’ system of record for Worker data. The corporation’s HR department would
like to send a congratulatory note and gift to newly married couples. It wants information about these changes
to come from the Workday system. You must create an integration that will subscribe to Marital Status updates
(via Change Detection) and report those to the SFTP location used in Integration 1 of this Exam.

The data change record will be generated on the Core Connector Worker output file when the scheduled
integration runs. Since this integration runs daily, these changes will be sent to the SFTP address within a day of
the Marital Status data change.

The integration will also send an email notification to you. The notification should be triggered when the
integration completes. The actual email destination must be an account you control. Do not send the message
to any email accounts used in our GMS tenant, including any used by Logan McNeil.

Updates to other Fields in Workday or triggered Events initiation by any other Workday Business Process will not
be included in the output interface file.

NOTE: To narrow the scope of the requirement, any type of change in Marital Status will be included in the
integration output and add a row in the Interface File. This application does not filter on the type of marital
status. All changes, i.e. Married to Single, Single to Married, etc. will be included.

An overview of Integration 2 system components

Page 8 of 16
Technical Description
This section defines how the process should execute

Category Value

Core Connector Worker, Version 25.0

Integration Type
Output File out of Core Connector Worker – XML format.

Include data for the workers who have a marital status change effective since
the last run of the integration.

Since the integration will run daily, this will select the workers who have an
effective marital status change within the last day.
Data Selection Criteria
Updates to other fields will not result in an entry in the output file.

Triggering other Business Processes should not result in entries in the output
file.

Eligibility criterion Select only workers with an “Active Status” of True.

Daily, including weekends at 4:30 PM, Pacific Time (this can be adjusted to
Schedule coincide with the time the test data was entered), with a unique name for each
output file.

Deliver the integration output to the SFTP folder assigned for your use in this
class.
• Host: sftp://wd2-sales-sftp.workday.net:3022
Integration Delivery
• Directory: /home/<your><name>
• Username: As provided in class
• Password: As provided in class

The format of the output will be in an XML document. Each data field will be
File Format
contained in an XML element named after that field.

Document Retention
30 Days (Default Value)
Period

Page 9 of 16
 Add a “Trigger on Status” of “Completed” for the integration. The integration
will send this notification to an email address you use.
Notification
The subject should be “HR Announcements Integration Fired”.
The body should be “HR Marital Status changes have occurred. Check for
announcement events”.

Process Overview
This section defines how the integration will be configured

Category Value

Integration System Name EXAMONE_CCW_DATACHG_MARITALSTATUS – CCW Standalone Server

Integration System User EXAMONE_DATACHGMARITALSTATUS_USR – For CCW

Process Request Name EXAMONE_CCW_DATACHG_MARITALSTATUS

XSLT Customization To
No
CCW Output Required?

examone_datachg_maritalstatus_monthinyear
_dayofmonth_year_hour_minute_seconds_Seq.xml

where:
• monthinyear - Two-digit month i.e. 01, 12
Core Connector – Worker
• dayofmonth - Two-digit day of month i.e. 01, 29
Output File Name
• year - Four-digit year i.e. 2011, 2012
• hour - Two-digit hour of day i.e. 01, 23
• minute - Two digit minutes i.e. 57
• seconds - Two digit second i.e. 49
• Seq – unique sequence number starting from 0 and increment by 1.

Page 10 of 16
 Updates done to Marital Status should appear the output XML file with the next run of
this integration.
- Kevin Gibson’s marital status change will show up in the output file with the
next run after that change is complete.

Updates to other field will not appear in XML output file.

Test Scenarios
- Meg Saunders’ – Gender change will not be in the file.

Triggering other Processes will not result in a row in the output file.
- No new hires will appear in the output file. None of ExamOne PastDated”,
ExamOne Current”, “ExamOne Future”, “ExamOne FtoCurr1” and “ExamOne
FtoCurr2” will be in this output file.
- Aidan Mitzner’s termination will not cause his change to be in the output file.

Page 11 of 16
Interface File Row Record Format
This describes the data sent to Kerbie for each qualifying Marital Status change, in an XML format.

XML Output Data Source Example of

Description Build Instruction
Element Name Field Valid Values

21001 Standard Field found under Summary

Employee_ID Employee ID Employee ID
22005 section of XML output

Legal Name – Legal First Logan

First_Name
First Name Name Jackie

Legal Name – Legal Last Mcneil

Last_Name
Last Name Name Wilson

Calculated Field created by applying

Substring function on Marital Status
CRF. Drop country reference and
return only the status itself (e.g.
CHANGED_MS
WICT CF Married Married, Separated, etc.). Like Day 2,
Element Label in Marital Status
Marital Status Divorced Supplemental Homework Activity and
XML output
like the “Exam 1 – Substring Marital
Status Field.pdf” description. Add to
this integration with a Field Override
Service.

Sample output for Steve Morgan:

<ws:Worker>
<ws:Summary>
<ws:Employee_ID>21002</ws:Employee_ID>
<ws:Name>Steve Morgan</ws:Name>
</ws:Summary>
<ws:Eligibility>true</ws:Eligibility>
<ws:Personal>
<ws:Name_Data>
<ws:First_Name>Steve</ws:First_Name>
<ws:Last_Name>Morgan</ws:Last_Name>
</ws:Name_Data>
</ws:Personal>
<ws:Additional_Information>
<ws:CHANGED_MS>Married</ws:CHANGED_MS>
</ws:Additional_Information>
</ws:Worker>

End of Integration 2 Specification

Page 12 of 16
Page 13 of 16
Exam 1 Integration Test Data
This section defines the final test data used to evaluate this integration. Enter this data when you are confident
your scheduled process is running correctly. Enter it all at the same session – do not spread entry over multiple
hours or days.

These names and dates correspond to the names and dates on the Exam summary spreadsheet you return to
your instructor. See that spreadsheet for directions about collecting the test data. The spreadsheet
accompanies these Exam instructions.

Before you enter this evaluation data, be sure your integration works properly. Be sure your test data will be
picked up by an automatically scheduled process run

Create and test each scheduled process with your own list of test Workers first before entering the final,
evaluation test data.

Each day the scheduled process runs, it should pick up the correct list of Employees listed in these test cases.

Again, the Workers listed below should only be keyed into the tenant when you are 100% confident your
scheduled processes will process and pick up the data correctly in the next process run, and all data should be
entered at the same time.

The test data you enter here is used in the evaluation of both Integrations. The data touches on both exams.
Some items are New Hire events, others are not. Some are changes that appear in one integration file but not
the other. Others should not be included in any integration output.

IMPORTANT: Please use appropriate Tasks for Hires and Marital Status changes. This will insure that these
events are collected in the Transaction Log and available for the change detection process. This is particularly
true for Marital Status changes. These changes will be recorded in the Transaction Log as "Marital Status
Changes" if done by the Worker him/herself with the appropriate change Marital Status task. If changed by
another user (such as Logan McNeil, changing another user’s data) the update may be logged as a Personal
Data Change and NOT as a Marital Status change.

Page 14 of 16
 Test Scenarios Values

Hire Date – 01 June 2016

Past-Dated Hire Employee’s Legal First Name – ExamOne
Employee’s Legal Last Name – PastDated

Hire Date – Today’s Date

Current Hire Employee’s Legal First Name – ExamOne
Employee’s Legal Last Name – Current

Hire Date – 01 December 2017

Future Hire Employee’s Legal First Name – ExamOne
Employee’s Legal Last Name – Future
Hire Date – Today’s Date + 1 Day
Future - Current + 1 Day Employee’s Legal First Name – ExamOne
Employee’s Legal Last Name – FtoCurr1
Hire Date – Today’s Date + 2 Day
Future - Current + 2 Days Employee’s Legal First Name – ExamOne
Employee’s Legal Last Name – FtoCurr2

Data Change – Marital Status Update Kevin Gibson Marital Status

Data Change – Gender Update Meg Saunders’ – Gender

Terminate Aidan Mitzner

Terminate Termination Date – Today
Reason – Voluntary > Unknown
Current and Past-Dated Hires should be shown in the output file as it is
entered and approved in Workday.

For the first scheduled run –

- Both Current and Past-Dated Hires should be included once in the
output file.
o “ExamOne PastDated” will be in the output file
o “ExamOne Current” will be in the output file

EXAMONE_CCW_HIRE_ACCOUNT - Future Dated Hires will not be included in the file.

Records to Include in Output File o “ExamOne Future” will not be in the output file

For the second and subsequent runs -

- Future Dated Hires should only be included in the file on the day
Hire Date becomes current.
o “ExamOne FtoCurr1” will be in the output file, when the
Hire Date becomes effective.
o “ExamOne FtoCurr2” will not be in the output file, and
will only be included once the Hire Date becomes
effective.

Page 15 of 16
 o Workers reported in previous runs will not be in the
output file

Updates done to other data on existing Workers should not be in the

output
- Kevin Gibson’s marital status change will not be in the file
- Meg Saunders’ Gender change will not be in the file

Any other transaction will not result in a row in the output file.
- Aidan Mitzner’s termination will not be in the output file

Marital Status changes should be shown in the output file as they are
entered and become effective in Workday.

For the first scheduled run:

- Updates done to marital status should appear:
o Kevin Gibson’s marital status change will be in the file
- Updates done to other data on existing workers should not
appear:
o Meg Saunders’ Gender change will not be in the file
EXAMONE_CCW_DATACHG o Aidan Mitzner’s termination will not be in the output file
_MARITALSTATUS Records to o New Hires will not be in the output file
Include in Output File
For the second and subsequent runs:
- Updates done to marital status should appear:
o No marital status changes have occurred so output will be
blank.
- Updates done to other data on existing workers should not
appear:
o Meg Saunders’ Gender change will not be in the file
o Aidan Mitzner’s termination will not be in the output file
o New Hires will not be in the output file

End of Integration Test Data Specification

Page 16 of 16