10 Workday Integrations Interview Questions for Candidates and Recruiters
In the fifth part of our Workday Interview Questions for Candidates and Recruiters series, we are addressing Workday Integrations.
Click Here to Read Part I – 10 Basic Workday Interview Questions for Candidates and Recruiters
Click Here to Read Part II – 10 Workday Report Writing Interview Questions for Candidates and Recruiters
Click Here to Read Part III – 10 Workday Business Process Interview Questions for Candidates and Recruiters
Click Here to Read Part IV – 10 Workday Configurable Security Interview Questions for Candidates and Recruiters
Click Here to Download eBook – 50 Workday Related Interview Questions
Always remember to look into Workday Learning and Workday Community as your primary source for official Workday documentation.
Integrations are crucial when communicating external systems with Workday. To be able to say you master them means that you understand how data can be imported to or exported from Workday. Thankfully, there are predefined rules of how that data must look like, and public interfaces you can access anytime you need to build an integration. In this set of integration questions, we do not attempt to test the mastery of the different Workday Integration tools available, but the general knowledge of how to build integrations.
What are the main types of Workday Integrations and how do you select which solution to use?
- The main types of integrations are Workday Studio Integration, Enterprise Information Builder (EIB) Integration and Cloud Connect Integration.
- When deciding over which tool to use we need to take into account some factors; whenever you take in the design of an integration, from the requirements you should follow a roadmap, here is an example of it:
- Is the solution already pre-built? Am I connecting to a third-party vendor with a solution already in place? – If yes, most likely you will choose a Core Connector.
- Does this integration just need to export or import some data into Workday? – If yes, then most likely you need to go with EIBs.
- Do I need to execute several rules, and reports to get the data and calculate the results I need? For example: Determining payroll between Exempt and Non-Exempt employees, calculate deductions, etc. – If yes, then most likely you need a Workday Studio Integration.
Name a prefix you can use to search for integrations:
Name some Integration ID types:
- Workday ID, External ID, Reference ID
Name some input and output types for EIBs:
- Input: SFTP/FTP, REST, or attachment
- Output: SFTP/FTP, HTTP, Email, CSV, JSON, XML, etc
What do you use XSLT for in an integration?
- You use XSLT to transform the input or output data going into an XML document.
What is a WSDL? Why are they important?
- WSDL stands for Web Service Description Language, and they are important because they specify how XML documents should be formatted to be accepted as input or define the output of Workday Web Services.
Say that you have a data warehouse or an external system that needs to be updated when an employee changes their information in Workday. What integration should you use?
- Core Connector: Worker
What is the name of the XML query language you can use to select elements from an XML?
Name some MVEL variables you can use in Workday Studio and what are they used for:
- “lp” to access launch parameters, “props” to access message properties, “vars” to access MessageContextVariables
What Workday Studio component you can use to translate a conditional if or a loop? What good practice you should add to your integration to get notified of any errors in your Studio integration?
- The Route component can act both as a conditional if or a loop depending on the routing strategy. Error handlers type send-error are used as a good practice to catch errors and send them to either the integration event or another output method via the out-transport.
Don’t forget to follow us on LinkedIn, Twitter and Facebook to keep up with the latest updates!