Use of baselines (or other method?) to "lock down" versions of bursted EPMDocuments?
(apologies in advance: thinking of cross-posting since not sure which forum will have the right audience...)
Just posted this as a PTC call to the group supporting the Arbortext <=> Windchill Content Adapter - hoping someone here also may have some tips / useful experience to share:
While we understand that the HREF can include the version identifier for objects in the Content Manager (i.e., "x-wc://file=0000014024.xml&iteration=C.1"), we don't see this iteration identifier included in the HREFS inserted into bursted objects currently.
Please help to guide us towards the best way to implement our requirement of "locking down" the set of objects comprising a published result ("product view") as part of our product workflow.