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. (Hau da, berri-kontratatu on-barnetegi inprimaki Giza Baliabideetako ek erabiltzen duen workflow bat jarri du abian).

Helburu hori bete ahal izateko, Sortu sortu dut bi baimen mailak ("create and update" and "update only"), broke inheritance for the form library and assigned permissions to a "create, eguneratu" user and a separate "update only" Erabiltzaileak. The mechanics all worked, but it turned out to be a little more involving than I expected. (Sentitzen duzu, pixka bat bada, dar-dar SharePoint baimenak, begiratu blog post honetan). 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, Honako hau egin nuen:

1. Berri bat sortzeko baimenik maila.
2. Garbitu kanpoan aukera guztiak.
3. Selected only the following from "List permissions":

• Elementuak editatu
• Ikusi elementu
• Ikusi aplikazio orrialdeak

Aukera horiek hautatzean, erabiltzaileak inprimaki bat eguneratzeko, baina ez da sortu.

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, baina bihurtzen da.

Create-and-Update was even stranger. I followed the same steps, 1 bidez 3 Goiko. I had to specifically add a "Site Permission" aukera: "Use client integration features". Berriz, deskribapena dago, ez du dirudi InfoPath inprimaki bat egon behar da, behar bezala, baina ez da.

</amaiera>