Applies to: Design considerations for Domain View-creation

Follow the view design best practice recommendations below to enhance system performance and user experience.

Impact

Areas to focus on

Benefits

Number of columns in a view.

Number of filters in a view.

Number of assets in a view.

Multi-path hierarchies.

Views that span content across communities.

Reduced latency.

Reduced resource utilization.

Improved page refresh time.

Improved user experience.

Best practice recommendations

Views are useful for hiding complexity and joining together assets from multiple communities and domains for a better user experience.

Avoid multi-path hierarchies and more than 50 columns, fields or characteristics when creating views to ensure optimal performance. Use the display name of the driving asset as the first characteristic or column when you enable the hierarchy. If you want to display the characteristics of the related assets, use a hierarchical representation for a better user experience. For more information, go to our Documentation Center.
Use single-path hierarchies for grouping rather than multiple filters or multi-path hierarchies. Avoid using more than 5 filters per view when you are working with hierarchies.
Use a global view instead of a domain view when assets span multiple communities.
The maximum number of recommended assets in a view is 250,000 in order to maintain performance. Create a default view for everyone that maps to your scope assignment with a minimum cardinality of 1, keep in mind that 0 will not display. This ensures that the default view includes all the fields commonly needed by users across all roles.

Operating Model → Execution and Monitoring Concepts → Views

Run the Operating Model Reverse Engineering, or OMRE, on a regular basis to keep an overview of your operating model.