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

Extend Prohibit Publishing with Regular Expressions Matching

Extend Prohibit Publishing with Regular Expressions Matching

In Windchill Visualization Services (WVS) we can prohibit publishing of individual objects but out-of-the-box there is no way to filter out specific file types (MFG, IDX, CATPART, etc).  If you check in a CAD Document or Document to Windchill it will be considered as an EPM Document or WT Document and will be scheduled for publishing regardless of WVS' ability to actually publish the content.

We don't always want to limit publishing by file type.  We sometimes use semi-intelligent naming conventions to identify file sub-types.  For example, some companies include adding 'ESR' to the file name to identify external simplified reps.  All the out-of-the-box ECAD template models fail publishing and have to be prohibitied one at a time even though all begin with "ECAD".

The current limited functionality results in a lot of publishing failures, erroneous/useless publishing statistics and overloaded/unstable publishing queues. It unnecessarily adds to the already overwhelming WVS maintenance and monitoring effort. 

These situations can be resolved by PTC enhancing the current Prohibit Publishing functionality to accept regular expression matching (e.g. search rules) for Name, Number, and/or File Name.  For example, if the Number includes '.MFG' then prohibit publishing.

Today the only workaround is to write and maintain a WVS customization to exclude non-publishable types.  As far as I know there is no way to prohibit publishing by regular expression name/number/file name matching.

3 Comments
Newbie

Support for Regular Expressions should be throughout Windchill, not just for publishing control. If you agree, please vote for it at http://communities.ptc.com/ideas/1035

Newbie

This is something that you have always been able to do. Because we cannot predict what people will want to do to control what objects get published, we provide a hook that lets you insert your own business logic to determine what is published and what is not.  The supplied OOTB implementation in 10.1 is targeted at small customers and allows you to control what is published based on the file extensions of the CAD files.  The source code is supplied for that, and you can easily use regular expressions based on whatever attributes you have on the CAD documents to control what is published.

If you look in wvs.properties.xconf for "publish.service.filterepmdocumentpublishmethod" that will describe how to use the hook and where to find the source for the OOTB implementation that you can modify to suite your requirements.  Alternatively technical support would be able to help you.

Community Manager
Status changed to: Archived