22nd
Ideas para restringir el acceso a ciertas vistas de un documento InfoPath
Paul Galvin ha publicado una plantilla InfoPath con la idea de que podamos utilizarla como “Starter kit” para los formularios InfoPath que queramos realizar. Podéis descargarla aquí: InfoPath: Part 1 - Template | End User SharePoint
La parte que más me ha gustado, es la que el describe como “Password controlled access to an admin view of the form” esto es, contar con una vista a la que sólo pueda accederse tras introducir una contraseña, y donde podamos tener información y funciones reservadas a un administrador.
La implementación de la idea la realiza Galvin de forma muy sencilla, os recomiendo que descarguéis su “Starter Template” y le echéis un vistazo.
Aquí os copio y pego el listado completo de características de la plantilla:
- Naming convention for views.
- Standard form layout, including an instructions section, “main data” section and save/discard buttons.
- Pre-built views for showing a “successfully saved” type of message for when users save the form but continue to work on it (as opposed to save and return to SharePoint).
- Pre-built views and some logic for handling “discard my work” scenarios. Basically, it forces the user to confirm they want to discard their work.
- Password controlled access to an “admin” view of the form.
- A “developer notes” view to provide a logical place for developers to write notes about their forms and help to reduce the cost of form maintenance. Ideally, it will provide a good answer when maintenance programmers ask the question, “What in world was he he thinking when he created this form?” The developer view can answer that.
- Standard logic / place holder to assign a file name to the form for when it is eventually saved back to SharePoint.
