Recommendations on embedding Kurve records in TRIRIGA Portals

  • Build each portal around one question, or a set of closely related ones

Pick records someone would look at in the same sitting to make the same decision. If it covers different topics, we'd suggest splitting it into separate sections.

  • Keep it to around ten records per portal section

Reports and graphs together. Every record joins the same queue to pull information from the system.

  • Narrow each Kurve record to the data relevant to the question it answers

Decide what a report or graph is there to tell you, then apply query filters to match. It loads faster and reads better, because what's left on screen is exactly the information you need.

  • Put the reports and graphs you check first at the top

The page loads top to bottom, so ordering by priority improves the overall experience.


*Portals and their sections are arranged in Portal Builder by your application administrator. 

If you are not the person who builds them, let your administrator know.


Why this happens


Kurve runs inside TRIRIGA. When you embed a record in a portal section, that record asks TRIRIGA for its data, and TRIRIGA returns it in batches. The more records it asks for, the more batches it waits through. Every Kurve record on the page is in that same line, served one after another from the top.


That explains what you might see:

  • Reports at the top are first in line, so the top of the page fills in first.
  • A very large report holds up other reports in the same portal section.
  • The more records on the page, the longer the queue.