Integration with Other Applications > Windchill Workgroup Manager Documentation > Arbortext IsoDraw > Administration and Configuration > Configuring Business Practices > Configuring Attributes > Implicit Parameter-to-Attribute Mapping
  
Implicit Parameter-to-Attribute Mapping
Implicit mapping occurs when the authoring application parameter uses the exact syntax as its Windchill attribute. This makes the parameter publish automatically in the authoring application.
For example, a CAD document has a set of global attributes that are published to the authoring application. From this set, use the global attribute Name and map it to the NAME of the parameter in the authoring application. The subtypes used in this case are:
EPMDocument
EPMMemberLink
EPMReferenceLink
If Name is the same by a case-sensitive evaluation, the two are implicitly mapped. Do not add other parameters to the CAD document unless they are explicitly mapped. For example, if the administrator has created a global attribute with the name, Cost, then the user must also create the global attribute with the name Cost so it is implicitly mapped. If the authoring application user creates COST, it will not be mapped.
If the authoring application does not support case-sensitive parameter names, the name is treated in all uppercase characters. For example, if the authoring application treats Cost and COST the same, then Windchill receives and handles this attribute as COST. The Windchill global attribute name must also be COST.
* 
Although the user may create an authoring application parameter called Cost, it is passed to Windchill as COST. Therefore, ensure the authoring application parameter name is in all uppercase so that it is implicitly mapped in Windchill. Other properties are not added to the CAD document, unless they are explicitly mapped.
If a mapped parameter is inconsistent with its corresponding global attribute, the following occurs:
Inconsistent type
If the two are not the same type then a warning is given to the user on upload; but upload continues. The value is not pushed to the CAD document.
Inconsistent units
If the quantity of measure is different between the attribute and the parameter, then the CAD document receives an error on upload. The user is notified to check in the CAD document.