Gets the annotations attached to the part instance.
This gets an array of AnnotationGroupInfoInterface.
DO NOT modify in place this array, this results in undefined behavior.
Each part instance may have specific documents attached to it.
This is a list that tells the attached documents to this part instance.
The list of attached documents.
Gets the security tags of this instance.
Please refer to DataSessionInterface for an explanation of the tag system.
DO NOT modify in place this array, this results in undefined behavior.
Each part instance may have specific metadata attached to it with a specific document.
This is a list of all the instance metadata documents of the given part instance.
DO NOT modify in place this array, this results in undefined behavior.
Each child of an instance is linked to its parent with an optional link metadata document.
This is a list of all the link metadata documents of the given part instance.
If defined, the link documents are retrieved and included in the definition of the child.
DO NOT modify in place this array, this results in undefined behavior.
A part metadata document is shared among all part instances of the same part.
This is a list of all the part metadata documents of the given part instance.
A part is the definition of a single element of the DMU that may be instantiated multiple times.
DO NOT modify in place this array, this results in undefined behavior.
Gets the status flags of to this part instance.
The status flags are the OR of PartInstanceInfoStatusFlag.
The status flags of this part instance.
The InstanceMetadataInterface tells about the information linked to a
part instance, be it a node or a leaf.The InstanceMetadataInterface is included in the PartInstanceInfoInterface or ChildrenPartInstanceInfoInterface, which is retrieved by an IdCardGetterInterface or ChildrenIdCardGetterInterface. In the case of PartInstanceInfoInterface, the retrieved data is actually an AncestryInstanceMetadataInterface that provides also the World Matrix of the
part instance.There is a unique instantiation chain of
part instances, starting from the rootpart instanceto a specificpart instance(this is the definition of apart instance). The InstanceMetadataInterface is one element of such a chain.The InstanceMetadataInterface shows the metadata documents and the properties of a
part instance.The InstanceMetadataInterface is organized by document types (
part metadata documents,link metadata documents,part instance metadata documents).Such metadata documents may be :
part metadata documents: these documents are shared among all the instances of the samepart(a bolt for example).link metadata documents: when defining a child of apart instance, a metadata document may be set to define the link between the twopart instances. The childpart instanceincludes the link metadata document (as such, the rootpart instanceof the DMU cannot have a link metadata document and thus its link metadata document is empty).instance metadata documents: the givenpart instancemay have specific information attached to it (not shared by all the instances of the samepart, as a serial number for example).All these documents follow the same pattern :
Please remember that the part instances that include specific
metadata documentscannot be queried by theirstring idbut by theirinteger ids(see Search).NB :
link metadata documentsare used for computing the configurations (WorkingSetInterface, Main concepts) of the DMU. A configuration is a set of included or excluded effectivities. Any link that satisfies the requirements in term of effectivities is included in the configuration, meaning the childpart instanceof the link will be available in the given configuration. If not, the given childpart instancewill not be included. Herelink metadata documentsonly expose their internal content and not the effectivities.Warning : the documents content may change depending on the given configuration, as such, some fields may appear or not depending on the chosen configuration.
The InstanceMetadataInterface include the documents of the part instance hierarchy if included in a PartInstanceInfoInterface, if included in a ChildrenPartInstanceInfoInterface, then the documents are the one of the children of the requested
part instance. The IdCardGetterInterface.retrieveIdCard and ChildrenIdCardGetterInterface.retrieveChildrenIdCard will return the same number of PartInstanceInfoInterface than the number ofpart instancesthat were queried.A chain, or children are exposed as an array of InstanceMetadataInterface with the size of the chain of the
part instances, or the number of children of a part instance. In the case of a chain, the first item in the chain is the rootpart instance, the last item is thepart instancethat was queried by IdCardGetterInterface.retrieveIdCard. In the case of a children list, the order is irrelevant.The InstanceMetadataInterface also shows if the given
part instancehas any attached document (see DocumentContentGetterInterface and AttachedDocumentInfoInterface) attached to it, if it is displayable.Here is an example of an InstanceMetadataInterface :
The InstanceMetadataInterface may be queried by the following code :
or :
With async calls :
or :
The InstanceMetadataInterface documents contains fields that are included in the AttributesDictionaryInterface. Just look for the given attribute in the AttributesDictionaryInterface.
Any field may have the given type, an array of the given type or null (depending on AttributeInfoInterface.getAttributeType). Any field may have not be included in the AttributesDictionaryInterface, in this case, such metadata cannot be filtered, since it cannot be indexed. Such data that cannot be indexed can be found in the DocumentContentInterface.getNonIndexedContent fields.
See