From RPM Wiki
| Table of contents |
Summary
This page allows users to create custom views. It is also used for view management such as deleting.
- Start with the Views functional spec
Details
View name
Custom views can be given a name when saving. Custom view names must be unique among other views of the same category and share status (private/shared). Therefore it is possible for the user to have two custom views of the same name if they, for example, save a private view with the same name as a shared view.
Private, Shared
The private/shared status of a custom view is set when the view is created or renamed. All staff can save and delete private views. Saving (including overwriting) and deleting shared views is a privilege. All staff can use (including loading to create a different view from) shared views.
Add and copy
From this page a user can start a new view or start a copy. In either case the name edit page is brought up so the user can name the new view. If it is new the name is blank, and if it is a copy
Auto copy
When a user edits a view they cannot save, a new view is created instead with " copy" appended to the end of the original view name.
- This includes editing built-in views. It also includes shared views if the user doesn't have the "Save shared views" privilege.
- The one exception is temporary views where the temporary view name is simply used, without the brackets. There is no need to add " copy" since the temporary view doesn't exist as a saved view.
- See Naming a copy (spec)
Saving
The view as shown is saved by clicking "Save" or "OK". The only difference is "OK" returns to the grid (with the view being edited selected) while "Save" stays on the edit page.
- Auto save. Actions that would load a different view for editing will prompt the user to save the current view if they like. This is only done if a change had been made to the view since saving.
- Name uniqueness is checked again at saving in case another user or session has since taken the name the user chose for this view. If the name has since been taken a "Name already exists" error is shown.
Deleting
Custom views can be deleted. This puts the view in the recycle bin where it can be restored (as long as its name is still unique, see above)
- Private views are only seen in the bin by the owner of the view
- Shared views can only be deleted or restored by users with the "Save shared views" privilege. All staff users with that privilege see any shared view in the recycle bin.
- Individual filters and columns are removed, not deleted (they don't go to the bin).
- When a view is deleted, the next view in the list the user is allowed to edit is shown in the edit page. If the end of the list is reached start working backwards. The list starts with shared views in alphabetical order than private views in alphabetical order. If there are no remaining views the user can edit, the user is returned to the grid with the "All" built-in view selected.
- Example: A user without the "Save shared views" privilege would be returned to the grid after deleting the last private view.
Limits
- Maximum custom views per category per user (Settings XML file)
- Shared views count toward the limit
- Built-in and temporary view do not
- Default is 500
- If the limit is exceeded the "Add" and "Copy" links will go to the generic limit error page.
Security
Staff users
- Any staff user can modify a shared view and even save it as a private view
- The "Save shared views" privilege is required to save, delete, and restore shared views.
History
- This page was last modified 19:50, 21 Dec 2009.
- This page has been accessed 1327 times.