Rovo data retrival

[Ahmed Boghdady]

i have 5 pages on confluence as my KB
each page is 200-300 pages long,
Rovo fails to get the proper information when asked, It only works when i split those docs to a one or two pages

[Evgenii · Accepted solution]

Hi, @Ahmed Boghdady 

Rovo works with Confluence knowledge bases but has limitations with very large documents. With pages that are 200-300 pages long, Rovo may struggle to retrieve accurate information because it processes content in chunks. To improve results, break your knowledge base into smaller, more focused pages with clear headings and structure. Consider creating summary pages that link to detailed content, or reorganize your KB so each page covers a specific topic rather than being overly long. You can also narrow Rovo's knowledge scope to specific spaces or branches to help it focus on the most relevant content.

You can see this manual, for more details on configuring Rovo knowledge sources: https://support.atlassian.com/rovo/docs/knowledge-sources-for-agents/

[Ahmed Boghdady]

Thanks A lot!!

[Barbara Szczesniak]

@Ahmed Boghdady A suggestion to implement this.

Recently, I went through an exercise to break up some of my longer pages into smaller ones. To help me with this, I used Rovo Chat with the prompt:

To make this content easier for readers, how would you break the <link to> Managing Patients page up into separate pages, to form a section on managing patients? Group related content together on a page with links between the pages where necessary

In your case, you might want to specify that you want multiple levels of child pages or something.

Rovo came back with:

Then, for each of the child pages, it provided:

• New page title
• Main content to move here (with helpful hints)
• Cross-links from this page

Below that there was a section titled How the Navigation Could Look in Confluence. At the end, Rovo included:

If you’d like, I can take one of these (for example, “Quick Patient Intake and Pending Patients”) and draft the actual page outline/headings in Confluence-ready markdown for you to paste in.

I'm not sure why it would be in Confluence-ready markdown for me to paste in, rather than just a Confluence page I could add to my tree, but the page was not that long, so I manually made all the pages.

I wonder if you could somehow feed this into a Create with Rovo request to have it make all the pages or make an Rovo Agent to make it repeatable, since you will want to do it with both your pages or in case you get it to make 1 child level and then you want to iterate the process across some of those child pages.