The first thing I do when trying to determine which Response_Group parameters to use is fire up Postman. The latest version of the WD SOAP API has over 60 different Response_Group parameters! (At least it lets you get a single book, not the entire encyclopedia set, I guess.)ĭetermining the right combination of Response_Group parameters can be challenging, as some will enable an information chunk and others will enable even more, but then others will restrict some of the information that was just allowed via another parameter. But instead of just getting those pages, you have to grab the whole H book. Imagine going to the library and wanting just the pages from the encyclopedia for the Human Genome Project. It doesn’t allow you to get granular with the data elements that are returned, but rather like chunks of data. I mentioned Response_Group earlier, which is a Workday SOAP parameter that allows you to somewhat restrict the data that’s coming back. Response_Group – Fire Hose or Garden Hose? Let’s take a look at the tricks and utilities I have found that will expedite SOAP-based integrations for Workday and ServiceNow. It’s not so much about using SOAP in ServiceNow to import Workday data, but rather how to speed up the process of getting the right data, parsing it, and extracting it efficiently. Which brings me to the purpose of this article. SOAP is a giant pain in the ass at best, if you ask me. So, I’ll dig into the Response_Group parameters only to come to the conclusion that the existing integration is already optimized as much as possible based on the data that the organization wants to import. I haven’t, so I don’t pay much attention to those API docs.Įxcept, that is, for when I get an itch about the WD integration for a customer taking 17+ hours to complete due to the amount of (useless) data that comes back for each worker. They are a good reference, but mostly it’s a bunch of jargon that assumes that you’ve already taken the 100- and 200-level classes on Workday and web services. (I’ll cover my experience with Workday RaaS and REST in another post.) The Workday SOAP API docs for the Human Resources web service can be found here (other versions here). They do offer REST endpoints, but only if a custom Report as a Service (RaaS) is built, which, in my experience, requires a lot of technical know-how on the Workday side. Workday, for some reason, only has SOAP APIs by default. (The organizations I have worked with have an existing Workday integration and don’t want to spend the project dollars on rebuilding something that’s already working and doesn’t appear to be going anywhere, even if it would mean that the Workday sync would take less than 3/4 of a day.) ServiceNow has since released a new version of the Workday integration that might be easier/better/faster/whatever, but I haven’t used it yet. I cut my teeth with the old HR Integrations application, which included a Workday integration (among others). As a consultant who spends a significant amount of time working on HRSD projects, I often find myself face-to-face with a Workday integration.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |