enabling the property publish.republishonepmdocumentchange will create representations on all metadata changes.
For example on rename -> all Iterations of the renamed epmdocument will be republished. In most cases this is not intended and creates an massive worker load.
More specific republish properties such as publish.republishonstatechange or publish.republishonrename .... can resolve that kind of issues
I beleive you could create a listener that watches for those events and then executes a republish. If it is a workflow making the change you could add the republish following the line that changed the object, but I suspect you are talking about manual actions performed by a user.
Not that having more granular control OOTB is bad.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.