The alternate view feature lets you create alternate views from existing Horizon views. The purpose of alternate views is to let you customize views to fit the needs of certain users in your library. (For example, you may want to restrict part time circulation clerks from changing borrowers’ btypes. In this case, you can create an alternate “borrower” view with the btype column set to be uneditable.)
You can alter views to display alternate window titles and field names, make column data editable or display-only, omit or change the order of certain columns in the view, and so forth.
In addition, you can create alternate views that restrict the records that display in a list window. (For example, you can specify that only “Student” btype records display in the List Borrower Circulation Types window for the alternate “btype” view. This type of alternate view requires you to create a new SQL view.)
After you create alternate views, you need to assign the alternate views to view sets and assign the view sets to users.
This section explains these topics:
• | Creating Alternate Views |
• | Assigning Alternate Views to View Sets |
• | Assigning a View Set to a User |
• | Creating a SQL View for an Alternate View |
• | Giving a User View-only Access to an mq_view |
• | Troubleshooting Alternate Views |
In order to create alternate views in Horizon, you must have a thorough knowledge of views.
© 1998-2017 Sirsi Corporation