pdm-cust-config.xml Configuration File

To integrate your company’s customized data model in X-PDM exchanges, it is possible to configure a mapping in a file called pdm-cust-config.xml.

An example of object and attribute mappings of a sample customized 3DEXPERIENCE platform data model is provided with the installation of the adapters.

The structure of file pdm-cust-config.xml is a list of <Object> xml tags inside the <ObjectsConfig> xml container element:

<XPGCustConfig …>
  <ObjectsConfig>
       <Object …>
          <attribute …>
          <attribute …>
           …
           </Object>
           <Object …>
           <attributeGroup …>
              <attribute …>
              <attribute …>
           </attributeGroup …>
            …
      </Object>
     …
  </ObjectsConfig>
</XPGCustConfig>

Each <Object> xml element corresponds to the declaration of a mapping between a XPDMXML entity and object type of the 3DEXPERIENCE platform data model. Each <Object> xml element contains declarations for attribute mapping. The format of <Object> xml element is as following:

<Object XPGXMLType="…" V6Type="…" V6CustoName="…" MappingType="…">

Where,

• XPGXMLType: XPDMXML entity name mapped (in the default mapping) to the 3DEXPERIENCE platform entity from which the exchanged entity is deriving.

• V6Type/V6CustoName: 3DEXPERIENCE platform entity type (existing or customized).

  See Engineering Exchange or E-BOM Exchanges section for the list of default mapping of entities.

  Notes:

  • For Engineering Exchange scenario: V6CustoName is not used. Only V6Type containing the actual object type name is necessary for mapping.
  • For E-BOM Exchanges scenario: V6Type is not used. Only V6CustoName containing the symbolic object type name (type_XXX) is necessary for mapping.
• MappingType: User-defined name corresponding to the xml attribute mappingType object elements in the XPDMXML file.
  Note: The mappingType value is important and must be coherent between export and import. An error message is displayed, if the mappingType value provided on objects is incorrect at import (either because it does not correspond to a mapping entry or to 3DEXPERIENCE platform type name).

For each object, an attribute mapping should be provided. The attribute mapping is defined into an <attribute> element. The format of the <attribute> xml element is as following:

<attribute XPGName="…" V6Name="…" type="…" Export="…" Import="…" >

Where,

• XPGName: Is the mapped name of the 3DEXPERIENCE platform attribute.

  It is the value (exported and expected at import) of the name attribute on the Property elements in the XPDMXML file.

• V6Name: name of 3DEXPERIENCE platform attribute to be exchanged.

  It must correspond to an attribute declared on the 3DEXPERIENCE platform object type.

• type: attribute data type.

  Some of the possible values are boolean, double, integer, string, dateTime as well as their list form (XXXList).

  Refer pdm-cust-config.xsdfile, for a complete list of possible values.

• Export/Import: true or false.

  To prevent exporting or importing any specific attributes, the Export or Import attribute must be set to false in the corresponding attribute xml element.

• Attributes can be grouped in attribute groups.

  All the required attributes must be defined within the attributeGroup xml element for which the name attributes defines the name of the group, which corresponds to the name attribute on the Property elements in the XPDMXML file.

  For example: <attributeGroup name="…">