11.0 SP12 Extended AML Enhancements

This section contains examples of AML Enhancements released as part of SP12. You can use AML to set xProperty values and attributes such as their permission_id and explicit flag. For example:

<AML>

  <Item type="Part" id="816AEDE3506042C38211796A3581F4B9" action="edit">

    <xp-shape set="value">Cylindrical</xp-shape>

  </Item>

</AML>

Available options for the “set” attribute are “value”, “permission_id”, and “explicit”. It does not matter if the xProperty is defined or not. If you want to explicitly define the xProperty, you must use “explicit.” Use the “|” separator to set several operations at the same time:

<AML> 
  <Item type="Part" id="816AEDE3506042C38211796A3581F4B9" action="edit"> 

    <xp-color set="value|permission_id|explicit" permission_id="A518B142B9CB4013A85392AA60AB7899" explicit="1">blue</xp-color> 
</Item> 
</AML> 

The xClasses set on an Item are configured as relationships in AML using the pattern %itemtype_name%_xClass. The type name is automatically defined based on the name of the ItemType specified on the xClassification Tree. This means that the xClass name for the item type “Part” would be “Part_xClass.” For the “CAD” item type the xClass name would be “CAD_xClass”.

For example:

<Item type="Part" id="816AEDE3506042C38211796A3581F4B9" action="update"> 

<Relationships> 

<Item type="Part_xClass" id="CF3E37DFE57E451CB910FDFF6B429579" action="add"> 

<related_id>51CF3CA830AD49BB97CE9C3553863A76</related_id> 

</Item> 

</Relationships> 

</Item>