We're looking into a solution for you, but I don't have a release date quite yet. Just to make sure we get our requirements and expectations right...you mention a kiosk, but it sounds like the forms are not public? The inbox is only available to logged in user, so is the kiosk logged in as a generic user? Would public forms be an option for you?

Would'nt this require me to purchase portal? Isn't that another $10k?

I'm trying to understand how your current kiosk setup works so we can design a working page for it.

IT WORKS JUST LIKE FORMS, SIGN IN, CLICK PROCESS FILL OUT FORM, BUT ON THE FORMS HOME PAGE YOU ADDED ALL THAT CRAP THAT I DONT NEED TO SEE THAT CAN GET ANY USER BACK TO A PREVIOUS FORM THAT HAS SENSITIVE INFORMATION ON IT

Right, I understand that part, but I am trying to determine which part of it exactly is a problem for you so we come up with a good solution.

My History lists processes that the user either started or was a participant in. They only see the forms they submitted, which presumably is information they've already seen when they participated in that instance.

That's why I was asking if they log in as individual users or as a generic user.

Or are we talking about the process details for an instance under My History? The submitter wouldn't be able to see forms in later steps, but they would see the comments left when the step was completed. Is that where they see sensitive information?

Miruna, I think he is using a generic login so they can see the list of available processes to choose from, but needs to be able to hide tasks, reports, history, etc. I could see a good use for this with our organization as well. Instead of being able to customize a users individual experience though, we would like a kiosk mode for public view. Within the kiosk mode be able to specify which processes are available. Possibly have tiles for each processes with a screenshot of the starting form and the process name (similar to how it was in Forms 9).

Blake, that's why I was asking for more details. From the previous threads, I first thought we were talking about the case of a user who's only job is to submit forms, so I could definitely see how the change from thumbnails to a list and the addition of the extra click is obnoxious.

I see a few different use cases here and more details help us prioritize them properly and shape the implementation.

1. Public forms. Obviously not the case here, but I can see how, if you do have the portal feature, you'd want a want a page that lists all public forms (or a selection) either as a list or with thumbnails.

2. Submitter in a process that has sensitive information somewhere up the chain. So the admin would want an option to hide all details from the instance history. I'd argue that hiding the instance altogether from My History is not necessary in this case because it still gives the submitter a "did I submit that form?" check, but that could be an option too.

3. Kiosk-type setup. You have various forms displayed for easy access, possibly more than one page and grouped by type. For ex, the HR department would have their page with their forms while Accounting would have a different one.

I think you finally understand! Blake hit the nail on the head!

Miruna, did you come up with a kiosk solution for this? We're looking at implementing kiosks with a Forms process to get people to the correct information and form to submit so I'm curious to know what came of this. I'm just starting my research so I'll keep looking and apologize if there is more updated info out there that I haven't found yet. Thank you.