When managing
user accounts, you can configure the view
mode values specified in the custom XML files according to your requirements.
The following table gives
the default values of view modes for
different business components.
Table 1. Default values of view
modes for different business components| XML file name |
Business component |
Default
value of view mode |
|---|
| UserList.xml |
User |
5 |
| Employee.xml |
Employee |
5 |
| AvailStatusTypes.xml |
List Of Values |
9 |
| NotificationTypes.xml |
List Of Values |
9 |
| Organization.xml |
Organization |
9 |
| PersonalTitle.xml |
List
Of Values |
9 |
| Positions.xml |
Position |
9 |
| Responsibility.xml |
Responsibility |
9 |
| TimeZone.xml |
Time Zone |
9 |
Note: The adapter ignores the view mode
values in the following
XML files, which have the searchSpecificationAttribute or the searchSpecificationValue
specified for a business component:
- PersonalTitle.xml
- NotificationTypes.xml
- AvailStatusTypes.xml
However, the
viewMode attribute is a required
attribute in the definition of a business component, and cannot be
deleted.
The following table gives the default values
of view modes for
the Multi-Value Group (MVG) business component. It also provides the
default values for the PickList business component attributes in the
UserList.xml file.
For information about identifying types
of attributes, see
Identifying
types of business component attributes.
Table 2. Default
values of view modes for MVG business components and
PickList business components in the UserList.xml file| Type of attribute |
Name of support data attribute |
Default value of view mode |
|---|
| PicklistBusComponent |
Time Zone |
9 |
| PicklistBusComponent |
Personal Title |
9 |
| PicklistBusComponent |
Availability Status |
9 |
| PicklistBusComponent |
Standard Notification |
9 |
| PicklistBusComponent |
Emergency Notification |
9 |
| MVGBusComponent |
Employee Organization |
9 |
| MVGBusComponent |
Responsibility |
9 |
| MVGBusComponent |
Position |
9 |
The following table lists the numeric
values that you can specify
in the definition of a business component for a view mode, and their
meaning.
Table 3. View mode specification in the custom XML
files| View
mode value |
View name |
Meaning |
|---|
| 0 |
SalesRepView |
Users can access records owned by them or can
access records whose team contains their position. |
| 1 |
ManagerView |
Users can access records associated with their
own position and positions that report directly to them. |
| 2 |
PersonalView |
Users can access records with which their person
records are associated. |
| 3 |
AllView |
Users
can access all records, except those records
with a missing or an invalid owner. |
| 5 |
OrganizationView |
Users can access records that are associated
with a single organization or with multiple organizations to which
their position is linked. |
| 6 |
ContactView |
Users
can access records that are associated
with a single organization to which their position is linked. |
| 7 |
GroupView |
Users can access categories of master data that
are associated with any of the access groups with which they are associated.
Users are associated with an access group if during the current session,
they are associated with a position, organization, account, household,
or a user list that is a member of the access group. |
| 8 |
CatalogView |
Users can access a flat (uncategorized) list
of data in all of the categories across catalogs to which all of the
user’s access groups have access. Users are associated with an access
group if during the current session, they are associated with a position,
organization, account, household, or a user list that is a member
of the access group. |
| 9 |
SubOrganizationView |
Users can access records associated with their
active organization or a descendant organization. |