How to Integrate with Workday to get user data in Madrid since OOB plugins are inactivated.

[Ankit Jain5]

Can somebody provide a stepwise guide on how can we get data from Workday.

Since OOB plugin supported SOAP, so I am assuming that we need to go with the same, but since we need just unidirectional integration i.e. data movement only from Workday to Servicenow not vice-vera.

P.S. If there are no supporting documents, just type in steps, rest will be taken care.

[Alberto Consonn]

Hi,

please use the suggestion of michaelj.sheridan in the below thread:

https://community.servicenow.com/community?id=community_question&sys_id=4c9a2049db4d338023f4a345ca96...

If I have answered your question, please mark my response as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.

Thank you

Cheers
Alberto

[Ankit Jain5]

Hi Alberto,

That answer is more related to steps needed for upgradation, but I have to implement from scratch in Madrid only.

So, just want to know how to ask client about requirements, actually they have just provided us with a user having integration roles, we are using custom WSDL's online.

If you have an insight on how this integration could be carried out, kindly help me in a step wise manner, if possible.

[manasamaniac]

HI,

Our Team had created a design Document . We had implemented in Kingston Version now in Madrid.

Kindly check if below notes are helpful .

ServiceNow will expose its REST API to receive data feeds from Workday. The feed will be a full data feed everyday.

Below are the Workday data currently in scope to be pushed from Workday

• Workers
• Positions

             Below are the Workday data currently in global to be pushed from Workday

             -      Cost Center

             -      Location

A Scheduler in Workday will run everyday during non-business hours to push the foundation data from Workday to ServiceNow. Based on the unique ID for each record type, ServiceNow will either insert or update the data.

Location data, Cost Center data is core platform and is also considered as master data.

Postion and Worker data is HR System specify data and will only be referenced and retrived in HR application.

Position is reference data in HR Profile (worker) data which should be loaded in the system before the worker data.

Data load process will follow the below sequence to make sure all the data is loaded with all reference data

related in the system. 

All staging stables are created in HR(Human Resource) scope only.

STAGING Table                                    CORE Tables                                                        Data

                sn_hr_core_workday_location                   cmn_location(global)                                           Location Data             

              sn_hr_core_workday_cost_center           cmn_cost_center(global)                                   Cost Center Data      

            sn_hr_core_workday_position                  sn_hr_core_position(HR Scope)                      Position Data

            sn_hr_core_workday_user_profiles         sn_hr_core_profile(HR Scope)                         Worker Data

Worker data have referecnce for Location, Cost Center and Poition data so we need all these data loaded before worker data is loaded.

Service Now FieldName	Table Name	Reference details	Backend FieldName (SNOW)	Workday  Source Object
Location ID	cmn_location	No reference	Location Id	locc:Location/locc:Location
Location Name	cmn_location	No reference	Name	locc:Location/locc:Location_Name

Scripted REST AIP xml file which provide the translation and mapping details.

Location REST API URL Dev:  https://------.service-now.com/ api/sn_hr_core/-----/----/locations

Similarly for cost center , Positions , workers

Workers

Service Now FieldName	Table Name	Reference details	Backend FieldName  (SNOW)	Workday Source Object	Encryption
Employee Number	sys_user (global)	Reference to sys_user	User.Employee_Number	ws:Worker/ws:Summary/ws:Employee_ID
First Name	sys_user (global)	Reference to sys_user	User.first_name	ws:Worker/ws:Additional_Information/ ws:Preferred_First_Name	Y

Similarly REST API for cost center, locations and workers.

Hope above info is Useful. We had implemented Scripted REST API.

Thanks

Manasa

[Ankit Jain5]

Hi Manasa,

Thanks for the input, but we need to integrate in such a way that everythign is taken care by us from Servicenow end, need no depencdency on Workday. 

You may take it as single handedly we have to carry out integration from Servicenow end, all help we can get from workday is WSDL and user with integration roles.

If you have anything in such regards then let me know ASAP.

Thanks