EntitlementConfiguration DTD: type element

The <type> node defines an entitlement type.

Example

<type id="user" name="account" category="security account">
	<display-name>
		<value langCode="EN">User</value>
	</display-name>
</type>

2. Attributes

Attribute Value(s) Default Value

category CDATA

the category helps grouping different entitlements with the same type name into categories. E.g. Active Directory supports multiple different types of groupings: local groups, security groups, and distributions lists. All are of type name “group” but have different categories “security grouping”, “security grouping”, and “other grouping”.
#REQUIRED

id CDATA

the ID (id) identifies a type uniquely per managed system. There cannot be two entitlements with the same same type ID defined for the same managed system (driver).
#REQUIRED

name account | group | other

the name provides a non-localized identifier for the type. Typically the name should resemble or be equal to the English display name of type. Type names don't have to be unique per managed system. There can be two or more entitlements with the same same type name defined for the same managed system (driver).
group

type

Example

1. Allowed Content

2. Attributes

3. Content Rule

4. Parent Elements

Attribute	Value(s)	Default Value
category	CDATA the category helps grouping different entitlements with the same type name into categories. E.g. Active Directory supports multiple different types of groupings: local groups, security groups, and distributions lists. All are of type name “group” but have different categories “security grouping”, “security grouping”, and “other grouping”.	#REQUIRED
id	CDATA the ID (id) identifies a type uniquely per managed system. There cannot be two entitlements with the same same type ID defined for the same managed system (driver).	#REQUIRED
name	account \| group \| other the name provides a non-localized identifier for the type. Typically the name should resemble or be equal to the English display name of type. Type names don't have to be unique per managed system. There can be two or more entitlements with the same same type name defined for the same managed system (driver).	group