I've got a problem with the way Windchill manages "latest" representations and the property publish.republishonepmdocumentchange. The support tells me it's normal, but I would like to know if someone found a workaround. I've got the properties :
publish.configspec.default.useasstoredifavailable=false (we want the latest iteration of an assembly to be up to date)
publish.republishonepmdocumentchange=true (we want the drawings to be republished with the latest lifecycle state or name/number)
I create an assembly A1 :
I modify it by mooving a component, it goes to A.2 :
I modify one part, the representation is marked as out of date and I can republish it with the scheduler :
Iteration A.1 is not out of date, that's what I want, I've got my history.
No problems there, I republish and I've got my A.2 representation updated.
But if I rename the assembly Windchill republish every iteration including the old ones and I now have A.1 representation with the components at the right place but with the new part instead of the old one...