Hiding unfinished content

Comments

7 comments

  • Avatar
    Nils Bier

    Hi Edward,

    currently the workflow implementation has only basic functionality and it's not yet possible to control to only publish completed pages. We already have an improvement in our JIRA system regarding this functionality: https://k15t.jira.com/browse/VSN-864
    Please sign up at https://k15t.jira.com/secure/Signup!default.jspa to watch, to comment or to vote for this issue.

    As a workaround you have to manually set permissions to the pages you don't want to publish (make sure that you use different groups as defined in the Scroll Versions roles). I'll add this workaround to our knowledge base.

    I hope that helps.

    Cheers,
    Nils

    0
    Comment actions Permalink
  • Avatar
    Eva Mayrhofer

    Hi all,

    I would like to add my solutions to this request. Maybe they are helping!

    I am using conditional content of Scroll version to have unfinished content that is not included in the published documentation. 

    1. I have created an attribute "Internal" (under "Scroll Content Management" - "Attributes") in my source space. Observe that this source space cannot be accessed by the public (only certain persons are authorized to view/edit this source space).
    2. I have created a variant "NoInternal" (under "Scroll Content Management" - "Variants") in my source space.
    3. If phrases within an article are not finished yet, I insert Scroll Versions macro "ConditionalContents" and check "Internal" (provided under "Internal").
      If the complete article is not finished yet, I edit the attributes for the page (provided under "Variants" below the article header) - I check "Internal" (provided under "Internal").
    4. Every time I publish a version of the documentation (to a new space), I select variant "NoInternal".

    Result: The published version does not contain the phrases and articles for that I have checked "Internal". The new space can be accessed by the public.

    When the phrases are finished, I copy the phrases from within the macro "ConditionalContents" to the text outside of the marco (this is necessary as deleting the macro is deleting macro and the phrases), then I delete the macro "ConditionalContents". When the article is finished, I  edit the attributes for the page again (provided under "Variants" below the article header) - I uncheck "Internal" (provided under "Internal"). Then I publish (still selecting variant "NoInternal). Now the published version does contain the new phrases and articles.

    Maybe this seems a bit complicated, but this procedure works fine for my company for months now. 

    Cheers,
    Eva Mayrhofer

    0
    Comment actions Permalink
  • Avatar
    Nils Bier

    Hi Eva,

    that sounds like a proper workaround to me, thanks for sharing :-)

    Is it okay for you, if I add this workaround to our knowledge base, until we've improved the workflow functionality?

    Cheers,
    Nils

    0
    Comment actions Permalink
  • Avatar
    Edward Plumer

    Thank you Eva. That is a great idea and will serve well in the interim.  

    0
    Comment actions Permalink
  • Avatar
    Eva Mayrhofer

    Hi Nils,

    sure, go ahead. I am glad, if my workaround is of use to other users.

    Cheers,
    Eva

    0
    Comment actions Permalink
  • Avatar
    Eva Mayrhofer

    Hi Nils,

    I forgot to add the following for step "2) I have created a variant "NoInternal" (under "Scroll Content Management" - "Variants") in my source space."

    • Variant "NoInternal" must have condition "unset" checked under "Internal".  (Unset is automatically provided by Scroll Versions. This is important as otherwise the workaround will not work.)

     

    Cheers,
    Eva

    0
    Comment actions Permalink
  • Avatar
    Nils Bier

    Hi,

    I just wanted to let you know, that I've created a new knowledge base entry regarding Eva's workaround: http://www.k15t.com/pages/viewpage.action?pageId=79005148


    Cheers,
    Nils

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk