Whoops…Nothing found

Try other keywords in your search


 1 Minute



Pages are the objects that govern the appearance of the frontend in the Virtualitics AI Platform.

  • A Page object can be thought of as a web page canvas at any given point in a Flow.
  • While frontend and backend tasks are performed in Steps, Pages must be invoked to display and/or update the content on pages in the Virtualitics AI Platform.
  • A Step must be associated with a Page object on which that Step will run.


A hierarchical structure has been built into Pages to allow developers fine-grained control over content layout on pages:

  • Pages: Parent object containing everything a user might see in the Virtualitics AI Platform at the conclusion of a Step.
  • Sections:
    • Pages must have at least one Section.
    • Sections operate as dividers between Cards and Elements and can be used to display groups of Elements with titles (headings) and descriptions. 
  • Cards:
    • A Section will likely consist of one or more Cards.
    • A Card object contains all Elements to be displayed on a given baseball card style UI element. 
  • Elements (Page Elements):
    • Elements must exist in Cards.
    • Please refer to the “Page Elements” section for an overview of the Elements supported in the Virtualitics AI Platform.


A combination of Sections, Cards, and Elements can be used to customize Pages, providing end users with a streamlined data input/processing process and consumable tables and plots. For an example of the page hierarchy, please refer to the images shown below. 

In this example, we display screenshots from with a Page with:

  • A Page title (“Merging Data & Engineering Features”)
    • One Section (no title; contains two Cards)
    • Two Cards
      • Card #1: “Visualizing Training Data Gearbox Lifetime”
        • This Card contains a single Dashboard Element
          • Within the dashboard, we have three bar plots.
          • Each bar chart is a Plot Element.
          • The Dashboard contains two Rows:
            • Row #1: Single Bar Plot (“Overview of Component Lifetime in Training Data”)
            • Row #2: Two Bar Plot; each bar chart takes up the same width within the row 
      • Card #2: “Visualizing Training Data Gearbox Failures”
        • This Card also contains a single Dashboard Element.
        • Again, we have three (bar) Plot Elements arranged in two Rows.


Why are Pages useful? When would I use Pages?

Pages are like Flows and Steps in that they are ubiquitous within the Virtualitics AI Platform. Any Flow you write needs at least one Page. Situations where a developer would create a Page in a Flow include when:

  • A user must upload a dataset from their local device.
  • A user must specify query parameters before connecting to and querying a database in a Step.
  • A user wants to display tables and charts to visually inspect ingested data before modeling.
  • A user wants to display tables, charts, and metrics to evaluate the performance of a ML model.
  • A developer wants to allow users to interrogate a ML model using embedded explainable AI tools.


How do I use Pages in the Virtualitics AI Platform?

The use of Pages in Flows is covered in the following knowledge base articles regarding our sample Flows:

Was this article helpful?