Monday, February 4, 2008

ACCESS CONTROL(9 to 13)

9. What is ‘All’ access control?
‘All’ access control provides access to all records that have a valid owner, as defined in any of the business components view modes. ‘All’ visibility essentially provides a view of data access all organizations. There are no business component view modes specific to ‘All’ access control. ‘All’ access control is set at the view level


10. What is access group access control?
This is meant to control access by groups of diverse party types to categorized master data. An access group is a collection of any combination of positions, organizations, divisions, accounts, households and user lists. Its members cannot be individual people.


A user is associated with an access group if during the current session, the user is associated with a position, organization, division, account, households and user list that is a member of the access group.

You can create hierarchies of access groups. An access group can belong to only one access group hierarchy. You can grant access groups, access to catalogs and categories of master data.

You can only control access to catalogs and categories of master data. You cannot control access to individual master data, using access group access control.

When access groups are associated with a catalog or with categories, in a catalog, you can apply access group access control. Control can be done in the following ways,

Group – While in a given category, the user sees either a list of categories sub-categories, to which the user has access, or, all the data records in the current category, depending on the applet being used.
Catalog – The user sees a flat list, of all the data, in categories, across all catalogs to which the user has access.


11. What components determine, the data within a view to which a user has access?

The following components determine what data a user sees, within a view:

Business component view mode – A view can have several applets – lists, forms, or trees. Each applet is based on a business component. The business components view mode determines the allowable properties, on which access control can be based for the business component.
Applet visibility properties – A view can specify one of it’s applets as the visibility applet. The visibility applet connects the business component to the view. The visibility applet specifies which business component to use, and the display names for the business components fields.
View visibility properties – A view’s visibility properties determines the access control mechanism that is applied to the business component, on which the view is based. The business component may have personal or position based access control available. The view specifies which of these to use.

The application and a users’ responsibility, restrict the views presented to the user. Within a view, view visibility properties determine the applet that drives the visibility in the view, and, specifies the access control mechanism to apply to the business component.

The views visibility applet specifies the business component being used in the view. The business component specifies how a user can be associated with data to provide access.


12. What is local access?
Each view has a ‘Local access’ flag. If set to True, all users with the view, in their responsibility, can access the view from, either the local or server database. When set to false, users can access the view when they are connected to the server database.

The ‘Local access’ column is primarily a mechanism for controlling, which views mobile users can work in offline mode.


13. How do you override the visibility property set in the ‘business component popup visibility type’ property?
The developer can override the visibility property set in the business component popup visibility type by,
--Setting the visibility of picklist object.
--Use the visibility ‘Auto all’ property.
--Use the special Frame class and user property.

No comments:

Siebel Basics and FAQs