# Data Object - PbmCapabilityPropertyMetadata(pbm.capability.PropertyMetadata)

Property of
  PbmCapabilityMetadata
Extends
  DynamicData
See also
  PbmCapabilityTypeInfo, PbmExtendedElementDescription

## Data Object Description

The PbmCapabilityPropertyMetadata data object describes storage capability. An instance of property metadata may apply to many property instances (PbmCapabilityPropertyInstance).

Properties

Name | Type | Description
--- | --- | ---
allowedValue* | xsd:anyType | All legal values that the property may take on, across all implementations of the property. This definition of legal values is not determined by any particular resource configuration; rather it is inherent to the definition of the property. If undefined, then any value of the correct type is legal. This object must be a generic container for the type defined for the property; see PbmBuiltinGenericType for the supported generic container types.
defaultValue* | xsd:anyType | Default value, if any, that the property will assume when not constrained by requirements. This object must be of the type defined for the property.
id | xsd:string | Property identifier. Should be unique within the definition of the capability. Property instances refer to this identifier (PbmCapabilityPropertyInstance.id).
mandatory | xsd:boolean | Indicates whether incorporating given capability is mandatory during creation of profile.
requirementsTypeHint* | xsd:string | A hint for data-driven systems that assist in authoring requirements constraints. Acceptable values defined by PbmBuiltinGenericType. A property will typically only have constraints of a given type in requirement profiles, even if it is likely to use constraints of different types across capability profiles. This value, if specified, specifies the expected kind of constraint used in requirement profiles. Considerations for using this information: This is only a hint; any properly formed constraint (see value) is still valid for a requirement profile. If VMW_SET is hinted, then a single value matching the property metadata type is also an expected form of constraint, as the latter is an allowed convenience for expressing a single-member set. If this hint is not specified, then the authoring system may default to a form of constraint determined by its own criteria.
summary | PbmExtendedElementDescription | Property name and description. The `summary.label` property (label) contains property 'name' in server locale. The `summary.summary` property (summary) contains property 'description' in server locale. The `summary.messageCatalogKeyPrefix` property (messageCatalogKeyPrefix) contains unique prefix for this property within given message catalog. Prefix format: <capability_unique_identifier>.<property_id> capability_unique_identifier -- string representation of PbmCapabilityMetadataUniqueId which globally identifies given capability metadata definition uniquely. property_id -- 'id' of this property id Eg www.emc.com.storage.Recovery.Recovery_site www.emc.com.storage.Recovery.RPO www.emc.com.storage.Recovery.RTO
type* | PbmCapabilityTypeInfo | Type information for the capability. The type of a property value (PbmCapabilityPropertyInstance.value) is specified as a builtin datatype and may also specify the interpretation of a collection of values of that datatype. type.typeName specifies the PbmBuiltinType. type.genericTypeName indicates how a collection of values of the specified datatype will be interpreted (PbmBuiltinGenericType).
Properties inherited from DynamicData
None

*Need not be set
Show WSDL type definition
<complexType xmlns="http://www.w3.org/2001/XMLSchema" xmlns:pbm="urn:pbm" name="PbmCapabilityPropertyMetadata"> <complexContent> <extension base="pbm:DynamicData"> <sequence> <element name="id" type="xsd:string"/> <element name="summary" type="pbm:PbmExtendedElementDescription"/> <element name="mandatory" type="xsd:boolean"/> <element name="type" type="pbm:PbmCapabilityTypeInfo" minOccurs="0"/> <element name="defaultValue" type="xsd:anyType" minOccurs="0"/> <element name="allowedValue" type="xsd:anyType" minOccurs="0"/> <element name="requirementsTypeHint" type="xsd:string" minOccurs="0"/> </sequence> </extension> </complexContent> </complexType>