Has anyone ever got the Workday Integration working properly?

DenMagnuson1 · ‎07-20-2015

We're implementing the HR Case Management and would like to use the Workday Integration to update the User, HR Profile, and Department tables as a start.

After configuring the properties as documented, trying to run any of the functions or execute the Import Schedule, keep getting 'invalid username or password'. We've been able to successfully connect to Workday through SoapUI but, the property 'WSS-Password Type' has to be set to PasswordText. The assumption that this was a SN developed integration should account for the proper security configuration doesn't seem to apply. I ran across a post that mention, " build out the SOAPMessage script include to add the SOAP header" but, that seems like a lot of work for a provide/paid plugin.

I need to get this functioning in a test instance to validate it's functionality and justify paying for the subscription. Appreciate any thought or ideas before I try going the HI ticket route.

Thanks,

Dennis

eric_hemmer · ‎10-19-2015

With the Fuji release, SN delivered a one-way integration that pulls information from Workday into SN. A few weeks ago at Workday Rising, one customer asked another customer how long it took to get that working and he said, "about 9 minutes."

With the Geneva release, SN plans to delivery a two-way integration with Workday, so employees can also initiate changes to personal informtion without leaving ServiceNow.

View solution in original post

DenMagnuson1 · ‎07-20-2015

Just an update, after playing and researching the Workday community docs, I was able to successfully connect and query data after adding the following Header information:

<SOAP-ENV:Header xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">

<wsse:UsernameToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

<wsse:Username>username@tenant</wsse:Username>

<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">password</wsse:Password>

</wsse:UsernameToken>

</wsse:Security>

</SOAP-ENV:Header>

Per the other post that mentioned modifying the header, not sure what Script Include this is in but will be looking at probably reporting back to SN what I've found.

rashmic · ‎07-27-2015

Thanks for sharing the solution Dennis,

This will be handy for us too.

Mike Patel · ‎10-09-2015

Yes, I have it perfectly working in my instance. I was getting same error. I made the service account admin of few modules in workday and that fixed the issue.

ankitsaharavat · ‎10-18-2015

Hi Dennis,

Integration between ServiceNow and Workday is possible using Informatica Cloud. For more info on ServiceNow connector, please visit -http://www.servicenowconnector.com.

For any further query, please reach at info(at)mansasys(dot)com.

Thanks,

Ankit