This is related to my previous post, but I think I need to elaborate on the use case a bit more and recommend additional features and improvements.

First of all we love Web Access 10. It's the greatest thing since sliced bread. We stopped showing the desktop client to new clients and are working to switch existing clients to use WA 10. The prospect of embedding it into a form to be able to display repository contents is awesome and opens new possibilities. I know you could do it before with older versions of WA but the new one looks slick, is responsive and works very well. I just want to elaborate on a type of scenario we have come across several times recently.

In this scenario, we want to use Web Access inside a form in order to display documents submitted through the form in a previous step. This is pretty easy to do. However, what makes this scenario challenging is that the users involved are not tech-savvy. At all. In fact some of them can barely use a computer and we are going to have to train them heavily to transition them from a paper-based environment to a Laserfiche environment.

As such, we need the embedded Web Access view to be extremely simple and locked down. This is to prevent accidents, errors, and general confusion. The only thing the users should be able to do when looking at WA through a Form iframe is:

• See a list of documents
• Click a document and view its image in full-screen mode

That's it. We don't want the users to be able to do the following:

• Use the checkboxes next to the document name in the entry browser. Most people end up clicking them in their first attempt to open a document (hey, it's a checkbox, why not click it right??). Then they wait for a few seconds and get confused when nothing happens. Like I said, very non-technical users. So we need a way to get rid of those checkboxes in this locked down view. They aren't needed anyway since multi-selecting docs is not needed in this case.
• Right-click anything to open its context menu (need a way to disable it)
• Drag and drop new documents into the folder (we need all file imports to be done via Forms)
• Open documents inside the same iframe (they currently open in a new tab and we need to prevent this)
• See a document's thumbnails or metadata pane (page navigation should occur only through the up and down arrows on the doc viewer toolbar)
• Place annotations on the document or rotate it, or change it in any other way
• When viewing a document inside the iframe, quickly and easily go back to the folder
• Perform searches or log themselves out (a way to hide/remove the entry browser toolbar and the navbar that doesn't require custom JavaScript)

I know some of these are possible via the readonly query parameter. The problem is that the help files state read-only mode only works if the user has to log in after clicking the link. Once again though, these users are very very non-technical and the last thing we want is to display a login screen to them. We want to leverage LFDS single sign-on as much as possible, so readonly mode needs to work somehow when the user is already logged in.