View Management (how do I create, edit, copy, move or delete a View or Subview?)

Views vs Subviews

View management and server configuration sets

Permissions

Specifying the content of a View

To create a View or Subview

View naming and View paths

To create multiple Views

To copy a View or move a View

To edit a View

To delete a View

RESTful API

Views vs Subviews:

A Subview is the child of a View. You can create a hierarchy with any number of Subviews. The level at which you create a View/Subview determines its hierarchy, e.g. if you navigate to My Network View > Subview 1 View, and then create a new View (Subview 2) at this point, it will then become a Subview of Subview 1.

A parent View inherits the contents of all its Subviews (though the contents of a Subviews will be visible only when you have accessed that Subview. If a user has access to a View that is a parent View to Subviews, that user will then have access to those Subviews. If a user has access to a View but not its parent View, that user will be able to see the View (through the Explorer, for example), but will not be able to access it.

View management and server configuration sets:

The Views tab under the View Management page is where you can specify, create and edit the Views that are to be included in server configuration sets. For further help and information on server configuration sets, please see this article.

To manage the Views for a specific configuration set, ensure that you are on the Views tab and then select the specific configuration set from the Server/Configuration Set dropdown box in the top left of the page:

The Views tab under the View Management page table displays the following details:

Permissions:

If not an administrator, access to the View Management page requires the Create View user permission. Please see this article for help and information on user permissions in Entuity.

Specifying the content of a View:

The content of a View is determined by two factors:

1. How the content is populated - a View can be populated in the following manner:

• Manually:
  • you can choose which objects to include in the View.
• Automatically, based on either:
  • a union of specified existing Views/Subviews, i.e. all objects within specified existing Views and Subviews.
  • an intersection of specified existing Views/Subviews, i.e. only the objects common to each of the specified existing Views and Subviews.

2. How the content is filtered - a View content filter is a defined set of rules that determines which of the network objects potentially available in a View are actually displayed. Filters allow the content of a View to change as the objects that meet its criteria change.

Note, in circumstances where hierarchy is important to the display of information, e.g. in the Explorer tree or the View Contents dashlet, any contents of the View that are sourced from a Subview will not be visible. (All content sourced from base Views will be visible.)

To create a View or Subview:

There are four places from which you can create a View, depending on whether Views are managed via server configuration sets (if all servers are managed via config sets, then View creation options will only be available via the View Management page):

• via View Management:
  Main Menu > Administration > View Management > Views tab > Create Top View or Create Subview
  
  
  
  
• via My Network (if the Views of one or more visible servers are not managed by configuration sets):
  My Network in the Explorer > right-click Context Menu > Create View
  
  
  
  
• via Contents dashboard (if the Views of one or more visible servers are not managed by configuration sets):
  My Network > Contents dashboard > Create View
  
  
  
  
• via View Contents dashlet (if the Views of one or more visible servers are not managed by configuration sets):
  Any dashboard containing the View Contents dashlet > Create View
  
  
  
  
  

The New View form will open on the right of the page.

The form's title will depend on the position of the View or Subview in the View hierarchy, e.g.:

Top level View:

Subview:

Complete the fields in the form:

View Settings

1. Enter a View Name. Please see the section below on View naming and View paths for further help and information on View naming conventions.

Contents

1. Specify how the View/Subview's contents are populated in the Contents field. There are three options available:
   
   
   
   
   • Manually Populated - choose which objects to include in the new View/Subview in the Contents Filters field below. To create a new content filter, click the Contents Filters field and then + Create Content Filter. The New Content Filter form will open, where you can specify your content filter rules.
     
     
     
     
     
     
     
     
   • Based on the Union of the Views - the contents of the new View/Subview will consist of all objects within the selected Views/Subviews specified in the Base Views field below. You can also apply contents filters to this selection in the Contents Filters field below.
     
     
     
     
     
     
   • Based on the Intersection of the Views - the contents of the new View/Subview will consist only of objects common to each of the selected Views/Subviews specified in the Base Views field below. You can also apply contents filters to this selection in the Contents Filters field below (please see this article for further help and information on setting View content filters).
     
     
     
     

Access Control

1. Specify the owner of the View/Subview in the Owner field, and determine the viewing and editing rights of user groups in the User Groups field below.
   • Clicking the User Groups field will open the User Groups form. This form lists all of the user groups, and under each user group you can set the viewing and editing rights. The first group is the Administrators group, which has the Edit right (this cannot be changed). User groups are only displayed in this list if they are available on the specified server or configuration set.
     
     
     
     
     
     
   • You can choose from one of the following permissions for all other non-Administrators user groups:
     
     
     
     
     • No Access - users in this user group will have no access to this View.
     • View - users in this user group can view this View, but they cannot edit it.
     • Edit - users in this user group can view and edit this View.
   • Once you have made your choices, click Done in the top right of the form to save your changes and return to the Edit View form, otherwise click Cancel.

Location

1. If the Geographical Map mode is enabled, specify the geographical location of your View in the Location field. Click this field to open the Location form, in which you can search for and select your location, or manually enter coordinates. Please see this section for further help and information on the Geographical Map functionality in Entuity.
   
   
   
   
   
   

Events & Incidents

1. Specify the event filters and incident filters you want to apply via the View/Subview in the Event Filters and Incident Filters fields, from where you can select or create new event filters and incident filters.
   
   

View naming and View paths:

View names:

Entuity permits most characters in View names, but excludes the following:

• / forward slashes, because these are used to delimit View paths.
• \ backslashes, to avoid confusion with file paths.
• :: double colon sequence, because it is a reserved character sequence. Entuity will allow a single colon.

View names are case sensitive, e.g. London Office and London office are considered as 2 separate Views.

Sorting Views:

Views are sorted on their name, sorting on case-insensitive, alpha-numeric comparisons. Entuity therefore ignores casing during sorting, and embedded integers are compared using their numeric value.

Copying Views:

When copying a View (see below), if a View with the same name already exists at the destination then Entuity will automatically append an integer enclosed in brackets to the View name. The integer is the next available integer, e.g. London Office(1).

View paths:

On each server, the View path must be unique.

For a View that is created against the server root, View name and View path are the same. For a View that is created as a Subview of another View, the View name does not have to be unique, but its View path must be unique.

The View path is built from the View name and any parent View. For example, London Office and Berlin Office are Views created against the Entuity server root. They both have a Subview called Switches - this is permitted because their View paths are unique:

Views in multi-server environments:

In multi-server environments, different servers may have Views with the same View path, e.g. every installation is supplied with the My Network (admin) View.  Also, when logged into multiple servers and operating in consolidation mode, if you create a View then each Entuity server to which you are logged in will create that View. Entuity recommends creating Views in consolidation mode when you want to use Views with the same name across more than one server:

• this ensures View names are exactly the same.
• this ensure View definitions are exactly the same, at least at the time of creation.

Use the View Hierarchy report to check for consistency across servers.

To create multiple Views:

To create multiple Views, it is recommended that you utilize Entuity's RESTful API functionality. Please see this article for further help and information on using the Entuity RESTful API functionality.

To copy a View or move a View:

1. Navigate to the View you would like to copy or move, either via the Explorer, the breadcrumbs, or from a Contents dashboard/View Contents or Map dashlet.
2. Right click the desired View and click Copy/Move to Another View.
   
   
   
   
3. The Target View menu will slide in on the right. This has an explorer through which you can find the View to which you want to copy or move the selected View as a Subview. Select the target View and click Done in the top right of the form.
   
   
   
   
4. A confirmation message will appear asking if you want to Copy or Move the currently selected View to the target View. Select as appropriate, otherwise click Cancel.
   
   

To edit a View:

1. Navigate to the View you would like to edit, via the Views tab of the View Management page, or if Views of all visible servers are not managed by configuration sets, the Explorer or the breadcrumbs.
2. Right click the desired View and click Edit View.
   
   
   
   
3. The Edit View form will open on the right of the browser, which has the same fields as when adding a new View (see above). Make the changes you would like and click Save in the top right.

To delete a View:

Note, when you delete a View, you are only deleting the View and not the managed objects within it.

1. Navigate to the View you would like to delete. Right-click and click Delete View.
   
   
   
   
2. A deletion confirmation window will appear. Click Delete.
   
   

RESTful API:

Please see the following for help and information on managing Views via Entuity RESTful API:

• List available Views or create a new View.
• Inspect, update or delete a View.
• Inspect, add or delete View objects.
• Config sets - list the Views in a config set, and add Views to a config set.
• Config sets - update, rename or delete Views in a config set.