We have family tables stored in a read-only product. When the family tables are updated, they're moved from the read-only product to one with write access. The family tables can then be checked out, updated, checked back in, and moved back to the read-only product.
Moving the family table along with its instances facilitates the publishing of every version of every instance. This creates thousands of unnecessary items being sent to the publisher.
How do I configure the publishing rules in the Worker Agent to prohibit this behavior?
There are several ways to go about this requirement:
Thank you Vishwas.
we are so numerous needing to prevent the worker from republishing objects that are simply moved from products or libraries to others that i am wondering why there is no easier way to activate this.
But on your post, you wrote : 1-Disable publish/republish on EPMdocument change :
Can be disabled using following properties in wvs.properties publish.republishonepmdocumentchange=true
which sounds a bit contradictory when reading (republish=true whereas it should disable republish...)
Then you route to https://www.ptc.com/en/support/article/CS238377 where the first lines say to set properties as publish.republishonepmdocumentchange to false. So it's confusing me a little.
I am really looking for something easier to set in place from PTC as it is a common will for Windchill admins to skip those users request asking for purging unwanted publish jobs that prevent their own promotions and publications to be printed out quickly.