Personalizzazione avanzata > Business Logic Customization > Data Exchange using Standards in Windchill > STEP Data Exchange using EXPRESS > AP214 AIM Mapping > Sample Mapping Name Patterns
  
Sample Mapping Name Patterns
The following convention represents mapped element name and required_attributes:
A relative path, such as Template_instance/Name/value, get/set values by it.
An absolute path for a single element, such as /Application_context, which means this element is stored in the same level as the current element instead of a sub element.
An alias path, can use an alias to reduce duplicated mapped names. The AIM format does not use alias mapping
A value reference path, such as value_reference_product_related_product_category, which will be defined in the value_reference_mapping section as follows:
<value_reference name="value_reference_product_related_product_category"
mapped_name="/Product_related_product_category"
ref_attribute="Products/Product"
connect_reference="Formation/Product_definition_formation/ref/Of_product/
Product/ref" path="name" multiple_instances="true" />
This creates a Product_related_product_category element in the same level as the current element and stores the value to name. Product_related_product_category also contains a reference of current elements by product, which can be used as a value reference to reduce duplicated mapped names.
A second value reference path (sometimes referred to as “value reference path two”), such as value_reference_describe_link_product_definition_shape, which will be defined in value_reference_mapping section as follows:
<value_reference name="value_reference_describe_link_product_definition
_shape" ref_type="/Product_definition_shape" attribute_name=
"Definition/Product_definition_shape/ref">
<sub_value_reference attribute_name="" identifier=""
required_attributes="expId={UUID}" />
</value_reference>
A Product_definition_shape element is created to store the ID, keep the name as empty and set the element to current element by Definition/Product_definition_shape/ref. You can also use a value reference to reduce duplicated mapped names.
Tips
The following variables can be used in required_attributes:
{ROOT} : Use the root object of this element
{UUID} : Create a random UUID
{KEY} : Use the name of the current attribute
{VALUE} : Use the string representation of the current attribute’s value