I have found this process very annoying also. I generally log in as Site Admin to delete those extra processes as I go. It would be very nice to eliminate this extra work and keep the other "real jobs" on track.
I agree with PTC that a move is a change of the object, since this information is documented in properties of the CreoView file.
But I agree also, that for may types of changes, a republish is not required.
Therfore in general, it should be easy to configure on which type of change a republish should be inniciated.
e.g. move, lifecycle change, ...
On top it would be grate, if it couls be configured also by the type of object.
E.g. lifecycle change of a drawing should be republished (think of a Lifecycle on a drawing) but upon a lifecycle change of a part, a republush may not be required.
Maybe a configuration like the additional files configuration could be a way to realise it.
We are so numerous needing this to be simple settings and not customization.
Any mass move between libraries and products could impact thousands of CAD objects very quickly and so preventing all other end users from getting their publications fast. It can last several days before a designer gets his drawing before all the unwanted publish jobs complete before him...
Having the publish.republishondocumentchange and the 3 others set to false does not change a thing, mass move still pushes thousands of objects in publication queues...
and deleting the jobs from the job monitor is what i think we would like to avoid. Thousands of job filling in the queues for nothing, real needs prevented from being published because of the ones already pending, and what about when admins are off-work... this is why i can see Windchill admins would like some tools here
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
