Post publish delegates are quite powerful and widely used and supports in storing / updating neutral content from native 3D / 2D content. But often the current configurable approach using publish rules may not be suitable for certain requirements. Below are some use cases where we see a need to extend this delegate.
Different rules needed for different product containers.
Creating several publish rules for containers and maintaining them is difficult.
Finding existing documents using multiple criteria (If object not found with one criteria use second criteria).
Updating the file name after the WTDocument is created.
I see that this is possible by using EDR Loader extensions but having the capability to do this within post publish delegate helps us having less customizations.
Linking WTDocuments with WTParts
Setting IBA values with custom values derived from other parameters from WTPart and EPMDocument.
I understand that we have to take care of revisioning and other cases with respect to Published Content Document linkage of WTDocument with EPMDocument. But on the other hand, having so many limitations makes this delegate less usable and forces customers to look for alternative solutions outside of Windchill.
Please let us know if there are any other better ideas to manage these requirements OOTB.