Notes from the morning of day 1. Kalan presented an overview of Workday Integrations
Everything going in or out of Workday goes through a web services API for consistency
2 integration tools - Enterprise Interface Builder (EIB) and Workday Studio
The Workday Integration Network (WIN)
- HCM Network
- Benefits Network
- Payroll Network (Interface)
- Workday Payroll (Network)
- Workday Spend Network
- Workday Financial Network
bulk loads typically don;t happen - usually one data item is transferred at a time
Reviewed a few use cases (see Workday slide deck)
Typical Integrations Mix - Configured (Workday Integration Network - 30%), EIB (simple - 45%), Workday Studio (complex - 25%)
Studio is an Eclipse based language - Java based
EIB Integrations Outbound: => Get Data -> Transform -> Deliver -> External System
Inbound: External System -> Get Data -> Transform - > Deliver
Cornell has 95 integrations - 25 of which are studios
Why does CU have more Studios than most customers? - retroactive benefits and semi-monthly pay are a result of Kronos configuration at CU
A menu of SOA design options - Dustin - Vivantech
Service Oriented Architecture (SOA)
It is a formalized approach for incorporating:
- Web Services
- XML
- Enterprise wide multi-tiered design
Goals
Compatible with current systems
- New applications would be able to communicate with existing systems
- Minimal changes should be required to existing applications / systems
Support multiple document formats
- Legacy Formats (PS, Kronos)
- Current Formats (Workday XML v14)
- Future Formats (XML v100)
Ease of Maintenance & Enhancements
- Maintenance & Enhancements account for well over 50% of typical software cost
- In long lived environments, like universities, the costs jump much higher