Walk-up Experience user check-in

clyon · ‎03-13-2019

In walk-up experience, at user check in, it currently ask for user name. Is it possible to change what field it is searching on? We'd like to use the 'user_name' field which contains our SSO id. TIA

Michael Ritchie · ‎03-13-2019

Unfortunately this isn't possible with simple configuration. In order to accomplish this you would have to clone the walkup_check_in widget and then use this widget instead. But this is a great enhancement request since other widgets allow the setting of system properties to set things like this.

Change your scope to Walk-Up Experience
Pull up the Service Portal Configuration and clone the walkup-checkin widget
Edit the highlighted piece of code as show below
Edit the walkup_check_in page and use your cloned widget instead

Please mark this post as helpful or the correct answer to your question if applicable so others viewing may benefit.

View solution in original post

darius_koohmare · ‎03-13-2019

Hi,

As noted by Michael, there's a way to change it (although not easily).

Do you find that using the onsite check-in with a reference field is working for your environment?

We are looking to simplify the check-in experience in the Walk-up for useres.

Would you prefer/consider other approaches such as:

Badge Scanning
Facial Recognition
NFC Through Mobile
QRCode Scanning Through Mobile

Let me know!

Darius, ITSM Product

Don Malik1 · ‎12-18-2019

Hello Darius, I have requirement for employee to scan their badge when checking-in. You suggested very intersting approaches. Are there any documents around badge scanning or any of the approaches you mentioned?

darius_koohmare · ‎12-18-2019

Hi Don,

We will also plan to include a badge scanning integration framework with our upcoming Orlando release. Documentation will be available at that time.

darius_koohmare · ‎01-21-2020

Hi, as of orlando we also plan to add configurability to the check-in widget instance options, where you can define to use email versus name as the unique identifier.

Janel · ‎05-26-2020

The problem with cloning the widget is that you do not get any of the angular templates (sp_ng_template) that go with it. I tried cloning the widget and made copies of the angular templates with new names and tried to track down where they were used (angular providers). At this point it was resulting in updating OOB providers that defeats the purpose of cloning the widget. So I had the same problem where things wouldn't display right (someone mentioned looking "corrupted" above).

I came up with a little band-aid fix. I added the OOB widget to my page and on the container I set the class to hidden. Then I added my cloned widget to the page and it seems to work fine. You do need to have the 8 copies of the Angular ng-templates on your cloned widget or it will not work. Not all 8 seem to be needed (and I'm puzzled why any of them as copies are needed at all), but I do not know which ones for sure are.