Emloyee Lifecycle Events - digital signature employee contract

[Lucien Lauret]

We are in the design phase of an ServiceNow employee onboarding project and we need help with the following customer requirement.

Current situation
The employment contract for a new hire is generated in the HR Core system (PeopleSoft). This results in a pdf that needs to be signed by the new hire. In the current situation PeopleSoft sends this contract-pdf to the personal email address of the new hire. The new hire prints, signs, scans and sends the signed version back to a central email box.

New situation
In the new situation, with the implementation of ServiceNow Lifecycle Events, the customer wants this in PeopleSoft generated contract (pdf) to be signed by the new hire in the ServiceNow environment making use of a digital/electronic signature. After the employee signs this document in ServiceNow, it needs to return to their file in PeopleSoft. It is not an option for this customer to transfer the generation of the employee contract from PeopleSoft to the ServiceNow document generator.

So far in our search for the (best practice) solution we did not find the option for uploading an outside ServiceNow created pdf file that can be digitally signed in ServiceNow. For a digital signature we are looking at options with DocuSign, AdobeSign and the e-Signature in ServiceNow. Does anyone have the experience and/or the knowledge how we can make this work?

[michaelj_sherid]

@Lucien Lauret Given that ServiceNow cannot be the generator of the file, you will not be able to use the OOTB "Sign Document". The other options are using a 3rd party digital Signature such as Adobe Sign or Docusign. Even going this route there are going to be some complexities (one being a customization in PeopleSoft to return the AdobeSign/Docusign completed document into PeopleSoft). I do not see this as a simple customization to inject a signature within ServiceNow from a PeopleSoft Generated document. Is there a plan to store this document at all in ServiceNow? I understand you do not want it generated in ServiceNow, but if signed in ServiceNow I am curious if this is part of the use case or if the document will only reside in PeopleSoft once complete. I ask for many reasons, one being the Employee Experience. If I sign a document in ServiceNow, then have no access to see it afterwards (in ServiceNow), I am depleting the experience.

Regards,

Mike

[Lucien Lauret]

Hello Mike, 

Thanks for your reply! It more or less confirms what we expected. Also a valid point regarding the user experience.

Regards, Lucien