Workflow with intermediate releases

Follow

Christina Force

January 30, 2015 19:29

I'm a new user, and couldn't find this particular issue in the documentation, and know it will be something I'll encounter often: 

What is the recommended workflow to handle document changes in Scroll Versions for intermediate releases that are created -after- a "later" release? 

For example: My current content is all in v1.0. I create a version 2.0 (with 1.0 as the preceding version) and start creating page updates to reflect 2.0's changes. The version tree is nice and linear, awesome. Suddenly, we need a 1.5 release, so a 1.5 version is created, also using 1.0 as the preceding version. I have to add in v1.5 changes to the same page that will also house v2.0 changes. The version tree is now branched. 

I would expect that i'd be able to make the v1.5 changes, then either: 1) Merge 1.0 and 1.5 together, and those changes should be carried through to 2.0, or 2) Change the "Preceding Version" for 2.0 to v1.5, making the tree linear again. However, when I tested these out, neither of these options appear to actually include the 1.5 changes in the 2.0 versions of the pages. Can you clarify the recommended process to handle this type of situation?

0

• 

  Peter Bastian February 03, 2015 11:07

  Hi Christina,

   

  the 'preceding version' functionality doesn't quite work that way. 

  When a new version is created with a preceding version, there are actually no pages created. When a page of the new version is shown, that hasn't been edited in the actual version yet, the content of the page in the preceding version is shown ('fallback'). 
  As soon as the page gets edited in the actual version, a page is created for this version with the content of the preceding version. From now on, the two pages are independent of each other. That means that if the page in the preceding version gets changed, the actual page doesn't get touched at all.

  So the preceding version functionality only considers whole pages, not the content.

  That's why the changes of your version 1.5 aren't taken over to version 2.0, when the page already has been edited, because the two pages are independent of each other.

  I hope this helps to clarify this issue. If you have any further questions, feel free to ask.

   

  Cheers,
  Peter

  1

  Comment actions Permalink
• 

  Christina Force February 03, 2015 19:35

  Thanks Peter -  So this means once a page has been edited, if changes are needed to any earlier versions of that page, the earlier version change needs to be copied and pasted into each later page version separately, correct?

  0

  Comment actions Permalink
• 

  Peter Bastian February 05, 2015 09:24

  Hi Christina,

  yes, that's correct. Once a new versioned page is created the page does not fall back to a previous version.

  Cheers,
  Peter

  0

  Comment actions Permalink

Please sign in to leave a comment.