We are facing a strange behaviour, since we switched from network folders to Vault 2011 Professional.
If we create a new revision of an iPart factory and make changes to that factory, members that are placed in assemblies already reflect the changes, although they have not been revisioned and re-generated. It seems like the member is already fetching the latests revision of the factory from Vault by default.
Best regards
Erik
I investigated a bit more.
So when placing an iPart member, you can choose between "Latest Revision" and for example "Revision 00".
When you place the member with a fixed revision, everything stays as it is, when you change the revision of the factory.
When you select latest revision, any revision changes on the factory will be directly shown in the assembly, though the member was not updated yet, leading to an "Edited out of turn" of the factory.
In my opinion, the option "Latest Revision" makes no sense at all for iParts.