Organization Model Entity Properties

Organization model entities are assigned attributes via the model schema from which they take their "type". This model schema association is optional; but, when included, the associated schema element of an organization model entity may define attributes that the organization model entity may carry. The attribute elements in a request describe the attribute definition (its GUID, name, label, and data type), and the value(s) assigned to that attribute.

Calendars can be assigned to groups, organizations, organization-units, positions, model organization-units, and model positions. These assignments are made using an alias; a design-time proxy to which a calendar definition can be associated at run-time.

The fact that an organization model entity holds a calendar alias does not mean that the calendar alias is associated with a calendar definition.

Candidate queries can be assigned to groups, positions, and model positions. When assigned to these entities, this property will describe its configuration.

A boolean indication of whether an organization-unit or position is derived from a dynamic organization model Template. If "false", or not specified, the entity is not derived from a dynamic organization model template.

For those organization-unit entities identified as extension points, this shows the configuration of that extension point, including any dynamic instance ID attribute mappings. The extension point configuration may not be complete; in which case the configuration will carry the property complete="false".

Positions and model positions can carry an integer value to indicate the number of resources that should, ideally, populate that position. This is purely for information and is not enforced, that is, fewer or more resources can be assigned.

Each organization model entity carries an optional label value. This is generally a non-normalized form of the name property entered in TIBCO Business Studio, but it can be used as a description of the organization model entity.

Organizations, organization-Units, positions, model organization-Units and model positions may be associated with a location. If so, this property gives the GUID, name, and label of that location entity. The location entity must be located within the same major version of the organization model as the entity referring to it.

Model organization-units may have any number of model organization-units within them (sub-units). This property array gives the GUID, name, and label of each model organization-unit entity. Each model organization-unit entity must be located within the same major version of the organization model as the model organization-unit.

The root organization-unit of a dynamic organization model instance (an organization model fragment generated from a dynamic organization model template) will carry the dynamic instance ID attribute values that distinguish that instance from all other instances of the same dynamic organization model template. These attributes consist of the attribute name (as configured in the dynamic organization model template) and the instance's value (taken from the LDAP attribute associated with the attribute in the extension point's configuration).

Organizations may have any number of organization-units located directly within them. This property array gives the GUID, name, and label of each organization-unit entity. Each organization-unit entity must be located within the same major version of the organization model as the organizations.

Organization-units may have any number of positions within them. This property array will give the GUID, name, and label of each position entity. Each position entity must be located within the same major version of the organization model as the organization-unit.

Organization-units, positions, and groups may hold any number of privileges, which are inherited by those resources directly within them (for groups, those resources within sub-groups inherit the privileges of parent groups). This property array gives the GUID, name, and label of each privilege held. Each privilege entity must be located within the same major version of the organization model as the entity referring to them.

For those privilege holdings that refer to a qualified privilege, the holding will also list any qualifier value that applies to the holding.

Push destinations allow resources to be notified of offered and allocated work items using mechanisms such as e-mail or SMS. Push destinations can be configured against organizations, organization-units, positions, model organization-units, and model positions.

Groups, positions and model positions may hold any number of required capabilities. Although not enforced; these are the capabilities a resource should hold in order to be a member of that group or position. This property array gives the GUID, name, and label of each required capability. Each capability entity must be located within the same major version of the organization model as the entity referring to them.

For those required capabilities that refer to a qualified capability, the holding will also list any qualifier value that applies to the holding.

For those organization model entities to which resources can be directly assigned (groups, positions and capabilities), the number of resources assigned to those entities can be, optionally, included in the response.

An organization model can include a model schema; a meta-model that gives type information to entities within the organization model itself. In particular, the model schema entities provide attributes that can be assigned to organization model entities that reference those entities.

Organizations, organization-units, positions and locations can carry a reference to a model schema entity. If so, this property gives the GUID, name, and label of the model schema entity. The model schema entity must be located within the same major version of the organization model as the entity referring to them.