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. (Dan huwa ġdid-kiri forma on-imbark użata minn riżorsi umani li tniedi workflow).
Biex jintlaħqu dan l-għan, I ħolqot ħolqot żewġ livelli permess ġdid ("create and update" and "update only"), broke inheritance for the form library and assigned permissions to a "create, jaġġornaw" user and a separate "update only" utent. The mechanics all worked, but it turned out to be a little more involving than I expected. (Jekk inti tħoss ftit dgħajfa fuq permessi SharePoint, check out dan 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, Jien għamilt dan li ġej:
- Oħloq livell permess ġdid.
- Ċar bogħod għażliet kollha.
- Selected only the following from "List permissions":
- Edit Punti
- View Partiti
- Ara Pages Applikazzjoni
Għażla ta 'dawn l-għażliet jippermetti utent li taġġorna forma, iżda mhux joħolqu dan.
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, iżda jinstabx huwa.
Create-and-Update was even stranger. I followed the same steps, 1 permezz 3 hawn fuq. I had to specifically add a "Site Permission" għażla: "Use client integration features". Għal darb'oħra, id-deskrizzjoni hemm ma jagħmilha jidhru simili hi jmissha tkun meħtieġa għal forma InfoPath, iżda hemm hu.
</aħħar>