Workday Integrations

Workday Integration Cloud

Integration – A Key Deployment Challenge

 Today’s enterprise applications rarely live in isolation

 Integration burden traditionally has rested with the customer (IT)
Complex

Consuming

Costly

 Connectivity is a reality, but should be simpler to build, deploy, and

maintain
 Application vendors should share the burden of responsibility
A Better Way…
 Workday believes in solving more of the integration problem
than any other application vendor.
– Designed from the ground up with interoperability in mind
– Inherent part of the application
 Why Workday for integration?
– Core system-of-record for an enterprise
– Proven integration technology
– Multi-tenant SaaS model
– Inherent understanding of workers, organizations, business
processes, and approval workflows
Workday Integration

 EIB (Enterprise Interface Builder) Created Integrations

 Workday Studio Created Integrations
 Delivered Integrations
Enterprise Interface Builder
 Use the Enterprise Interface Builder (EIB) to build simple and secure integrations
with Workday.
 EIB gives you a framework to build your own integrations based on your unique
business needs. You can use the EIB for both inbound and outbound integrations.
 The integration is represented in Workday as an Enterprise Interface, which you
must build and configure before the integration is ready to launch. You can design
an Enterprise Interface by using either of these methods:
– Wizard design method — Create simple inbound or outbound integrations in a few steps
with the wizard, which guides your setup with appropriate options based on the data
flow.
– Classic design method — Create integrations by building an integration system and then
configuring its components with the Configure Enterprise Interface task. This
approach involves more steps, but gives you additional flexibility.
Enterprise Interface Builder
Integration Type Description Examples
Inbound (import data) •Upload data into Workday by using:An attachment •Import accounting journals into Workday from an Excel
•A REST-based URL spreadsheet that you provide as an attachment.
•A file transfer from an external SFTP, FTP/SSL, or •Import data into Workday from an Excel spreadsheet
FTP location to perform a high volume business process, such as
hiring a group of employees or requesting mass
compensation changes.
•Import expense credit card transactions from card
issuer's external file so that you can process the
transactions in Workday Expenses.
Outbound (export data) •Export data from Workday in a variety of formats, such •Export all active employees from Workday in an Excel
as:CSV spreadsheet and send it to E*Trade Equity Edge with
•Excel SFTP.
•Google Data (GData) •Export employee hours and billing rates from Workday
•HTML in CSV format and send it to Kronos with SFTP.
•JavaScript Object Notation (JSON) •Export employee headcount and contribution data from
•Really Simple Syndication (RSS) Workday in CSV format and send it to a life insurance
•Simple XML provider by email.
•Text files
•Workday XML
•Then send the data to an external system by using
various protocols, such as:Email
•SFTP, FTP/SSL, or FTP
•HTTP/SSL
EIB Integration Components
An Enterprise Interface has four components:

Integration System This is central to creating integrations, of any sort, between Workday and an
external system. An integration system defines an integration in Workday.

Integration Data Source This indicates what kind of data Workday will receive from an external source
(for example, a spreadsheet of business plan data) or will be extracted from
Workday (for example, a particular custom report) and the location of that data
(for example, a specific URL or FTP site).

Integration This converts the data into something that Workday or the receiving external
Transformation system can understand. Workday provides some delivered transformations, but
you can also create your own.

Integration Transport This tells Workday how to import data from or export data to an external
Protocol system, for example, by using email, SFTP, or a web service.
Workday Studio

 Workday Studio is an Integrated Development Environment (IDE) that

you can use to create complex hosted integrations.
– Workday Studio custom integration systems are developed on your
desktop, hosted in Workday's data centers, and accessed by your
production tenant.
 Using Workday Studio on your desktop, you create all aspects of your
custom integration system.
– Once your custom integration system is complete, you then deploy it to
Workday's cloud environment, where it is available to your production
tenants.
Workday Integration Cloud

Workday Cloud
Workday Applications
Public, Web Services APIs Custom APIs

Workday Integration Cloud

Integration Cloud Platform
Integration
Custom Integrations
Cloud Connect

Cloud
Applications On Premise Payroll LDAP/AD
Applications Benefits Providers
Providers
Opening the Integration Cloud Platform

New New
Customers SI Partners

New
Workday
Development ISV Partners
and Services
Workday
Integration Cloud
Platform
Ecosystem Strategy: Targeted Growth

 Continue to add partners in key functional and technology areas

 Invest in technical and development support for partners in building
and supporting integrations
 Measured expansion of Workday Cloud Connect, with increasing
focus on Connectors
Growing Application Partner Ecosystem
Cloud Connect

Where is Workday today?

Where is Workday going?
Integration Cloud Connect
What Is a Packaged Integration?

 Definition
– A pre-built integration offered by Workday to a specific third-party
application
 Key concepts
– Workday/partner relationship
– Supports specific usage scenarios
– Applicable to all Workday/partner customers
– Managed roadmap
– Treated like a product
What Is a Connector?

 Definition
– A pre-built integration product focused on a specific solution
 Key concepts
– NOT built to a specific endpoint
– Supports specific usage scenarios
– Can be extended
– Applicable to all Workday/partner customers
– Managed roadmap
– Treated like a product
Why Isn’t Everything Packaged?

 Partnership issues
– We don’t think it’s worth offering without partner cooperation
 Non-standard third party
– Some applications are highly customizable
– Needs to fit with the SaaS model
 Doesn’t fit strategically
– Needs to complement our applications
– Needs to apply to ALL (or sizeable number) customers
Who Builds This Stuff Anyway?

 Workday integrations are ‘applications’

– Treated like any other application feature
– Follow same methodology
– Follow same delivery
 Dedicated team
– Product management
– Development team
Connector Value Proposition

 Functional domain
– Focus on the use case at hand
– Designed for a particular problem
 Predictable and stable
– Enforce consistency for common patterns
– Common starting point for complex integrations
 It’s a product
– Managed roadmap
– Kept up-to-date with Workday applications
– Always current
How Do Connectors Do That?

 We own one of the endpoints

 We can optimize and simply the Workday process
– Orchestrate APIs
– Implement and enforce best practices
 A good Connector candidate
– Integration complexity is with the Workday part of the equation
– Well-defined problem
 Configurable
– Take advantage of our tooling
 Connectors and the Overall Problem

Complex
VERY
Workday Application
Complexity
SIMPLE

VERY Complex SIMPLE

Target Product Integration Complexity

 Case 1: Pattern-Based Connector
Examples  Cloud Connect for HCM: Worker Sync
 Cloud Connect for HCM: Directory Services
Scenario  Delta sync pattern
 Worker-based changes
Workday  Change detection is complicated
Complexity ‒ Many, many calculated fields
‒ Complex Workday Studio integration
Configuration  Completely define output layout
 Field selection based on Report Data Source
 Configure field order
Extension  Optional, but not usually required
 Case 2: Standards-Based Connector
Examples  Cloud Connect for Financials and Payroll
‒ Electronic Payments

Scenario  Direct deposit and financial payments

Workday  Interact with financial application

Complexity
 Manage multiple payment standards
Configuration  Completely configurable
 Does not require any supplemental steps
Extension  Not required
 Case 3: Domain-Based Connector
Examples  Cloud Connect for Third Party Payroll
‒ Payroll Interface
Scenario  Workday Human Capital Management (HCM) and a
third-party payroll system
Workday  Interact with HCM, staffing, compensation, etc.
Complexity
 Determine what payroll systems needs
Configuration  Highly configurable
Extension  Optional
‒ SafeGuard based on Workday canonical format
‒ Small populations
Extending Connectors

 Functional canonical format

‒ Workday defined structure
 Part of a multi-step process
 Sometimes, but not always!
 Example: ADP PayXpert Payroll Integration

Payroll Secondary Optional Delivery Step

Interface Integration Approval Step

• Produce • Transform to • Approval BP • Deliver to

Configurable PayXpert step payroll
Canonical format system
Cloud Connect for Benefits Framework
Medical,
Dental,
Vision
CCB Core
 Framework
 Core processing
FSA COBRA

CCB  Affects ALL providers

CCB Catalog
Core  Specific functionality
 Conforms to vendor specs
CCB Connector
Life / AD&D Retirement  Abstract CCB core
 Available over the next few updates
Roadmap: Workday 15

 New packaged integrations

‒ Salesforce.com Chatter
‒ Cornerstone OnDemand LMS
‒ AngelPoints
 Updated Connectors
‒ Payroll Interface
‒ HCM Worker Sync / Directory Services
‒ Electronic Payments
Current Roadmap: Workday 16 (subject to change)

 Packaged integrations
‒ Northgate Arinso
‒ Taleo Enterprise
‒ eVerify
‒ Ariba Supplier Network
 Connector enhancements
– Cloud Connect for Benefits
– Enhancing over next few updates
– Look for support for retirement savings next
Roadmap: Future

 Continued packaged integration build-out

 Continued investment in Connectors
– Looking to simplify and reduce implementation time for complex integrations
Q&A / Wrap-up

 Questions?
Integration Cloud Platform
 513 - Integration Cloud Platform

Daniel Beck, Kimberly Kuo

Technology Product Management
Workday Studio
 For complex integrations
Deploy
 Rich, graphical development environment Run

 Deployed and run in the Workday Cloud

Workday
Studio
Build
Case Study: Fairchild Semiconductor
Integration Cloud Key to Workday Decision

20 Studio + 8 EIB integrations = 4 months

 Fairchild significantly reduced implementation time and cost using the Workday
integration platform
 “Businesses like ours require far more than APIs to simplify and improve
enterprise integration. Workday recognizes this and has taken a leadership
position by providing customers with critical access to its core technology.”
– Paul Lones, Fairchild Senior Vice President for IT
Inbound EIB Spreadsheet Templates

 Generate EIB spreadsheet

templates from 200+ WS
operations, including
business processes
 Modify templates to meet
your needs
Integration Meets Business Process

 Orchestrate integrations from

the business process
framework
– Approval and delivery
– Retrieval and approval
– Chain integrations
– Tag and deliver documents
to different locations