*We no longer allow for XSLT integrations*

Please review all possible scenarios for Workday integrations:

Client/End-user hires Workday to build the integration
Fees determined by Workday.
Third-Party Mercer builds integration. (Taz preferred and most widely used method)
Fees determined by Mercer.
Client hires own Workday Consultant (this is quite common for employers to already have this and often necessary due to the complexity of Workday client configurations)
Workday consultant configures and builds the Workday side of the integration
CRA hires a third party to build the other half of the integration to and from the TazWorks API.
Client/CRA hires own third party to facilitate integration in tandem with their own internal or Workday consulting teams.
TazWorks will provide support to those coding to the TazWorks API in the form of answering questions and general help, but will not and cannot do any coding in this scenario.

For scenario 3, TazWorks would like to build their own “Workday Connector” which will always involve a Workday consultant on the other end, until then it will be done by a Third-Party. TazWorks will refer to Mercer for any current integration needs under this scenario.

Summary of process

This Integration may take between 3-5 weeks for implementation.

Submit your request along with your client name to TazWorks ticketing system.
Sign and return Workday SOW with desired level of integration to initiate the process.Typically, your client will have questions and a few calls with TazWorks and Digital Mercer may be needed in order to help them along and provide direction and confidence.
Upon receipt of signed SOW, TazWorks initiates process with Digital Mercer who will then allocate a resource to the project within 5 business days.
CRA invoiced for full SOW immediately.
TazWorks and Digital Mercer coordinate development efforts during weekly calls.
Updates and collaboration with CRA headed by TazWorks team.
When testing phase is reached, end-user will be engaged for collaboration.
Workday engaged to finalize configuration on their end.
Real orders are processed.
TazWorks follows closely the activation and testing process to ensure success.

Ordering Instructions

Workday Integration Screenshots.pdf

Workday Tiers and Scope.pdf

Each Interchange API implementation needs the following as a minimum

Authentication into TazWorks software: CRA creates a client API user and provides credentials to ATS. Requires ATS Server IP range white list.

Username / password

Or Json Web Token (JWT)

Internal configuration Use for API Connector: Integration entry int TazWorks software.

Client to use an integration
AWS / SDK URL to post back order status
AWS / SDK credentials to post back order status

Integration entry in the AWS SDK

TazWorks software(URL) for screening requests
TazWorks software(URL) for package requests
TazWorks software Authentication for package list / order requests
ATS (URL) for screening status updates
ATS Authentication for screening status updates
Other integration custom info (per ATS)

Additional Fields Collected

Personal Identifiers:

Name, Social Security Number

Delivery Options

TazWorks automatically posts back events to ATS. If yes partner receives post backs on the following events:

Completed search, Completed report

Orders are processed automatically.

QuickApp gathers authorization and disclosures for orders from ATS.

TazWorks Integrations Library

Workday

(801)572-7401

Information

Services

Quick Links

Office Hours