When collaborating around a large scale project, using IW 360, we need to use “Proposals” as one way of keeping data separate between disciplines. At a later date we can then “Merge” it together to a complete proposal.
What we have discovered regarding proposals is that anyone (with Publish rights) opening a model can edit/erase a Proposal, no matter who created it. That is not great.
Because ADSK IW 360 is aware (has info on) who created the proposal it should of course protect the proposal being modified by others.
If someone want to edit data in another user's proposal they can create their own proposal and merge the other proposal in to it.
As it is now, user A can create Proposal “Ideas from A”, publish it. User B finds it and get it accessible when synchronizing.
User B does an edit of the proposal “Ideas from A” at the same time as user A keeps working on it. Then we have two versions of the proposal and every time any of the users synchronize the model it overwrites the existing.
Not good!
Please consider a “locking” of proposals depending on who created it.
