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?
Move action is consider as unknown job source for publishing
to filter these objects we need to identify specific EPMDoc attribute which identifies these objects uniquely (e.g. name, number, any user created attribute)
Find the sample attached example xml
You can also find out epm* attributes which can be used by launching representation in Creo View
With the provided xml it will only disable the publishing for container equals to target folder in move operation. Along with it this will also disable the publishing for any other metadata change (state change or rename when in that context)