Skip to Content
Business Trends
Author's profile photo Manu Bhutani

Integrations options between ServiceNow (SN) and SuccessFactors (SF) – Point to Point (PTP) and through Cloud Middleware (SAP CPI/Boomi)

ServiceNow (SN) is a cloud based platform and also has mobile service apps for the employees.  Many of you may remember SN as a ticketing tool. ServiceNow provides a platform for all service departments to easily access the services they offer to employees. ServiceNow has evolved into a very mature platform for HR services by which many business probelms can be resolved. Many clients are getting attracted to services provided by SN hence it has become common to Integrate the HRIS system with SN.

I would talk about Integration options between SAP SuccessFactors (SF) and SN. It is possible to integrate SN with almost all HRIS systems. SN can be used for ESS and MSS transactions and can be integrated with SF using the APIs. SN is fully driven by APIs.

SAP and SN have made good progress in last couple of years by working together and building a robust and seemless Integration between SuccessFactors and SN. ServiceNow has a product Integration with SAP SF EC. ServiceNow’s enhanced integration with SuccessFactors allows customers to deliver a seamless enterprise‑wide employee service experience. This complementary solution offering allows customers to leverage the power of both systems and create a connected experience.

Firstly, when SAP SF is system of record then very first integration we need is to bring in the Employee Demographic data from SF Employee Central (EC) to SN. This is required to get efficient service from SN because service teams have access to relevant employee data from SF. There is a pre-configured Integration in SN to extract employee profile data from SF EC. It is based on SOAP and REST. Basic and Oauth authentication is possible. Field selection and mapping are done in SN and job is scheduled. Similarly another preconfigured integration is to sync to-dos in SN and SF. These out of box Integrations can be set up quickly without much work to do.

Pre-configured%20Integrations

Pre-configured Integrations

For various other scenarios, in which there’s a business process for Employee or Manager self service we can easily set up Integrations between SN and SF. For ex. in LOA scenario where employee initiates the LOA in SN and it goes through various approvals, when the approvals are complete the SF APIs can be triggered from SN to update the LOA event in SF. Similarly for other HR processes, Direct Integrations or Point-to-Point (PTP) can be easily set up because both SN and SF have powerful APIs for connection and data updates. For such integrations error handling is also very smooth and straightforward. Since SN is a powerful ticketing tool we can configure our Integration to generate a ticket for success/error notifications. We actually don’t require an additional layer (i.e. middleware SAP CPI or Dell Boomi) to connect these systems.

There may be some complex scenarios where we need to build a heavy transformation logic then you can analyze whether it makes sense to have a middleware in between. For ex. if there are various steps in your logic which starts from reading employee data from SF, then transforming it based on some criteria, and then update in SF in mutliple steps. In such cases it is better to have a middleware where this logic can be built and accordingly error handling can be done. In this case if sender is SN and receiver is SF then you can create a service in middleware and expose it via end-point url. Create a sender HTTPS channel for SN to trigger the middleware. Make sure the HTTPS user is assigned the role ESBMessaging.send. This role is required to process messages on the CPI tenant node.

This end-point url can be shared with the SN team to configure, trigger and send the data. The middleware gets the data in XML/JSON etc. format and updates in SF.

Some integrations can be real time also i.e. when workflow is completed in SN then Integration should be triggered and data should be updated in SF in real time. In such cases based upon an event in SN the Integration can be triggered to SF. SN also has ability to schedule a job and trigger the Integration to SF.

For all such Inbound Integrations to SF you can create a service in middleware and give the end-point url to SN to trigger the Integration. There are two options – Basic and Certificate based (obviously more secure)

I would like to thank Prateek Srivastava (@prateek.srivastava3) who assisted us initially around Best Practices for such Integrations and introducing us to the SN capabilities.

Assigned Tags

      3 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Naresh Dasika
      Naresh Dasika

      Nice blog Manu.

      Author's profile photo michael ziegler
      michael ziegler

      Hi, nice and helpful blog. Thanks for sharing.

      One Question: Which RBPs are used in SFSF? Is a technical user a must, or can you, if both systems are using the same userid, authenticate via OAUTH and use the existing RPBs mapped to the current user?

      Thanks

      Michael

      Author's profile photo Manu Bhutani
      Manu Bhutani
      Blog Post Author

      Hi Michael,

      As best practice it is better to use different userids for the connection. The permissions are usually quite open for such technical user but again as per requirement permissions can be granted.

      Regards,