Dynamically-built Confluence page built based on parameters passed from other system?

Comments

5 comments

  • Avatar
    Roman Serazhiev

    Hi MD.

    Here is I understand the problem and what you could do about it.

    tasks — pages
    domain — variants
    versions — versions

    I would imagine a user opens up Confluence space, selects the required version and variant (domain) and see the page (task). The content for this task can be pulled from the main repository of content: this could be a different space or a different page tree in the same space. I would recommend using Conditional Content macros on task pages; inside Conditional Content macros you need to use Include+ macros that pull the required content depending on the chosen variant and version.

    To achieve the variant and version picker for readers (users who can't edit versioned pages), you need to use Scroll Viewport app. It will make the content from Confluence visible in an easy-to-read format with version and variant pickers.

    I would recommend trying out the apps on a staging environment to see if they can achieve what you want.

    Roman.

    1
    Comment actions Permalink
  • Avatar
    MD (Edited )

    Thanks so much for the suggestion, Roman. Seems like you get what we are trying to do and I appreciate the help!

    What I would really like is for my system to be able to push the needed version/task/domain to Confluence, and have  Confluence build the page dynamically based on those variables.

    Would there be a way to do this in a more automated way? If not we may need to fall back to manual steps but would like to avoid this if possible, just to reduce the risk of users choosing the wrong version or domain. 

    Thanks again!

    MD

    0
    Comment actions Permalink
  • Avatar
    Roman Serazhiev (Edited )

    Hi MD.

    Would there be a way to do this in a more automated way?
    There are apps that can help with automation (like ScriptRunner), but they are not compatible with Scroll Versions. If non of the available products fit your requirements, a custom app or script could be solution.

    How would the system know which combination of parameters to show to a user?
    How would a user be able to tell the system which combination they want to see?
    What if the combination needs to be changed by the user? Would the system allow user interaction?

    Roman.

    0
    Comment actions Permalink
  • Avatar
    MD

    Thanks Roman.

    The system would know the combinations of parameters to show to a user based on the domain and version related to the task they are working on (in our system). The user would not need to tell the system what they want to see -- the system already knows the task, domain, and version.

    From there, if the user wanted to navigate around to other pages, they could, but I want to show them the most relevant info for their context to start. The goal is to minimize the amount of clicking around the user has to do to find the documents relevant to what they are doing at that moment. 

    Thanks very much for the conversation -- it's helped me understand the capabilities of Scroll Versions and Scroll Viewport. 

    0
    Comment actions Permalink
  • Avatar
    Roman Serazhiev

    Hi MD.

    I would recommend to try out the apps to simulate the real world scenarios. You could try out any app from the Atlassian Marketplace for 30 days.

    If you have any questions or issues during the trial, please let me know.

    Roman.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk