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

Publish Arbortext to (graphic?) wtDocument

Aquamarine

Publish Arbortext to (graphic?) wtDocument

We are in the process of rolling out wtpart centric PLM.

To do that we are mapping CAD Documents to wtParts and also the Dynamic Document (Arbortext) Assembly Instructions.

The problem is that the Assembly Instructions can revise without revising the wtpart and or CAD Document. When that happens the Content relationship from the wtpart to the Dynamic Document is broken.

The workaround is to iterate the wtPart and restructure the Part to the Dynamic Document. This is world be inefficient.

Wondering if anyone has experience publishing the content from Arbortet dynamic document as the primary file of a wtDocument?

The reason is to use the Reference Document link to the wtPart that would enable the link between the wtPart and wtDocument regardless of Version of each.

3 REPLIES 3

Re: Publish Arbortext to (graphic?) wtDocument

The characteristics of the link you use between document and part is important. EPM Build links (owner, contributing content, contributing image, image), Content, Describing Doc are all WTPart version to EPM/Document version. Any changes to link are captured by a new version of WTPart.

  • Iterating or revising a WTPart in isolation will copy the links forward onto the new WTPart version. Resulting in multiple versions of WTPart linking to one version of document.
  • Iterating an EPM/Describing Doc will create a new version of WTPart automatically. The new document version is linked to the new WTPart version (with same link type).
  • If you revise an EPM/Describing Doc in isolation the new Doc revision will NOT be linked to any WTPart.
  • If you revise the EPM/Describing at the same time as "EVERY" linked WTPart, the links are carried forward onto the new revisions of WTPart and EPM/Doc.

Reference Links (used by Reference Document) are WTPart version to Document Master. Every "linked" version of WTPart points to latest version of document (with optional state filtering)

If neither of these characteristics suits your needs it is possible to create your own links, but this is customization.

When engaging in the practice of revision syncing documents with WTPart, the moment you have multiple associated documents this can cause problems.

Re: Publish Arbortext to (graphic?) wtDocument

EPM Doc links similar to Describing Doc

Re: Publish Arbortext to (graphic?) wtDocument

I am looking at using Publishing rules to create a Published Delegate!

I can see a link from the wtDocument (delegate) to the Dynamic Document called Related Representables and from the Dynamic back to the wtDocument called Published Content.

What I need to know is if it's possible to control the version between the Dynamic Document and the delegate wtDocument?

This support page

Seems to indicate that if the delegate wtDocument will need to be revised with the Dynamic Document together to keep the same Version.

Announcements

Thingworx Navigate content has a new home! Click here to access the new Thingworx Navigate forum! ______________________________ Check out the Windchill Tips Board! We're talking about Whirlpool's use of digital twin, augmented reality, and data-driven design!

The NAVIGATE WORKING GROUP is here! Come innovate with PTC!

Sign up for a Working Group