• State Verified Answer
  • Replies 1 reply
  • Subscribers 47 subscribers
  • Views 1129 views
  • Users 0 members are here
Options
Related

Branches not picked up by Publication Manager

Joakim Nybäck

I have a small test publication where there are two instance of a module:

* version 1, in Source draft state
* branch 1.1.1, in Source draft state

Note that there is no version 2.

In Publication Manager, Baseline tab, the "New version" column indicates "No". Autocomplete with "latest available" option has no effect.

Now, it does say "New version" in the UI, not "New version or branch"...

I think this must be a design decision rather than a bug? Could you share the rationale behind this behavior.

I am using:

SDL Knowledge Center Publication Manager 12.0.2417.0
SDL Knowledge Center Content Manager 12.0.3215.1
Rate translation
×
Suggest better translation
×
Parents
  • 0
    Hey Joakim

    Your observations are correct:
    - branched versions are never taken into account when autocompleting the baseline.
    - the built-in check in the baseline tab for "New Version" does not look at branches.

    This is by design. Branches should be seen as 'breaks' in the version history of an object. Only the main version tree is considered by the tools. Branches are ad hoc exceptions where the version logic of an object gets broken. A branch is technically a new object which can have its own versions and where the content changes do not make it back in the main version tree (1.1.1 > 1.1.2). Tecnically speaking, a branch or any of its versions could even be branched, again with its own versions (1.1.1.1.1).

    The tools would not know how to handle all these mixed version trees caused by branches. Hence we only use the main version tree. (1 > 2 > 3).

    Hope this helps,
    Kurt
Reply
  • 0
    Hey Joakim

    Your observations are correct:
    - branched versions are never taken into account when autocompleting the baseline.
    - the built-in check in the baseline tab for "New Version" does not look at branches.

    This is by design. Branches should be seen as 'breaks' in the version history of an object. Only the main version tree is considered by the tools. Branches are ad hoc exceptions where the version logic of an object gets broken. A branch is technically a new object which can have its own versions and where the content changes do not make it back in the main version tree (1.1.1 > 1.1.2). Tecnically speaking, a branch or any of its versions could even be branched, again with its own versions (1.1.1.1.1).

    The tools would not know how to handle all these mixed version trees caused by branches. Hence we only use the main version tree. (1 > 2 > 3).

    Hope this helps,
    Kurt
Children
No Data