Mandatory Attribute Support

The attribute IEF-CADToMxMandatoryAttrMapping in the Global Configuration Object allows the Integration Administrator to provide the mapping.

Mandatory Attribute support is implemented is for the following reasons:


  • To allow the user to synchronize certain attributes from CAD to ENOVIA, regardless of whether the user has selected the Copy Attributes option on the Checkin page. If the Integration Administrator marks attributes as mandatory, by putting them in the IEF-CADToMxMandatoryAttrMapping in the GCO, the indicated attributes will always be synchronized, regardless of whether the user selects Copy Attributes.
  • To allow the System Administrator to provide mandatory attributes a value that should be used, regardless of the value that exists on the CAD tool.
  • To allow the System Administrator to provide a value that can be over-written by the CSE if the CSE so desires.
  • To allow the CSE to provide the value of the mandatory attributes.

The type of the Mandatory Attribute is defined in the Mandatory Attribute format.

The format of the CAD to ENOVIA Mandatory Attribute name is

attributeName,attributeValue,attributeType

The attribute attributeName: indicates the name of the attribute. For example: $$Comments$$.

The attribute attributeValueindicates the value of the attribute.For example: a SolidWorks File.

The attribute attributeType indicates the type of the mandatory value, including:


  • mandatory: This implies that the value specified in the attributeValueshould be used by the CSE as the value of the attribute. The CSE MUST ignore the value of such attributes, as it exists in the File Summary Properties or the File Custom Properties. The System Administrator MUST provide a value in attributeValue, because mandatory attributes cannot be blank.
  • default: This implies that the value specified in the attributeValue can be used by the CSE as the value of the attribute, or the CSE can choose to over-write this value with a value of its own. The CSE picks up the attributeValue and synchronizes this with the ENOVIA Designer Central. In future releases, CSE may choose to over-write this value with a value of its own. The System Administrator MUST provide a value in attributeValue, because mandatory attributes cannot be blank.
  • null: This implies that the CSE should search this attribute in the File Summary Properties or in the File Custom Properties and pick its value to synchronize it with the ENOVIA Designer Central attribute. If a file or custom attribute is specified as null, then that property should contain a value, because mandatory attributes should have a value. The System Administrator should not provide a value in the attributeValue, as it will not be used by the CSE.

Rules for Mandatory Attributes

This section lists the rules for mandatory attributes.


  • To declare an attribute mandatory, specify the attribute in IEF-CADToMxMandatoryAttrMapping as well as in MCADInteg-CADToMxAttribMapping.
  • All mandatory attributes must have a value.
  • If the system administrator sets attributeType as mandatory or default, then he should provide a value in the attributeValue. It must not be empty. If it is empty, an error message prompts the user, indicating that mandatory attributes cannot be empty.

    Note: The mappings for system attributes must always be in lower case on the Mx side.

  • If the system administrator sets attributeType as null, then the CAD user must ensure that the attribute, if it exists in File Summary Properties or File Custom Properties, should hold a value and is not empty. If it is empty, an error message prompts the user, indicating that mandatory attributes cannot be empty.

The mandatory attribute rules listed above are applied when saving with or without the Copy Attributes option selected.