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. (Hii ni mpya-kuajiri juu-bweni fomu kutumiwa na Rasilimali kwamba yazindua workflow).
Kufikia lengo, Mimi umba kuundwa mbili ngazi ruhusa mpya ("create and update" and "update only"), broke inheritance for the form library and assigned permissions to a "create, update" user and a separate "update only" mtumiaji. The mechanics all worked, but it turned out to be a little more involving than I expected. (Kama wewe kujisikia shaky kidogo juu ya SharePoint ruhusa, angalia hii baada ya blog). 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, Nilifanya zifuatazo:
- Kujenga mpya ruhusa ngazi.
- Wazi mbali chaguzi zote.
- Selected only the following from "List permissions":
- Hariri Items
- View Items
- View za Maombi
Kuchagua njia hizo inaruhusu mtumiaji update fomu, lakini si kujenga.
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, lakini zinageuka ni.
Create-and-Update was even stranger. I followed the same steps, 1 kupitia 3 juu ya. I had to specifically add a "Site Permission" chaguo: "Use client integration features". Tena, maelezo kuna haina kufanya hivyo kuonekana kama inavyopaswa zinazohitajika kwa ajili ya fomu InfoPath, lakini kuna ni.
</mwisho>