As a Dynamic Document developer I have to deliver XML/Graphics to my customer. Our development process can span months/years and to manage milestone checkpoints a baseline is created for each. There are instances where a book or chapter map do not get revised from milestone to milestone, keeping them at the same version/iterations. The primary object, a book or bookmap, for any given baseline, may be the same version/iteration as the last. The best method of tying a baseline to a new primary object is to revise the book. This would ensure an "Export Compound Document" of a version/iteration would be exactly what was baselined.
i.e. Each baseline contains a new version of the primary object. Arbortext Browser would export the primary object and all associated and versioned dependents in that baseline. The structure is downloaded locally for delivery to the customer.
A solution could be that a baseline requires a revision change to the primary object. That could lock the baseline down to a version of the book, and all the linked dependents, that can then be exported with "Export Compound Document". Again books get minimally revised during development, so an automated revision to the book to create the baseline should solve this issue.
I'm not sure I'm understanding this one.
As I mentioned in the related idea, the correct way to open a set of specific versions is to add them to a workspace using the Windchill UI.
The Windchill UI does not require that the baseline be tied a specific revision.
When you use the Workspace UI in Windchill you can also add specific versions of individual documents. For instance, use all of the documents in baseline X except for the copyright document where you want to use the latest copyright notice. You would just add the specific version of the copyright to the workspace before you open Arbortext Editor and connect to the Workspace.
Thank You@plutsky I've tested the steps mentioned above and was able to successfully load baseline files into my workspace and open in Arbortext Editor. Also was able to specify what version of those files would be in a baseline. Does what you mention above support the idea of branching? Windchill seems to lack the ability of starting with a baseline and branching off and making updates to a non latest version of a file. Wondering if there is way to get really close to that with baselining, and if so, how?
In general the Arbortext integration does not handle branching. We support checking out the latest revision/iteration. It is possible to checkout non-latest in the Windchill UI, but the Arbortext integration does not always support that properly. Unless the author really knows the details, it is best to not try it.
@plutsky Thank you. Since this request is similar to idea Export-Compound-Document-w-baseline-option-if-Dynamic-Document it can be considered current functionality.
We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.
You can always post a new idea with all the details required in the form.
Thank you for your participation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.