Scribd
Upload
720 views

Core Connectors - Overview

This document provides an overview of Workday Core Connectors and the Core Connector: Worker integration. It discusses how the Core Connector: Worker detects changes to worker data by monitoring a transaction log and exporting changes in XML or CSV format. It also covers how to set up the integration system, configure the transaction log service, and perform document transformations to output data in the required format.

Uploaded by

Haritha
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
720 views

Core Connectors - Overview

This document provides an overview of Workday Core Connectors and the Core Connector: Worker integration. It discusses how the Core Connector: Worker detects changes to worker data by monitoring a transaction log and exporting changes in XML or CSV format. It also covers how to set up the integration system, configure the transaction log service, and perform document transformations to output data in the required format.

Uploaded by

Haritha
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

Core Connectors - Overview

Agenda

• Overview
• Core Connector: Worker
• Document Transformation

• Core Connector : Third Party Payroll


• Core Connector : Benefits
Integration - Overview

• There are three ways to


access the web services
to get and update data
via an integration system
to your Workday tenant.
You may use the
delivered configurable
integrations (Cloud
Connect), the integration
tools to create integration
systems (EIB and
Workday Studio) or your
own existing middleware.
Inbound Integration - Overview
Outbound Integration - Overview
Workday Connectors
• Workday Connectors are pre-built integration templates that extend Workday's
functionality to external systems for Human Capital Management (HCM), Payroll,
Payroll Interface, Financial Management, and Spend Management. All integrations
are hosted and maintained by Workday
• Workday provides two types of Connectors:
‒ End-to-end Connectors support a specific named third party application or service. When a
Connector is deployed, the specific business functions between the two systems are configured with
no additional coding required.
‒ Connectors are pre-built integrations that address the majority of the integration effort required to
connect to third-party end points.
• All Connectors require some level of tenant configuration and testing. Each customer
may have specific mapping requirements and different endpoint configurations.
• These differences in customer configurations can be accommodated with Workday's
integration templates and mapping capabilities.
Core Connector : Worker

• The Core Connector: Worker integration system exports worker data


changes from Workday in simple XML format. Workday also supports
output in CSV (Comma Separated Value) format, with certain limitations.
As you hire, promote, transfer, terminate, or update worker data, the
integration generates a text file containing the changes.
• Using configurable data sections or Workday-delivered report fields and
calculated fields that you create, you can export any worker data, in any
combination.
Change Detection
• The Core Connector: Worker detects changes to worker data by monitoring a
transaction log. When you set up the integration system, you may select which
business processes and transaction types that the integration system should
subscribe to. However, if your integration system does not subscribe to a transaction
type that affects your worker's profile, Workday will not include changes triggered by
that transaction type.
• The Core Connector: Worker integration uses a three-step process to detect and
report changes:
‒ When the Core Connector: Worker integration checks the transaction log, the integration determines
which workers have had changes which resulted in the generation of at least one of the configured
transaction events.
‒ For each worker with a matching transactional change, the integration compares their report fields for
the time at which the integration was run and the time at which it was last successfully run. It
identifies which, if any, of the values of interest have been modified.
‒ If the worker has any changes in field values or eligibility, Workday generates an appropriate creation,
change or deletion message.
Change Detection
• FULL-DIFF Extract
‒ You can configure your Core Connector: Worker integration to select all workers who meet the eligibility criteria, then determine changes for
the returned data.

• Worker Eligibility
‒ For each integration system, you define a group of workers that belongs to the integration system. Membership is defined by a single Boolean
report field or calculated field.

• As Of Entry Moment
‒ The As of Entry Moment launch parameter defines the end of a date range during which changes were entered. This parameter defaults to the
current moment.

• Effective Date
‒ The Effective Date launch parameter defines the end of a date range during which changes became effective. The integration extracts all
changes with effective dates on or before this date. This parameter defaults to the current date.

• Last Successful As of Entry Moment


‒ This launch parameter defaults to the As of Entry Moment (date and time) used in the last successful integration system launch. You can
override this date and time in order to force the integration to search for and retrieve data changes over a wider period.

• Last Successful Effective Date


‒ This launch parameter defaults to the Effective Date (date) used in the last successful integration system launch. The parameter defines the
beginning of a date range during which changes became effective
Activity # 1
a. Create an Integration System
b. Creating the Integration System User and Security Group
c. Launching the Integration system
Transaction Log
• The Transaction Log service enables your integration system to subscribe to events that
take place in Workday. This option enables your integration to first identify a relevant
population of workers that have had the subscribed transaction and then evaluate the data
for those workers.
• If disabled, your integration first extracts all data for all workers, and then evaluates the
data for changes. Using this option can adversely affect performance.
• When configuring the Integration Transaction Log you have the following options available:
‒ Subscribe to all Business Processes
‒ Subscribe to all Business Process Types except.
‒ Subscribe to all Transaction Types
‒ Subscribe to all Transaction Types except
‒ Subscribe to specific Transaction Types
Activity # 2
a. Configure the Transaction Log Service and Launch
Document Transformation

• Document Transformation is an integration system template that enables


you to build an integration that contains a stylesheet attachment that
includes Workday specific processing instructions to transform and
validate documents. The special instructions include:
‒ Validation
‒ Integration Message
‒ Format Text (Non XML)

• The ultimate objective of Document Transformation is to transform the


output of an integration, or the input for an integration, into the required
format.
Activity # 3
a. Fixed Length Transformation
b. Delimited File Transformation

You might also like