View Mode specification in XML file
The adapter supports various ready-to- use attributes for view mode.
This table shows the XML
files for the ready-to-use attributes
that the adapter supports.
| Used for | Business object: business component | XML file name | Default view mode of business component | Default view modes of MVBBusComoponets and PicklistBusComponents |
|---|---|---|---|---|
| User management | User List: User | UserList.xml | 5 |
|
| User management | Employee: Employee | Employee.xml | 5 |
|
| Support data - Availability | List Of Values: List Of Values | AvailStatusTypes.xml | 9 (not used) | Not applicable |
| Support data - Standard/Emergency Notification | List Of Values: List Of Values | NotificationTypes.xml | 9 (not used) | Not applicable |
| Support data - Organization | Organizations: Organization | Organization.xml | 9 | Not applicable |
| Support data - Personal title (Mr./Mrs.) | List Of Values: List Of Values | PersonalTitle.xml | 9 (not used) | Not applicable |
| Support data - Position | Employee: Position | Positions.xml | 9 | Not applicable |
| Support data - Responsibility | Employee: Responsibility | Responsibility.xml | 9 | Not applicable |
| Support data - Time Zone | Time Zone: Time Zone | TimeZone.xml | 9 | Not applicable |
This table lists the integer
values allowed in the definition of
the business component for viewMode and their meaning:
| 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 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. |
You can edit the XML file and set the required view mode accordingly. The viewMode is redundant in those XML files that have searchSpecificationAttribute or searchSpecificationValue specified for the business component. These XML files are PersonalTitle.xml, NotificationTypes.xml, and AvailStatusTypes.xml. But viewMode cannot be removed due to redundancy, because it is a required attribute in the definition of BusinessComponent.
The following sample of the Responsibility.xml file specifies view
mode as 9, SubOrganizationView for business component Responsibility:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE BusinessObject SYSTEM "Validator.dtd">
<BusinessObject name="Employee">
<BusinessComponent name = "Responsibility" viewMode = "9">
<Attribute name = "Name" isUnique = "true" isRequired = "true"> </Attribute>
<Attribute name = "Primary Organization Id"> </Attribute>
<Attribute name = "Description"> </Attribute>
</BusinessComponent>
</BusinessObject>