| diagram |
 |
| namespace |
http://browse.api.de.n2.tibco.com |
| type |
extension of XmlModelEntityId |
| properties |
|
| children |
dynamic-id-attr qualifierSet |
| attributes |
| Name | Type | Use | Default | Fixed | Annotation | | model-version | xs:int | optional | -1 | | | documentation | Major version number of the organization model in which an organization model entity resides.
If not specified, the default value will be the latest version of the organization model.
(Version numbers must be compatible with, and conform to, the OSGi version number schema. For Directory Engine, only the major part of the version number is significant.) |
| | entity-type | OrganisationalEntityType | required | | | | documentation | | Enumerated value defining the type of the organization model entity. |
| | guid | xs:string | required | | | | documentation | Globally unique ID of the organization model entity.
(Although this value is unique across all entities, if the entity exists within more than one major version, it will share the same GUID.) |
| | qualifier | xs:string | optional | | | | documentation | Only applicable in certain circumstances, and only to organization model entities whose entity-type is PRIVILEGE or CAPABILITY. These entities can have an association with other entities - for example, a resource may hold many capabilities, or a position may have many privileges.
These associations can have a qualifying value, according to their nature, to differentiate them. For example, the PRIVILEGE to sign off a purchase order may be qualified with the maximum amount that can be signed off. |
|
|
| annotation |
| documentation | Request element for browseModelNode operation. This operation returns the details of the organization model entity identified by its entity-type, guid and organization model version. If no organization model version is specified (or -1) then the organization model with the greatest major version value is assumed.
Each root-node in the response will indicate whether it has any children. For example, an organization entity may have organization unit entities as its children. If so, the identifiers for those immediate children will be given in the "child" sub-elements. These identifiers can, in-turn, be passed back into the browseModelNode operation in order to drill-down further into the organization model structure.
For organization entities, this operation will identify those LDAP containers that administer them. That is those LDAP containesr whose resources are permitted to view that organization structure. If no LDAP containers are listed, then the organization can be accessed by all resources.
Where applicable, each node in the response will specify the "selection-mode" by which associated resources will be selected for work allocation.
This operation is used with the openOrgModel operation to provide a drill-down view of an organization model structure.
It is useful for large organization models, where retrieving the entire structure would be expensive. The recommended alternative is to use the listOrgModelOverview operation. |
|
| source |
<xs:element name="browseModelNode">
<xs:annotation>
<xs:documentation>Request element for browseModelNode operation. This operation returns the details of the organization model entity identified by its entity-type, guid and organization model version. If no organization model version is specified (or -1) then the organization model with the greatest major version value is assumed.
Each root-node in the response will indicate whether it has any children. For example, an organization entity may have organization unit entities as its children. If so, the identifiers for those immediate children will be given in the "child" sub-elements. These identifiers can, in-turn, be passed back into the browseModelNode operation in order to drill-down further into the organization model structure.
For organization entities, this operation will identify those LDAP containers that administer them. That is those LDAP containesr whose resources are permitted to view that organization structure. If no LDAP containers are listed, then the organization can be accessed by all resources.
Where applicable, each node in the response will specify the "selection-mode" by which associated resources will be selected for work allocation.
This operation is used with the openOrgModel operation to provide a drill-down view of an organization model structure.
It is useful for large organization models, where retrieving the entire structure would be expensive. The recommended alternative is to use the listOrgModelOverview operation.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:complexContent>
<xs:extension base="orgdto:XmlModelEntityId"/>
</xs:complexContent>
</xs:complexType>
</xs:element> |