I needed to meet a security requirement for an InfoPath form today. In this business situation, a relatively small number of individuals are allowed to create a new InfoPath form and a much wider audience are allowed to edit it. (Dit is 'n nuwe-huur op-koshuis te gebruik wat deur menslike hulpbronne wat begin met 'n workflow).
Daardie doel te voldoen, Ek het geskep twee nuwe toestemming vlakke ("create and update" and "update only"), broke inheritance for the form library and assigned permissions to a "create, werk" user and a separate "update only" gebruiker. The mechanics all worked, but it turned out to be a little more involving than I expected. (As jy voel 'n bietjie wankelrig op SharePoint regte, check hierdie blog post). The required security configuration for the permission level was not the obvious set of granular permissions. To create an update-only permission level for an InfoPath form, Ek het die volgende:
- Skep 'n nuwe toestemming vlak.
- Duidelik weg alle opsies.
- Selected only the following from "List permissions":
- Wysig Items
- View Items
- Sien Aansoek Pages
Kies hierdie opsies kan 'n gebruiker 'n vorm by te werk, maar nie skep dit.
The trick was to enable the "View Application Pages". There isn’t any verbage on the permission level that indicates that’s required for update-only InfoPath forms, maar blyk dit.
Create-and-Update was even stranger. I followed the same steps, 1 deur 3 bo. I had to specifically add a "Site Permission" opsie: "Use client integration features". Weer, Die beskrywing is daar nie maak dit lyk soos dit behoort te wees wat nodig is vir 'n Path vorm, maar daar is dit.
</einde>