sdtimb
Giga Expert

[due to the size of the workflows, the images may be difficult to read. To save view in full screen right click on an image and select 'save image as...']

With our initial implementation of ServiceNow I created an Onbarding process that worked well. However, as the business grew, ServiceNow extended to our global locations, and IT transitioned from a semi-fragmented organization towards a centralized model, we quickly outgrew our original design.   After several revisions to the Onboarding process, both in ServiceNow and our internal HR processes, I have ended up with an Onboarding process that is very functional and extremely flexible to change. Our basic Onboarding process is as follows:

-- Human Resources interviews and selects a candidate. After the offerletter is accepted;

        -- The hiring manager completes the Onboarding form via the ESS. (previously, a paper form was filled out by the hiring manager, given to HR, HR would review, if everything looked good HR would then translate the information from the paper form into the ServiceNow onboarding form (madness). This is because we were lacking an approval process in the ServiceNow workflow)

        -- An approval email is sent to the Human Resources representative(s) at the new employees location

        -- Upon reviewing the Approval Email, which contains information from the Onboarding form about the new employee, the request is either Approved or Rejected*

        -- Based on the selections / information entered by the hiring manager, Catalog Tasks are created and email Notifications are sent. This allows us to trigger activities, not only to Process Users (solely IT in our environment), but also members of the business.

*Approvals are very rarely rejected, only in cases when HR was not aware of the new hire. For corrections to the information entered by the hiring manager (title, start date, etc.), a mail script captures the body of the approval email and enters it in a "HR Approval Comments" variable on the Catalog Request & Catalog Tasks. This also eliminated the need to purchase additional Process User licensing, and train Human Resources in another system when minor details needed to be corrected.

OnboardingForm.jpg

Onboarding_Main.jpg

Onboarding_Irvine.jpg

OnboardingTasks.jpg

2 Comments
solutioningnow
Giga Guru

Good thought


jbrassard
Kilo Contributor

Is the initial form an actual catalog item, a custom ESS content page, or a custom form? We are looking to do something very similar. Our previous consultant set up our Onboarding, Transfer/Change, and Offboarding processes using service catalog items, execution plans and record producers. It is getting very unruly and we are also beginning to experience weirdness, which we believe are likely collisions on the back-end. We are also taking the product global, so we will not only have multi-site, but multi-countries with multi-sites. We are definitely moving to workflows, but are considering which approach is best for the front-end.