Mandatory Attribute Support

IEF-CADToMxMandatoryAttrMapping attribute in the Global Configuration Object allows the System Administrator to provide the mapping to synchronize certain attributes from CAD to ENOVIA.

If the Administrator marks certain attributes as mandatory by specifying them in the IEF-CADToMxMandatoryAttrMapping in the GCO, then these attributes are always synchronized whenever designs are saved using ENOVIA > Save.

Mandatory Attributes are supported for the following reasons:

  • Allow the Administrator to provide mandatory attributes a value that should be used irrespective of the value that exists on the CAD tool
  • Allow the Administrator to provide a value that can be over-written by the CSE if required.
  • Allow the CSE to provide the value of the mandatory attributes.

This page discusses:

Rules

This section lists the rules to be followed while mapping the mandatory attributes.

The following rules must be followed while mapping mandatory attributes:

  • If an attribute to be declared mandatory then it should be present in the IEF-CADToMxMandatoryAttrMapping as well as in the MCADInteg-CADToMxAttribMapping.
  • All mandatory attributes must have a value.
  • If the Administrator sets attributeType as mandatory, then the Administrator should provide a value in the attributeValue and must not leave it empty. An error message informing that mandatory attributes cannot be empty is displayed if left empty.
  • If the Administrator sets attributeType as default, then the Administrator should provide a value in the attributeValue in the IEF-CADToMxMandatoryAttrMapping or in the CAD file propeties. If both are empty, an error message informing that mandatory attributes cannot be empty is displayed.
  • If the Administrator sets attributeType as null, then it must be ensured that the attribute has a value and is not empty if it exists in File Summary Properties or File Custom Properties. If empty, an error message saying that the mandatory attributes cannot be empty is displayed.

Format

This section shows the format of CAD to ENOVIA Mandatory attribute.

The format of the CAD to ENOVIA Mandatory attribute name is, attributeName,attributeValue,attributeType

In this mapping,

  • attributeName: The name of the attribute. Example: $$Comments$$
  • attributeValue: The value of the attribute.Example: SolidEdge File
  • attributeType: The type of the mandatory value. The attribute Type can have the following values:
    • mandatory: This implies that the value specified in the attributeValue should 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 as 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 it's own based on some criteria. As of now, the CSE picks up the attributeValue and synchronizes this with X-CAD Design Management. In future releases of CSE, CSE may choose to over-write this attributeValue with a value of its own. The System Administrator MUST provide a value inattributeValue as 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 it's value to synchronize it with the X-CAD Design Management attribute. If a file or custom attribute is specified as nullthen that property should contain a value as mandatory attributes are intended to have a value. The System Administrator should not provide a value in the attributeValue, as it will not be used by the CSE.