Skip to content

DataSplice Support Website

Sections
Personal tools
You are here: Home » Product Manuals DataSplice 2.3 » DataSplice 2.3 Admin Client Manual » Views - View Permissions

Views - View Permissions

Expanding the Views section reveals the View Permissions View Permissions listing. Clicking this button brings up the View Permissions screen. This screen allows you to see and alter access to particular users, groups, and views. The screen looks like this:

View Permissions

Group membership generally determines access to, and permissions for, views. Permissions may also be set for individuals, with access rights that differ from the rest of the group.

Default permissions are set in the Views section under the Connection tab. These permissions (and therefore access to the view) can be extended to the user, or they may be modified on a per-user or per-group basis. Once you click on a user or group, the Add Access button Add Access will become active. You can use this button, or simply place a check in the checkbox next to the user's name, to provide extended access to that user or group.

Note: When view permissions are altered for a specific user, those permissions take precedence over the standard view permissions. For example, if you grant Update permissions to a specific user and then grant Insert permissions to the standard view permissions for that view, when that user logs in he/she will have Update permissions but not Insert permissions. Any changes to the standard permissions for that view will not be reflected in the user's permissions. To reset a user's permissions for a particular view so they match this new standard view permission, you must remove the permissions for that user and then reassign them. You can do this by unchecking the box next to their name, then rechecking it. The user's permissions will now be reset to whatever is now the standard view permissions for that view.

To grant permissions by view:

  1. Expand the Views section in the left pane.
  2. Select the View Permissions section.
  3. Choose the Select by: View radio button.
  4. Select the view of interest from the dropdown list.
  5. Check or uncheck each User Name or Group Name to indicate whether they should have permission or not.
  6. Click the Update button Update Button in the toolbar.

Test View 1

To grant permissions by user or group:

  1. Expand the Views section in the left pane.
  2. Select the View Permissions section.
  3. Choose the Select by: User/Group radio button.
  4. Select the User or Group of interest from the dropdown list.
  5. Check or uncheck each view to indicate whether permission is allowed.
  6. Click the Update button Update Button in the toolbar.

Test View 2

Overriding Defaults

Permissions can be overridden by highlighting a view or user with permissions to that view, then changing the configuration of the view as necessary. The only items that may not be changed are the SQL statement and the type of list. Items that appear in the list may be overridden.

The following are some examples of permission overrides. This is not an exhaustive list, but rather some illustrative examples.

Overriding Access Permissions

A supervisor may need to change a description of a work order, and this access may not be desired for a worker. In this case, the default permissions may be set to make the description field a Readonly in the Field tab. Then, the administrator can open the view in the View Permissions section and open the view for the Supervisor group and deselect the Readonly checkbox in the Fields tab, then set the default permissions on the Connection tab to allow updates.

Overriding Visible Fields

Some fields may not be necessary for a particular group of workers. Someone stocking the inventory need not see the price of each item, as this may clutter the view with too many fields. A salesman using the same view will need the price field. The field can be enabled for the Salesmen group, and marked as invisible for the Stock group.

Overriding List Items

Although list types are set by the initial configuration of the view, the items in the list may be changed to suit a user or group. A group based in one warehouse may not need to use the inventory in another warehouse, therefore their list of item descriptions can be limited to just their warehouse.

Edit List Validation To override a list type value list for a field:

  1. Select the list entry in the Field Validation dropdown box.
  2. Click the Edit button.
  3. The Edit List Validation dialog box will open (as seen at left).
  4. In the Edit List Validation dialog, add entries to the list by typing the values into the Text Entry box in the upper left corner and clicking the Add button.
  5. Click the OK button when finished adding entries to the list.
  6. The list entries will appear to the user in the same order in which they are added.
  7. Select the Restrict Entry to List checkbox to prevent the user from typing data into the field and forcing them to select a value from the list provided.

The static list can display additional information to the right of the list of values. To create a two column list, separate the value from the additional information with the pipe character:

Example:

"1 | 1st Value"

Overriding Filters

The data which appears as part of the view may be changed per user or group by adding or altering the filters which appear in the Filters tab. This may be used to limit the inventory that appears to only that which is in a particular storeroom, or may limit work orders to those assigned to a particular supervisor.

Overriding Display Name

Display names may be altered for a specific user or group by editing the Display Name field in the Fields tab. The staff that places orders may refer to an item by a UPS number, while the staff that pulls the inventory may refer to an Item number. This is the same number in both cases, but it has a different name for each application. The Display Name can be changed in this case to avoid confusion.

 

Created by root
Last modified 2005-03-03 02:52 PM
 

Powered by Plone

This site conforms to the following standards: