Adding a New Type

X-CAD Design Management does not support creation of custom types from existing based types using web user interface unified typing tools.

In a customized or customer specific environment, if you have acess to MQL, then, it is possible to create new types which are derived from existing base types.

This task describes how to add new types in Connector for Inventor.

  1. Define a custom type.

    For example, define a new type "INV Engine Component" that is derived from parent type "MCAD Component" or "INV Component". Choose an appropriate parent type depending on the planned use of the new custom type.

  2. Register the new custom types. For more information, see Registering Your Own Administrative Objects in the Studio Modeling Configuration Guide.
  3. Add types to policies.
    1. Determine the policy that will be used to govern these types.
    2. Open the Business module and search for the policies that govern the revision and the iteration.
    3. Edit the policy that governs the iteration and using the "Governed Types" tab, add the new created type as governed type to this policy.
    4. Edit the policy that governs the revision and using the "Governed Types" tab, add the new created type as governed type to this policy.

      Perform this step only if any direct or indirect parent type of the newly created type is not already added as governed type. If any direct or indirect parent type of the newly created type is already added as a governed type, then the newly created type need not be explicitly added as governed type.

      For example, to use the "Inventor Design" and "Inventor Versioned Design" policies:

      Add the type "INV Versioned Engine Component" as governed type to "Inventor Versioned Design" policy.

      "INV Engine Component" need not be added explicitly to "Inventor Design" policy, as "CAD Model" that is an indirect parent of "INV Engine Component" is already added as a governed type to this policy.

  4. Add mappings to GCO using the following steps:
    1. Using the MQL, search the Global Config object for Inventor integration.
    2. Open the Edit Attributes dialog box.
    3. Search the MCADInteg-TypeFormatMapping attribute and add the following line to the existing mapping:

      Syntax

      <CAD Type>|<Custom type>,<format>

      For example,

      component|INV Engine Component,prt

    4. Search the MCADInteg-TypePolicyMapping attribute and add the following lines to the existing mapping:

      Important: If the custom type is governed by multiple policies, mention the policy names in comma separated format.

      Syntax

      <Custom type>|<Revision object policy 1>,<Revision object policy 2>

      For example,

      INV Engine Component|Inventor Design,Design Policy

    5. Search the IEF-Pref-MCADInteg-DefaultTypePolicySettings attribute and add the following line to the existing mapping:

      Notes:
      • In case the custom type is going to be governed by multiple policies, then this mapping will define which one of them will be the default policy.
      • In case the custom type is going to be governed by a single policy, then this policy name should be mentioned as default.

      Syntax

      (DEFAULTVALUE)<Custom type>|<Revision object policy>

      For example, (DEFAULTVALUE)INV Engine Component|Inventor Design

    6. Search the MCADInteg-BusTypemapping attribute and edit the existing mapping for the CAD type to specify the 3DEXPERIENCE platform type that should be used for a particular CAD type.

      Syntax

      <CAD Type>|<Custom type 1>,<Custom type 2>

      For example,

      component|INV Engine Component,INV Component

      Important: A single CAD type can be mapped to multiple ENOVIA types.

      When data of this CAD type is saved to 3DEXPERIENCE platform, the ENOVIA type that occurs first in the list is considered to be the default type of the object whenever the object of the mapped CAD type is saved to 3DEXPERIENCE platform. This default type can be changed using Type Selection on Save.

      For example,

      If the mapping is specified as, component|INV Engine Component,INV Component and an Inventor component is saved to 3DEXPERIENCE platform, it is saved to an object of type "INV Engine Component".

      If the mapping is specified as, component|INV Component,INV Engine Component and a simple Inventor component is saved to 3DEXPERIENCE platform, it is saved to an object of type "INV Component".