#happy2022workday day-087
Happy 2022 day-087! Today’s step is from WSDL to testing WWS…
Workday Boomerangs typically end with a Workday Web Service (WWS) call to an inbound operation which pushes data back into Workday.
Recall from a few days ago we were looking at a Sample called HelloWWS. That’s a good Sample for understanding how the Get_Workers outbound WWS operation returns a list of all workers.
Just as a google search result appears to you one page at a time, the Get_Workers WWS operation delivers to you all the workers one page at a time. This is unlike a RaaS report which could be run in the Workday UI and appears to show you all results when you scroll down and up (with some delays), as compared to one page at a time (requiring you to click Next, Next, etc.)
Anyway, to understand how an inbound WWS operation pushes data into Workday, we are today first looking at an outbound WWS operation:
- Start in the Project Explorer
- Expand the HelloWWS project and double click the Assembly item
- For now we are done with the XMLExamples project
- The PagedGetOfWorkers component will call the Get_Workers outbound WWS operation until all the workers are returned
- The Schema Explorer lists the operations of a WWS, such as…
- …, Get_Workers, which you can right click and open a Wizard that displays input options, such as…
- …, groups of responses to include or exclude, and…
- …, which Page, and the Count of workers for each page
- Clicking the [ Finish ] button results in the Request XML for the Get_Workers operation, showing a request for page 1 with a count of 10 workers per page.
For those of you with thousands of workers in your tenant, don’t worry as that is showing just an example default of 10 workers per page for human eyeball testing. You could actually request up to 999 workers per page.
In tomorrow’s day 88 we will step from outbound WWS operations to the typically much more complex inbound WWS operations.