Views provide a variety of ways to navigate, explore, and analyze the information collected in the repository. Views vary in content, in scope, and in layout to display the type of information you need to the relevant people.

Access Views

Based on user access and visibility setup on the views, you will find existing Views through the Explore section of the main Menu:

Select the Views menu to see all repository Views.

Public Views: Views that are visible to everyone with access to the Model content.
My Views: personal Views that are only visible to its owner.
Favorite Views: access your most used or preferred Views. You can add a View to your favorites by clicking "Add to favorites" in the Actions column.

My Views, Public Views, and Favorite Views are accessible in the Recent Views area on the OrbusInfinity Web Application.

Access Views.png — Figure 1. Access Views

You can also open a View from an OrbusInfinity Dashboard, either shared with you or newly created for your own usage. Learn more about OrbusInfinity Dashboards here.

Filter Views

To easily find the View you need, you can filter Views by its Type or a tag. Only saved Views contain tags.

To filter Views:

On the Public, Personal or Favorite Views page, find the Tag column
Click on the filter icon displayed near header.
To search for a specific tag, use the Search.
Use the checkboxes to select one of multiple tags to use to filter the list.

Public Views - Tags.png — Figure 2. Filter Views by tag

Click Apply. Only Views with the selected tag are displayed.

Open a View

To open a View, click on its hyperlinked name.

Attribute Permissions in Views

When you open a view with an attribute filter for a hidden attribute, no content will be displayed. For example, if you try to view a list of applications where the total cost exceeds 10,000, you will not see any results if you do not have permission to access the total cost information.

For more information, see Manage content permissions.

Add a View to Favourites

To save a View as a favorite:

From the Views main menu, go to the Public or Personal tab where the View is listed.
Select a View from the list.
Click on the favorite icon in the Actions column.

Types of Views

You will find existing Views in your environment. Those are setup out-of-the-box to support most common use cases and illustrate use of different types of Views.

Type	Description and Example
List	Displays Model Items as a list and their Attributes as columns. Used to display Model Items and their characteristics in an Excel-like table providing foundational functionalities like filtering, sorting and conditional formatting. The dataset can be then displayed as a selection of Visualizations. Typical examples: Application Inventory, Data Glossary (displayed as List), Business Process Decomposition (displayed as Visualization).
Matrix	Displays how selected Model Items relate to each other, showing one Object Type as rows and another as columns of a grid. The intersection cell displays relevant Relationship information existing between the 2 Objects. Used to visualize and/ or edit Relationships between different Objects in a structured format. Typical examples: Capability to Application matrix, Application to Technology matrix.
Traceability	Displays Objects and how they related to other Objects across the repository through different levels and types of Relationships. Used to navigate and analyse dependencies between Objects across domains and models. Typical examples: Project Context, Organizations impacted by Technology changes.
Landscape	Box-in-box representation of 2 Object Types and their Relationships. Decomposition is displayed if it exists. Used to visualize mapping of Objects to their Reference Model, analyze architecture landscapes and communicate status of Objects in their wider context. Typical examples: Business Capability Map, Technology Reference Model.

Interact with a View

Views generally provide interactive capabilities to explore enterprise data and drill down into detail of selected Model Item where relevant. In this section, you will find the most used View functionalities when exploring enterprise data.

New List View Toggle

A modernized List experience is available and can be toggled done as desired. It presents information through a clear, consistent table experience for managing repository data, with easy control over what you see via direct options and drag-and-drop column order.

A smart toolbar adapts to your context—showing view actions when nothing is selected, and item/bulk actions with a selected-item count when you select rows.

View Search

The View Search enables to find Objects referencing a known term in all data displayed on the List View. The Content of the List View is filtered to help locate Objects making reference to the searched term.

The content of the List can also be filtered using the filter on column headers.

search view using header filter.png — Use Filters on column headers

Use the global search to find Objects containing specific terms across the repository. Also use your browser search functionality to locate Objects in displayed Landscape, Matrix, and Traceability View.

Open Model Item

The Object Details Flyout gives quick access to more detailed information on a selected Model Item, allowing users to understand its characteristics without leaving their current context.

Use the Object Details flyout to:

Understand more about an Object or a Relationship, accessing its detailed information.
Navigate Object's context and related Items using the Impact Explorer.
Perform advanced management actions on the Object to reuse, copy, or move it to another Model.
Get direct information on where an Object is used in graphical models and diagrams.
View the Model Item's history of change in the repository

Object Details from search.png — Figure 5. Object Details Flyout

You can Open a Model Item systematically by clicking on the Object or Relationship hyperlinked Name. The Object Details Flyout will open. For more information on Object Details Flyout, learn to Interact with Object Details Flyout.

Conditional Formatting

Conditional formatting is used to colour-code an Object or its attributes value on the View Content. It is usually based on values of calculated attributes, score results, or attribute selections , associated with a specific colour to draw attention to certain Objects where acceptable thresholds have been bypassed.

Using conditional formatting on Views will:

Reduce time to identify areas or Objects of concerns: colours, when chosen wisely, can surface Objects with specific values as warnings or potential issues. For example: Applications with high risk of IT Obsolescence would be coloured in red.
Improve communication, highlighting information of importance or interest to stakeholders and other users. For example: Technology Standard Class can be colour-coded to indicate to Business Users that a Technology is not an official standard, and will raise an exception if used in business projects.
Increase efficiency in managing inventories, as change in rendering makes Objects to look after stand-out.

In Lists, tailor columns for Attribute values to be displayed with user-selected icons, text, or background colouring.

List view conditional formatting.png — Figure 7. List View conditional formatting

Applying your own conditional formatting on a Public List View will add an asterisk near the View name: it indicates the View must be saved to your personal Views to be retained for future use.

From the Details tab, click on the Save As icon.
The View is then saved in your personal Views and accessible from the My Views Menu on the left-hand side.

OrbusInfinity Views Save.png — Figure 8. Save as one of My Views

Conditional formatting is not applied to hidden attributes. This prevents users without permissions from inferring an attribute value based on the conditional formatting values. For more information, see Manage content permissions.

Learn more about other functionalities provided to configure Lists and manage its content.

Filter Content on a View

Views like Landscape View proposes an interactive filter from the top bar of controls.

It filters the content of the Landscape View based on a related Item or one or many selected attribute conditions.

Landscape Filter.png — Figure 9. Filter content on a View

List, Traceability, and Matrix Views have elaborated ways to define the dataset and define filter conditions to apply to the View Content. Find the Filter tab on opening the View.

Filter sets define the context where the filters are applied. This is where you can refine the type of metamodel item to display, the Model(s) in scope, and define the filter conditions.
Filter conditions define criteria through which the repository content is returned in the View.

Use Views - Filter.png — Figure 10. Configure filters

Filtering for objects where an attribute has no value

The available options depend on which List View experience you are using.

New List View: Column header filters include =∅ (is empty) and \neq∅ (is not empty) operators, allowing you to directly filter for objects where a specific attribute has not been populated. To enable the New List View, use the toggle at the top of the view.
Legacy List View: This operator is not available. As a workaround, switch to the New List View or export the view content to Excel and filter for blank cells in the relevant attribute column. See Download View Content above.

To learn more about the Filter, navigate to Configure filters and filter sets.

Save as your Personal View

A set of Public Views is available in the repository showcasing the most common datasets and their visualizations. Organizations may also define their own: users can open and navigate those pre-set Views to explore enterprise information.

A List, Traceability, or Matrix View available in Public Views may be saved to your personal Views section to apply the style and format you work with the best:

Select and open a View.
- Use Columns Options or Conditional Formatting to edit the layout or format used to display information. You will see thered asterisk (Legacy List, Traceability, and Matrix View) or the tag (New List View) appear next to the View name.
- From the Details tab, use the Save As icon (Legacy List, Traceability, and Matrix View), or select Save View as (New List View) to save the View in your personal Views section.
- Landscape Views are quick to create and save from the OrbusInfinity Home Page.

For Traceability View, you can also create a new personal View based on the existing Traceability View.

Figure 11. Create new Traceability View from the existing Traceability View

Make sure the Models currently active contain your data.

In the creation wizard:

Select for the new View to be Based-on View.
In the View list, select the View you want to copy.
Click on Start the View to create the View based on the selected one.

You can also add List View on a Personal Dashboard for quicker access.

Download View Content

To download View content, your User Role needs to have the Access To Export Or Download Data feature permission enabled.

You can export View content in Excel or XML format. The exported files can be used to update data then import those updated as Model content into OrbusInfinity. For more information, see Get started with Data Import.

You can download only saved Views.

To download View content:

Open a View from Views or from a Dashboard Widget.
On the toolbar, select Download View Content (Legacy List, Traceability, and Landscape Views),
If the New List View toggle is on, use the New List View experience to download content.

Use Views - Download.png — Figure 12. Download View content

The download process starts.

Upon completion, the file is saved to your computer in your downloads.

The downloaded file contains the content of the View as displayed in the View.

Figure 13. Downloaded View as an Excel Workbook

Exports may contain fewer columns than the View shown in the application. This is expected behavior, not a defect. When exporting a View via Excel Workbook, XML, or OData Live Link, non-attribute columns (for example, Approval Status, Is Pending Review) and system attributes are automatically excluded from the exported output.

To explore information from a View further, see Explore the context of an Object.