Integrations

Integrations

Integration System

A tenanted definition of an integration between Workday and an external system based on a template that provides the methodology for communicating data.

Reference ID

A unique identifier used to look up data for integration purposes.

System User

An account associated with and required to launch a Connector or Studio integration. Workday delivered integrations and custom integrations require a system user account for authentication and web service calls. A system user account is not associated with a person in Workday.

Integration Template

A collection of integration services that enables communication between Workday and an external system. Workday provides integration templates in categories such as Benefits, Financials, HCM, Payroll, Payroll Interface, Procurement, Recruiting, Security, and Settlement. Many of the delivered templates contain default values for attributes, as well as prompt values for attributes and maps, to define the integration further.

Integration Event

The record of an integration process. Every integration—current or past, involving the import or export of data, successful or not—gets recorded as an integration event. The integration event contains all the information about the integration process, including its status.

Connector

A set of  one or more integration templates that provide a framework for building integrations in a particular functional area. The integration can support a specific type of data, or can support a specific endpoint ( vendor, legacy system, third party payroll )

Enterprise Interface Builder (EIB)

An integration tool that enables you to create simple, secure, and customizable integrations with Workday. Alternately, an EIB is a simple integration created by the integration tool. An EIB consists of an integration system, an integration data source, an integration transformation, and an integration transport protocol.

Integration Field Overrides

A service that lets you customize integration systems that are based on a connector template. Field overrides are managed through an integration service. They use calculated fields or report fields to supply values to an integration system. Example: member IDs in benefit provider integrations.

Integration Attribute

An integration component that specifies the tenanted value of a data element in Workday. Example: Master Policy Number is a type of attribute in benefit provider integrations.

Integration Data Source

Indicates the type of data that Workday receives from or exports to an external system and its location.

Workday Web Services

Workday’s public API. Based on open standards, Workday Web Services (WWS) provide the core method for integration with Workday.

Integration Map

An integration component that specifies how values in Workday map to values in an external system. Example: Pay Rate Frequency is a type of map in third-party payroll integrations.

Integration Service

A group of related integration attributes, maps, and XSLT that provides a framework to transform Workday data into the format required by an external system.

Integration Transformation

Converts data into a format that Workday or a receiving external system can understand. Workday provides some delivered transformations, and you can also create custom transformations.

Integration Transport Protocol

Controls how Workday exports data to an external endpoint or service or imports the data from an external endpoint or service. Workday supports several types of transport protocols, including email, FTP and SFTP, HTTP/SSL, Workday attachments, and Workday Web Services.

Workday Studio

An Eclipse-based development environment that enables you to build more complex integrations with Workday.