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

Allow published office document to update Windchilll attributes

Allow published office document to update Windchilll attributes

currently when publishing office document containing Windchill attribute (eg: version, lifecycle state), the published PDF does not display the updated Windchill attribute value. As a result, the published office PDF does not reflect the correct Windchill information.

eg: A Word document contain a field linking to Windchill version attribute. This document at version "1.1". When checkin, the document iterate to version "1.2". The publsihed PDF for document version "1.2" is showing version "1.1" rather than "1.2".

8 Comments
Regular Member

Hello

I do not know what publisher you are using ? The one from Windchill ?

We use a third party software called PSW and we do not have the problem you report.

I am sorry but you post should be for a technical support rather than an idea for further improvement.

Contributor

Hi Chris,

Yes, I'm using the office publisher for Windchill. I've already created a call with PTC TS, in regards to this issue. PTC TS says it is a current limitation of the office publisher and working according to specs and this functionality would need to be submitted as an enhancement request.

I understand there might be other 3rd party software that would be able to resolve this issue. However, the purpose of this idea is to incorporate this functionality into the current Windchill Office publisher not using another 3rd party software.

sm
Newbie

Hi can you clarify the issue here? Are you stating that all documents are published with the wrong information across the board?

It is my understanding the Office Worker will sync all the Windchill Attributes in the Office document at the time of publishing. However, if the document's State, History or attributes have changed since publishing and no subsequent checkout/checkin operation has occurred to trigger a new publish request, there is a possibility the published document could be out-of-sync.

This is only the case for the publised PDF. If you are openeing the source document with Windchill Desktop Integration (DTI), the document will have it's attributes synced upon retreival. If you are not using Windchll DTI, the document attributes will not be synced since Office does not know how to do this on it's own and relies on Windchill DTI to do it.

If you have reference case/spr numbers associated with this request, please share.

Contributor

Hi Scott,

This is the article that PTC TS send to me: https://www.ptc.com/appserver/cs/view/solution.jsp?n=CS57428

I've relook into this issue and make a few tests and is able to update the Windchill attribute when publishing.

These are required in order to update/sync the Windchill attributes when publishing:

1) DTI needs to be installed on the Office worker

2) these document worker settings must be set:

- For DTI Properties, checked the option "Enable Merge"

- For Document Update Field, ensure the value of either "All", "Auto" or "Merge" is chosen

PTC TS has confirmed it works

sm
Newbie

Excellent! Glad to hear TS was able to hook you up with all the required information to get it working as desired.

Participant

Here is the fundamental problem:

I save a Word document that contains a database parameter such as the release status, then I check in the file. Then we release the document and the release status changes in the database, but when the file is opened, Word does not pull the current parameter from the database, it shows the parameter value as it was when the document was last saved by the user.  And if you perform a "Refresh Properties" from the DTI toolbar, Word will correctly tell you the file has been changed and ask if you want to save it, which if the user said yes, would cause the object to need to be released again => circular.

The enhancement request could be to autosave the file anytime an automated process changes a parameter referenced in the file (version, iteration, release status).  This would occur behind the scenes and not affect the file state.  Another method to achieve the same purpose would be to automatically Refresh Properties when the file is opened and "Unrefresh" when the file is closed (before Word checks for changes upon close).

sm
Newbie

Yes, this is a well understood issue and something PTC would like to address in a future release of Windchill. There are some newer web services that will allow us to make these types of updates, but the work has not yet been committed.

At this time, the best way to avoid this is to install and configure Windchill Desktop Integration. This will refresh the attributes in the document when it is opened, something Word and Excel cannot do on their own. 

Community Manager
Status changed to: Archived