A view is a way of structuring data in a sensible hierarchical structure. You need a view to be able to organise data correctly for your customer. It is important that you only include the information in the view that is necessary for your customer.
A view gives you a structure within which you can organise the mnemonics. You need to group the sites into customers and the customers into customer groups.
A view also gives you the ability to restrict what data the customer sees by using the view filter. The view filter can be applied by choosing any point in the tree hierarchy to limit the views that the customer can see to anything beneath that point.
The role of a view code
A view code is a unique reference to the customer. The view code must match the debtor code at the customer level in the tree. An example of a debtor code would be: debtor code sab001, or 101771.
Each site must also have a view code, and they must be unique, so you can’t simply re-use the debtor code. However, it is important that the view code resembles the debtor codes for the customer. You’ll need to prefix the debtor code onto the site. An example would be: 101771-Potchefstroom
What makes up a site within a view
Typically, a site is made up of a primary link, a backup link and a CE device. It is useful to group these together under a site for the customer instead of directly under the customer.
For example, the Santon site here.
If there is an IPSLA test that pertains to the site, that should also be under the site.
Iris Certified Engineer (ICE) Level 1, 2 and 3
We offer certification exams for all users and administrators. Tracks have been developed to cover the content for each of the levels. To register to be an ICE, please email email@example.com.