Portal Kiosk

[Mike_R]

Hello,

I’m looking for something similar to the walk up experience module. But instead, I just want to setup iPads where users can submit incidents and requests. There will be no genius bar/tech bar, just normal incident and requests.

Couple requirements:

1. Session should not time out (just like the walkup user doesn’t time out with the walk up experience)

2. After users submit requests, it should go back to home screen.

The only thing I can think of is to create my own portal for this but wondering if there’s a better way or if there’s something OOTB

[krzysztofsalbut · Accepted solution]

I have created a similar solution for IT Hub or so-called KIOSKs in Servicenow.

The perfect solution is to use a portal interface for this.

Create a copy of SP portal and copy each page you need. Use portal Designer to think of layout and few requests available on click.

in my case, I just needed to create a number for the queue so that the user knows the expected time when he will be appointed.

so think of creating a separate portal for all kinds of mobile devices with a limited number of requests and incidents. 

After submitting usually on portla you go back to the previous page but after each submit you can add a script to navigate back on the home page (native portal URL).

Creating your own portal by coping with the SP portal and its pages is a very good way of implementing it. 

[Mike_R]

Thanks, that's what I was thinking. Are you able to share some screenshots of what you created?

[krzysztofsalbut]

it looked better on smartphone or iPad. I only have a desktop picture for this. Just 3 different types of requests controlled via the touch screen. All fields were choices or references so that user doe snot have to type a lot...

better to allow select from the list then browse and just fied really important fields max 3-5. The rest can be loaded and updated behind the screen but shown on RITM or other types of tasks.

[Marc A Love]

We created a "Portal" with 2 pages (1.generic welcome/logo...click here page, and 2. a simple who you dropdown and simple what is your problem text field).

We didn't feel our users were savvy enough to determine an incident from a request so we create a "Call" record (which now is being deprecated to the interaction record) for the agent to pick up and determine which type of actual ticket to log.  We also have a display to show the "Call" records to show where they are in line (in the case of a walk-up bar).

This has worked out fantastically and we'll look going forward if this simple approach is worth converting over to the new walk-up OOTB approach or not.

ML