Visitor Check-In App for Facilities

shegde
Giga Contributor

‎08-17-2018 09:08 AM

Has anyone implemented the Visitor Check-In app from Servicenow Share?

https://developer.servicenow.com/app.do#!/share/contents/9521858_snc_visitor_checkin?v=1.01&t=PRODUCT_DETAILS

This was recommended to the client by a SN rep. I'm having issues automating the printing from the MID server to the connected printer. I'm curious to know if anyone has implemented it, and how.

0 Helpfuls
  • 1,917 Views
3 REPLIES 3

Tyler Herman
Kilo Guru

‎08-17-2018 11:20 AM

Hello Shegde,

 

I considered implementing this but was not pleased with a few components such as the look of the sign-in screen and reliance on Jelly. I've opted to build out a custom table/form to handle this process instead. Long term plans would be to build out Service Portal widgets to handle this process.

0 Helpfuls

shegde
Giga Contributor
In response to Tyler Herman

‎08-17-2018 11:33 AM

Hi Tyler,

 

How did you print out badges from your custom form?

0 Helpfuls

Tyler Herman
Kilo Guru
In response to shegde

‎08-17-2018 12:27 PM

Afraid that isn't something we've approached yet.

Here's what our sign-in process looks like today :

  1. User enters the lobby
  2. User is given a pre-printed badge with a number on it (0001-0025)
  3. User is asked to sign in on an iPad
  4. User goes to an iPad, which is sitting at the sign-in form, and selects their badge number from a dropdown.
  5. The user then enters their name, company, etc. and clicks a custom UI action titled "Sign-In". When Sign In is clicked, the record is saved and the screen reloads to the sign-in form with a message saying they signed in successfully and to return to the iPad when ready to leave.

 

When the user is going to signout :

  1. User goes to an iPad and sees the sign-in form.
  2. User selects their badge number, at which point a client script runs that looks up that badge number to see if it's currently in use by anyone. If it is, the form loads the rest of the fields with info from the existing record and replaces the "Sign In" UI action with a "Sign-Out" UI action.
  3. The sign-out UI action does NOT save the record but instead glide queries the existing record and updates it with a signout time, deactivates it, etc. 
  4. The form reloads with a message saying they've signed out successfully and to drop the badge at the receptionist.