cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Republish only metadata inside viewable

Republish only metadata inside viewable

When changing states with the option publish.publishonepmdocumentchange set to true, the entire model/drawing is republished.  If it takes 30 minutes to publish that is 30 minutes lost for a mere state change.  If the file content isn't changing, why doesn't it just update the pvs file?  In the case of PDF it should send the PDF to the AEM only.  AEM is capable of updating existing watermarks from previous publishing using the replaceExisting function.  (Along with some other switches I'm sure).  This would save considerable time as the documentation is reviewed and goes through it's lifecycle.  There would need to be options for the various metadata changes.  (Perhaps publish.<doctype>.<internal attribute name>.  The reason for the individual attribute is because some companies do need a full republish while others are just attribute updates within the viewable.  For instances with us, rename would need a full republish because that is on our drawing.  However the majority is just state changes and that bogs down our workers when running ECN's like most people do.

1 Comment
Pearl

Totally agree. PTC should provide a mechanism to change meta data without republish the complete model, assembly or drawing.

Most of my customers are really angry that the worker is most of time full of jobs. A renaming also creates jobs for each iteration.

Another possibility is that PTC creates more specific preferences for each action. E.g. should a publish job be created when the object is moved to another folder, or another context, or for which lifecycle state,... this will just minimizing the numbers of jobs and not the conversion length of it. Especially for Inventor and Solidworks a publish job can run for 1.5 hours and longer...