#happy2022workday day-086
Happy 2022 day-086! Today’s step is from XML into WSDL…
What is WSDL? Pronounced wiz-duhl, a WSDL file follows an important definition language for web services. We need to know about WSDL to return from our thrown boomerang, meaning to put data back into #Workday.
To review the past few days, we have moved from HTML to XML, and are now investigating a certain type of XML file that is used to define the operations in a web service. You might know about loading data into Workday using an Inbound EIB. We aim for you to soon catch an understanding of how your Inbound EIB file contains the data that somehow magically becomes the “input” for a Workday Web Service “operation” (WWS). Essentially, an Inbound EIB is actually just a front-end to calling a WWS.
The delivered XMLExamples inside Eclipse (we will soon start calling it Workday Studio instead of Eclipse) has a WSDL example:
- Return to the Project Explorer panel inside Workday Studio
- Expand the SpaceWarGame project
- Investigate the CommandSheet.xml by clicking to exand a “point” to notice the left-side highlighting (not a scrollbar) of that element
- Similarly with the ResultSheet.xml, expand a “ship” in the Design tab and then view the Source tab to see the left-side highlighting
- Notice that this project has a .wsdl file, so double click the SpaceWarGame.wsdl so it opens in a new tab
- Click to highlight getResultSheet
- Switch from the Design tab to the Source tab and again notice the left-side highlighting, which this time includes several lines
- Zoomed in view shows the words “operation” as well as “input”, “output” and “fault”
Challenge: For those who have loaded Inbound EIBs, explain how the steps you take to load data successfully into Workday using an Inbound EIB are related (if at all) to those 4 words in above item (8)?