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

Community Tip - Need help navigating or using the PTC Community? Contact the community team. X

Bursting for XML-documents has to be performed by Windchill, not Arbortext Editor

Bursting for XML-documents has to be performed by Windchill, not Arbortext Editor

Hello!

At the moment, the Arbortext Windchill-Adatapter is handling the bursting-process into Windchill.

This however, has the great disadvantage, that this will only takes place from actions inside Arbortext Editor and not from actions inside Windchill.

EXAMPLE:

On each root-element of our XML-doctype, we would like to have a 2-way-metadata-rule, which puts the Windchill lifecycle-state in that attribute.

When an XML-module is now being released inside Windchill, the state "RELEASED" is not updated in the XML-document. It would require a checkout from Arbortext Editor with an immediate checkin.

However, if the document is released, a checkout-change (updating the metadata-value)-checkin action should not be allowed.

The final goal is here to highlight sections of the publication in different colors or to display metadata (version, etc.) of all the modules. This is currently not possible or with additions to the default-delivery only possible for content holders content.

Therefor, we'd like to have all that bursting/xml-adapter-stuff to be moved from the Arbortext Editor adapter to Windchill itself, so that Windchill is able to keep the files up to date.


Thank you very much,

your Windchill-Team@DATACOPY

3 Comments
GregoryPERASSO
14-Alexandrite

exactly like the "file synch" for CAD files ...

should be easier to implement for an XML document

Pushpinder_Toor
13-Aquamarine

We are aware of this use case and request. It is on our long term roadmap to consider moving more functionality from client (Editor) to server instead.

PTCModerator
Emeritus
Status changed to: Archived