Ibi est a communibus missionem InfoPath formae. Nos volo patitur populus implere ex InfoPath formae et subire eos ad a bibliotheca. Nos volo praesepia (et non aliud) ad aditus ad formae.
Occurrit quaestio, et deinceps formae (e.g. http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/76ccef5a-d71c-4b7c-963c-613157e2a966/?prof=required)
Hoc est a velox via ut solvere possint placere contentus in bibliotheca formam. Vade bibliotheca scriptor version occasus et erexit illum ostenderat:
Click in "contentus approbatione Requirit" et quod tibi dabit valorem Draft colligunt Item Obses.
It’s a little counter-intuitive because we don’t think in terms of “content approval” when all we want to do is prevent people from seeing other users’ forms. Autem, it works well (in experientia). Just don’t approve those forms and they’ll always be considered “drafts”.
Give approval rights to the people who should be able to see them and you’ve closed the loop.
This isn’t exactly big news, but the question does come up with some regularity, so I thought it would be worth posting.
</finem>
Sequi me in Twitter ad http://www.twitter.com/pagalvin
HI Paulus,
Thanks for the basics. Unfortunately I don’t have 2 accounts at the moment (to test as a both Approver and Member). For the “Only users who can approve items (and the author of the item)” option we’re talking about here, is the system using both the “Created By” et “Modified By” fields to determine these access rights?
For this to work properly is it also calculating on the “Created” et “Modified” dates?
E.g. UserA created the document on 2010-07-23-0945 (it was approved, etc. etc) then UserB modified the document on 2010-07-24-1330.
In this case is the mechanism intelligent enough to only let UserB see the Draft version? Or can both UserA and UserB see the Draft version?
Gratias,
Brussius
P.S. mstechblogs is taking forever to load…
Brussius, sorry for never responding. I hope you found out what you were looking for along the way.