Archived - How do I create, edit, copy, move or delete a View or Subview?

This article has been superseded by Entuity v21.0. Please see this article for the latest information on this topic.

Views vs Subviews

View content

To create a View/Subview via My Network

To create a View/Subview via the Contents dashboard

To create a View/Subview via the View Contents dashlet

To create multiple Views

To edit a View

To copy a View or move a View

To delete a View

View naming and View paths

There are three ways in which you can create a View/Subview in Entuity:

• Via My Network.
• Via the Contents dashboard.
• Via the View Contents dashlet.

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 content:

You can set the content of a View by defining the following:

1. View scope (see step 4 below).
   • You can define a View's content scope in one of two ways:
     • manually.
     • automatic, based on none, one or more Views. If no Views are used, then the new View will be empty.
   • When editing a View, you can change it from manual to automatic based on other Views, and vice versa. However, Entuity will not combine the two states, e.g. if you have manually added devices to a View and then change it to automatic based on other Views, then Entuity will remove all the devices that were previously manually added from the View. Note, you cannot use a My Network View as the base for another View.
2. View filters (see step 4 below).
   • 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.

To create a View/Subview via My Network:

1. Right click My Network in the Explorer or the breadcrumbs, and click Create View.
   
   
   
   
2. The New View form will slide in on the right of the browser.
   
   
   
   
3. Enter a name for your new View in the View Name field. Please see the section below on View naming and View paths for further help and information on View naming conventions.
   
   
   
   
4. 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).
     
     Selecting your new custom View's contents from Base Views allows you to automate the creation process, thereby saving time.
5. 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). From ENA v18.0 P03 upwards, user groups are only displayed in this list if they are available on the servers specified in the Applicable Servers field above.
     
     
     
     
   • You can choose from one of the following rights for all other 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.
6. If you are using ENA v18.0 and above, 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. Please see this section for further help and information on the Geographical Map functionality in Entuity.
   
   
   
   
   
   
7. Specify the event filters and incident filters you want to apply to the View/Subview in the Event Filters and Incident Filters fields.
   
   
   
   
8. Click Create in the top right of the form, otherwise click Cancel.

To create a View/Subview via the Contents dashboard:

1. Click My Network in the breadcrumbs.
2. Click the Contents dashboard icon. This opens the Contents dashboard.
3. Click Create View in the top right of the browser.
   
   
   
   
4. The New View form will slide in on the right of the browser, with the same field as described above. Complete this form and click Create in the top right, otherwise click Cancel.

To create a View/Subview via the View Contents dashlet:

1. Navigate to a custom dashboard that has the View Contents dashlet.
2. Click Create View at the top of the dashlet or via the Overflow Menu.
   
   
   
   
3. The New View form will slide in on the right of the browser, with the same fields as described above. Complete this form and click Create in the top right, otherwise click Cancel.
   
   

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 edit a View:

1. Navigate to the View you would like to edit either via the Explorer or the breadcrumbs.
2. Right click the desired View and click Edit View.
   
   
   
   
3. The Edit View form will slide in on the right of the browser, which has the same fields as described above. Make the changes you would like and click Save in the top right.
   
   

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 on a Map dashlet.
2. Right click the desired View and click Copy/Move to Another View.
3. A 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 delete a View:

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 either via the Explorer or the breadcrumbs.
2. Right click the desired View and click Delete View.
   
   
   
   
3. A deletion confirmation window will appear. Click Delete.
   
   

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, 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.