1 / 36

Workday Integrations

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)

ggarnica
Download Presentation

Workday Integrations

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Workday Integrations Workday Integration Cloud

  2. Integration – A Key Deployment Challenge • Today’s enterprise applications rarely live in isolation • Integration burden traditionally has rested with the customer (IT) • Connectivity is a reality, but should be simpler to build, deploy, and maintain • Application vendors should share the burden of responsibility Complex Consuming Costly

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

  4. Workday Integration • EIB (Enterprise Interface Builder) Created Integrations • Workday Studio Created Integrations • Delivered Integrations

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

  6. Enterprise Interface Builder

  7. EIB Integration Components An Enterprise Interface has four components:

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

  9. Workday Integration Cloud Workday Cloud Workday Applications Public, Web Services APIs Custom APIs Workday Integration Cloud Integration Cloud Platform IntegrationCloud Connect Custom Integrations CloudApplications On Premise Applications Benefits Providers Payroll Providers LDAP/AD

  10. Opening the Integration Cloud Platform New New Customers SI Partners New ISV Partners Workday Development and Services Workday Integration Cloud Platform

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

  12. Growing Application Partner Ecosystem

  13. Cloud Connect Where is Workday today? Where is Workday going?

  14. Integration Cloud Connect

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

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

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

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

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

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

  21. Connectors and the Overall Problem VERY Complex Workday Application Complexity SIMPLE VERY Complex SIMPLE Target Product Integration Complexity

  22. Case 1: Pattern-Based Connector

  23. Case 2: Standards-Based Connector

  24. Case 3: Domain-Based Connector

  25. Extending Connectors • Functional canonical format • Workday defined structure • Part of a multi-step process • Sometimes, but not always! • Example: ADP PayXpert Payroll Integration

  26. Cloud Connect for Benefits Framework • CCB Core • Framework • Core processing • Affects ALL providers • CCB Catalog • Specific functionality • Conforms to vendor specs • CCB Connector • Abstract CCB core • Available over the next few updates

  27. Roadmap: Workday 15 • New packaged integrations • Salesforce.com Chatter • Cornerstone OnDemand LMS • AngelPoints • Updated Connectors • Payroll Interface • HCM Worker Sync / Directory Services • Electronic Payments

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

  29. Roadmap: Future • Continued packaged integration build-out • Continued investment in Connectors • Looking to simplify and reduce implementation time for complex integrations

  30. Q&A / Wrap-up • Questions?

  31. Integration Cloud Platform

  32. 513 - Integration Cloud Platform Daniel Beck, Kimberly Kuo Technology Product Management

  33. Workday Studio Workday • For complex integrations • Rich, graphical development environment • Deployed and run in the Workday Cloud Deploy Run Workday Studio Build

  34. Case Study: Fairchild SemiconductorIntegration Cloud Key to Workday Decision • 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 20 Studio + 8 EIB integrations = 4 months

  35. Inbound EIB Spreadsheet Templates • Generate EIB spreadsheet templates from 200+ WS operations, including business processes • Modify templates to meet your needs

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

More Related