Mandatory Attribute Support

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

Mandatory Attributes are supported to:

  • Allow the user to synchronize certain attributes from CAD to ENOVIA.
  • Allow the Administrator to provide values for mandatory attributes 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 App if required.
  • Allow the App to provide the value of the mandatory attributes

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.

This page discusses:

Rules

Few rules / information regarding mandatory attributes:

  • Attributes are declared as mandatory only if it is present in the IEF-CADToMxMandatoryAttrMapping and in the MCADInteg-CADToMxAttribMapping flags.
  • 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 properties. An error message informing that mandatory attributes cannot be empty is displayed if both are empty.
  • 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. An error message saying that the mandatory attributes cannot be empty is displayed if empty.

The mandatory attributes rule is applied when attributes are copied from Inventor to ENOVIA during the ENOVIA > Save operation.

Format

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

Each section of this format is:

  • attributeName: The name of the attribute. Example: $$Comments$$
  • attributeValue: The value of the attribute.Example: Inventor File
  • attributeType: The type of the mandatory value. There are three values that the attribute Type can hold. This is discussed below with the meaning of each type:
  • mandatory: This implies that the value specified in the attributeValue should be used by the App as the value of the attribute. The App 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 App as the value of the attribute or the App can choose to over-write this value with a value of it's own based on some criteria. As of now, the App picks up the attributeValue and synchronizes this with the X-CAD Design Management. In future releases of App, App may choose to over-write this attributeValue with a value of its own. The System Administrator MUST provide a value in attributeValue as mandatory attributes cannot be blank.
  • null: This implies that the App 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 App.

Known Limitation for Relationship Attributes

The following are the known limitations for Relationship Attributes:

  • Relationship Attributes are not supported for Inventor.
  • Any transformation related operations through the Product Structure Editor such as, Add Existing, Add New, Replace, Cut, Copy and Paste are not supported.

    Exception to this behavior is Replace Revision operation from the Edit Actions menu, which can be performed by "CAD Revision Manager" on or after finalization state, since Replace Revision does not involve any changes in the transformation matrix on the parent - child relationship.