only version page in space
Hello,
we have recently introduced the Scroll Versions for Confluence app hoping to have proper versioning tool for e.g. minutes of meetings in a central MoM space.
We haven't found a way yet to establish a check&release workflow for pages in a space so that we can access the previous version of an MoM by the version indicator in the top bar. Currently, it counts up as soon as you create a new version for the entire space. Any chance to make that happen on a per page base?
Thank you
Stefan
-
Ideally, you would version pages that change not on every day but for a specific version schedule - like product releases. MOM when versioned, you will be required to create a version for every date when you want it versioned for. It is not productive unless the entire space gets to use these versions in that manner. If I understand correctly, I would not version MOMs but add a date variable in the content and prefix/suffix the date in the MOM page title.
-
Hi Stefan,
versions created by Scroll Versions app are space-wide versions. The use case for using the app is geared towards technical documentation. Other use cases such as yours might not be easy to implement and follow with Versions.
If you need versioning on a page level, why the built-in page revision history doesn't work for you?
Roman.
-
Stefan,
have you tried out Comala Workflows? You can use it to approve pages. If a page is edited after approval, it can be transitioned to a draft state automatically.
Would this help you out?
Roman.
-
I'll try to put in other words
I went through the documentation but still have difficulties to
understand if our scenario can be feasible by it. I'm aware of the
following Scroll Version Documentation
<https://help.k15t.com/scroll-versions/latest/scroll-versions-documentation-110528202.html>
entries:1. Roles and permissions
<https://help.k15t.com/scroll-versions/latest/roles-and-permissions-153653325.html>
2. Intro to Workflows
<https://help.k15t.com/scroll-versions/latest/intro-to-workflows-153651322.html>
3. Intro to Publishing
<https://help.k15t.com/scroll-versions/latest/intro-to-publishing-150570014.html>
4. How can I lock version editing after publish?
<https://help.k15t.com/scroll-versions/latest/how-can-i-lock-version-editing-after-publish-110532097.html>
5. Manage versions
<https://help.k15t.com/scroll-versions/latest/manage-versions-153651332.html>
6. Publish a Version
<https://help.k15t.com/scroll-versions/latest/publish-a-version-110528291.html>
7. and the before mentioned so-called Private Master Space
<https://help.k15t.com/scroll-versions/latest/collaborative-editing-how-should-i-work-with-the-editor-s-draft-and-publish-functions-121930659.html>
approach, where Work in one space and publish to another space,
wherein you make us of the Confluence permission only.but as said before we have a frequent meeting with one of our key
suppliers. For those purposes, we have a collaborative space in
Confluence wherein we create and intend to archive our MoMs in the future.
We would like to achieve, that during the creation of the MoM, it is
only accessible to the smallest group (the attendees). During the review
process, it shall be editable by some more people (e.g. those who got a
task assigned to). After it was published it shall be accessible to
anyone who has access to this space but in read-only.According to the above-referenced articles, our scenario must be somehow
feasible but I miss some clear illustrations (pictures or may even
videos) showing the setup process and giving us an impression how the
space looks like during the process depending on the user's role. All
that I can say that we would follow the Public Master Space approach.
<https://www.k15t.com/blog/2013/12/best-practice-managing-versioned-documentation-in-confluence>Due
to that limitation and the fact that I don't have the possibility to
play around with Scroll Version I would highly appreciate if you could
provide some screenshots.Moreover, there should be an option to easily access previously
published version of an MoM (page) but as the version counter reflects
the entire space an addition button/function would be necessary. Could
that be done by Page Properties Macro
<https://confluence.atlassian.com/doc/page-properties-macro-184550024.html>? -
Hi Stefan,
I am sorry if I am not seeing the whole picture from your detailed description.
In order to answer your questions, I would to understand exactly what you need and why.
We have a collaborative space in Confluence wherein we create and intend to archive our MoMs in the future
Could you please explain what MoM stands for?The fact that I don't have the possibility to play around with Scroll Version
Why don't you have the possibility to do so?There should be an option to easily access previously published version of an MoM (page) but as the version counter reflects the entire space an addition button/function would be necessary. Could that be done by Page Properties Macro?
Would you like Page Properties Report to shot the page version? Or a control in the form of a button to select the page version?Roman.
-
Hi Stefan,
you have a very specialized and unusual use case and we will do out best to try and solve it. However the separation of the conversation across multiple channels only adds to the confusion and doesn't accelerate the process.
For that reason I would like to ask you to only use the support ticket for communication to keep the whole truth in one place. I will have a look at all of the conversation so far and answer in the support ticket as well.
Thanks you,
Cheers,
David
-
-
Could you please explain what MoM stands for?
Minuntes of Meetings -
Why don't you have the possibility to do so?
Our productive system still runs with Confluence V6.5 what is too old for Scroll Version. The testing instance is supposed to be on a newer state but it hasn't been stable for a while and the admin is on vacation until the end of the month.
I'm trying to get access to an Confluence Cloud demo through our Atlassian Partner but discussion has just started. I know that situation is more than only embarrassing and quite frustrating for the power user of us but that is how it is at the moment. -
Would you like Page Properties Report to shot the page version? Or a control in the form of a button to select the page version?
Second would be excelent but we may couldgo with the first one
--------
-
For that reason I would like to ask you to only use the support ticket for communication to keep the whole truth in one place.
will do, you are welcome
Thanks for our interest in my challange!
Stefan
-
Could you please explain what MoM stands for?
-
I need to warm this up. I am new to Scroll Versions and if I had known that I can only version spaces... Now I have to deal with it.
What do we have:
Product 1 = space
Manual for the app for users = page with subpages
(changes frequently but not with every new product version - 1.0 May 2019, 1.1 Jun 2019, 1.2 Dec 2019, 2.0 Feb 2020)Manual for the app for administrators = page with subpages
(changes frequently but not with every new product version - 1.0 Aug 2019, 1.1 Oct 2019, 2.0 Dec 2019, 2.1 Mar 2020)Manual with a practical example including both apps = page with subpages
(changes slowly - 1.0 Jun 2019, 1.1 Jan 2020)Manual with deeper info for a single topic of the product for both apps = page with subpages
(changes slowly - 1.0 Nov 2019)Many manuals more = pages with subpages
Product 2 = space
another big structure
Product ...
There are just two writers. They cannot write as quickly as development goes on. Versions are finshed at different times. Sometimes you can only manage to do one manual at one time.
It looks like we need to create one space for one manual. Because of content reusage we would need to create a reuse space where all other spaces get content from.
Many spaces don't help to have an overview.
The other way, using the product version and producing all manuals again for each version would mean, I need some kind of batch export to pdf or html whereby a few manuals have variants. Is that possible? In this case, a few manuals have changes and most of them don't when batch export is running.
In this case, is it possible to generate one version history document for all manuals as an overview?
Danny
-
Hi Daniela,
My name is Dash, and I am a product manager at K15t. My team and I work on the app called Scroll Documents for Confluence.
With Scroll Documents, you are able to manage a page tree (page with its sub pages) as a single unit of content called 'document'. You can then create versions of your document, compile documents from existing pages, export your documents with Scroll PDF and Word exporters, and much more.
With Scroll Documents, you are able to create and version multiple documents within a single space, something I see is a critical aspect of your requirements. Also, if you do not have complex content reuse requirements, then the app can provide a simple but powerful way to reuse existing content as well.
If you find the app interesting for your use case, I would love have the opportunity to talk with you to better understand your requirements.
Cheers!
Dash
-
Hi Dash
Thank you very much for your answer. I need to reuse existing content, full pages as well as small sections within a page.
Is it possible to use Scroll Versions and Scroll Documents in combination? Versions for reusing content (then there would only be one version for the space which never changes) and Documents for creating the required versioned documents?
Regards
Danny
-
Hi Daniela,
Unfortunately, it is not possible to use both Scroll Versions and Scroll Documents in combination. They are not compatible with each other due to the underlying architecture of the apps.
Here's an article highlighting the difference between the apps that might be helpful -
I wanted to point out that, Scroll Documents enables page level content re-use. You can create a global reuse library in a dedicated space as well as a local one within each product space utilizing some of the best practices highlighted here -
Once organized, you will be able to add them to your documentation easily with the help of the document composer.
I hope that helps.
Best regards,
Dash.
Please sign in to leave a comment.
Comments
13 comments