Community Tip - Have a PTC product question you need answered fast? Chances are someone has asked it before. Learn about the community search. X
You need to use the concept of Business Rule that has been introduced in Windchill 10.x. If you are in 9.x version then you dont have an option to control with customizations....One simple thing you can try is to assign a junk queue group to all of these publisher queues and fail the publish instead of processing the publish on the CAD Worker...
I'm with Steve V,
You can try:
<property name="publish.service.readytopublish.enabled"" overridable="true" targetfile="codebase/wvs.properties" value="false"/">
<property name="publish.republishonepmdocumentchange" overridable="true" targetfile="codebase/wvs.properties"</p">
value="false"/>
<property name="publish.publishonepmdocumentchange" overridable="true"targetFile="codebase/wvs.properties"</p">
value="false"/>
<property name="publish.service.documents.upload.enabled" overridable="true"targetFile="codebase/wvs.properties"</p">
value="false"/>
<property name="publish.service.documents.upload.markoutofdate" overridable="true" targetfile="codebase/wvs.properties"</p">
value="false"/>
<property name="publish.service.documents.checkin.enabled" overridable="true" targetfile="codebase/wvs.properties"</p">
value="false"/>
<property name="publish.service.partalternaterep.checkin.enabled"overridable="true"targetFile="codebase/wvs.properties"</p">
value="false"/>
The readytopublish service somewhat replace the service.publish.enabled. To make sure you only publish using workflow expression, you can set all the above to false.
Hope that helps,
Patrick
In Reply to Joginder Matharu:
You need to use the concept of Business Rule that has been introduced in Windchill 10.x. If you are in 9.x version then you dont have an option to control with customizations....One simple thing you can try is to assign a junk queue group to all of these publisher queues and fail the publish instead of processing the publish on the CAD Worker...
You don't need to shutdown all your Publishing Queues. Actually you shouldn't do anything from the queues. You should just go to the WVS monitor and delete your jobs there first. You still need your queues running to clear things out. Depending on how many workers and jobs submitted, the publishing worker queues do not recieve a job from the main publishing queue. So, it is very messy and not efficient if you just stop the queues and delete entries. It is best practice to delete the entries from the WVS Publish Monitor for jobs not even assigned or just assigned to a worker queue.
You will still be able to publish with rules and so forth from expressions in the workflow because the publishing rules are based on a successful execution of a publish.
In Reply to Patrick Chin:
I'm with Steve V,
You can try:
value="false"/>
value="false"/>
value="false"/>
value="false"/>
value="false"/>
value="false"/>
The readytopublish service somewhat replace the service.publish.enabled. To make sure you only publish using workflow expression, you can set all the above to false.
Hope that helps,
Patrick
In Reply to Joginder Matharu:You need to use the concept of Business Rule that has been introduced in Windchill 10.x. If you are in 9.x version then you dont have an option to control with customizations....One simple thing you can try is to assign a junk queue group to all of these publisher queues and fail the publish instead of processing the publish on the CAD Worker...
Hi David,
Are you sure you want to completely stop publishing via WVS? If you need workflows to run publishing, you still need to have publish service enabled which means you need this configuration:
<property name="publish.service.readytopublish.enabled"" overridable="true" targetfile="codebase/wvs.properties" value="true"/">
but the rest to false:
<property name="publish.republishonepmdocumentchange" overridable="true" targetfile="codebase/wvs.properties"</p">
value="false"/>
<property name="publish.publishonepmdocumentchange" overridable="true" targetfile="codebase/wvs.properties" value="false"/">
<property name="publish.service.documents.upload.enabled" overridable="true" targetfile="codebase/wvs.properties" value="false"/">
<property name="publish.service.documents.upload.markoutofdate" overridable="true" targetfile="codebase/wvs.properties" value="false"/">
<property name="publish.service.documents.checkin.enabled" overridable="true" targetfile="codebase/wvs.properties" <=" strong=">value="false"/>
<property name="publish.service.partalternaterep.checkin.enabled" overridable="true" targetfile="codebase/wvs.properties" value="false"/">
Your publish rules require readytopublish set to true. In the workflows expressions you can publish based on many types of object and itsattribute values.
Sorry, my mistake, I'm just wondering why you do or don't want anything to publish. Just from your statements, it just sounds like from a checkin or change.
I strongly recommend publishing through workflow expressions in Lifecycle states (i.e. Under Review, Preliminary Released, Released and Obsolete). Thus, watermarking and so forth can be applied. I really wish without customizations, simplified representations can be included into drawing 3d viewables markup objects. Thus, you don't have to transverse to the 3D large assembly for the full master representation which shows all your ID information.
Food for thought,
Patrick
In Reply to David Haigh:
We have a user that needs to check in multiple thousands of parts.
1. We don't want the publisher overwhelmed and shut off the workers. Jobs still go to the queue.
2. We then shut down all the publishing queues. Jobs still get submitted to the queue when the users check in their creo files, even when it's stopped.
3. We then disabled the publishing queues. Jobs still get submitted even with it disabled.
How do we configure Windchill so nothing goes into the queue while this huge check in process is going on?
David Haigh
Phone: 925-424-3931
Fax: 925-423-7496
Lawrence Livermore National Lab
7000 East Ave, L-362
Livermore, CA 94550