Hmm.. looks like the archive tab should probably check for edit tree-based approve permissions too. Unlikely to be able to roll back without being able to approve. What do folks think?
I agree with that. Moreso, I can even see situations where someone might be able to "Approve" but never be able to "Rollback". Althought this could be handled more "procedurally" than automatically (ie. through a manual policy).
The permissions are simple yes no checks. It's only the dmNavigation permissions that have an inheritance model. This means that whatever scheme we come up with it will be limited by the ability to inherit only a subset of permissions.
The new features in v2 have kinda of escaped our usual QA. We really need to come up with a spreadsheet or something that detail all the permissions and the their implementation with regard to default roles -- a test plan. Then we really need to test that things have been implemented this way :)
Anyone want to put their hand up for building a thorough test-plan for default permissions in v2?
-- geoff http://www.daemon.com.au/
--- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
