Procedure for Adding a Subtype

A subtype is derived from an existing type in a parent-child relationship, and then customized as needed. When defining the subtype (the child), you only need to specify the differences between it and the type you derived it from (the parent). A child inherits all attributes, methods, triggers, governing policis, and allowed types for relationships.

You can use Business Modeler or MQL; this procedure describes how to add a subtype using Business Modeler. See Types for a list of types. For more details on all the options available when defining types, see the Business Modeler Guide.

  1. Determine which existing type is closest to your needs.

  2. Select Object > New > Type.

  3. On the Basics tab, enter these details:


    • Name. Enter a name. The name must be unique within the ENOVIA system.
    • Description. Describe the purpose of this type: how it will be used.
    • Derived From. Click the ellipsis button and select the existing Type from Step 1.
    • Abstract Type. Only check this box if this type will be used as a parent type in a hieraarchy and not used to create business objects. The convention for naming abstract types is to use all UPPER CASE letters.
    • Hidden.When checked, the type does not show in any type chooser lists (although it can be specified using MQL). This option can be used for types needed by software code, but not viewed by the end user.

  4. Optionally, add an icon to display for this type.

  5. Assign attributes to the subtype:

    1. Click the Attributes tab.

      The dialog box lists the attributes inherited from the parent type.

    2. Click Add.
    3. Select the needed attributes. You can use the Name box and Filter button to search for needed attributes.
    4. Click OK.
    5. To remove any unneeded attributes: click the attribute name, then click Remove.

  6. Assign even triggers to the subtype:

    1. Click the Triggers tab.

      The dialog box lists the triggers inherited from the parent type.

    2. To remove any unneeded triggers: click the trigger name, then click Remove.
    3. Click Add.
    4. Select the needed trigger. You can use the Name box and Filter button to search for the needed trigger.
    5. Click OK.
    6. Double-click the trigger name. The Edit Trigger dialog opens.
    7. Type the name of the program to associated with the trigger (or use the Program Chooser to locate it) in the text box corresponding to the type of trigger:


      • Check. The trigger executes before the event occurs.
      • Override. The trigger replaces the even transaction.
      • Action. The trigger executes after the event occurs.

    8. In the Input field for each trigger, optionally define arguments to pass into the program.
    9. Repeat steps f-g for each trigger program.
    10. To remove any unneeded trigger: click the trigger name, then click Remove.

  7. Assign methods to the type.

    A method is a program that is associated with a type. These programs can be executed by users when they select any business object of this type. Programs selected as methods require a business object as a starting point for executing.

    1. Click the Methods tab.
    2. Click Add.
    3. Select the needed method. You can use the Name box and Filter button to search for the needed method.
    4. To remove any unneeded method: click the method name, then click Remove.

  8. Register the subtype:

    See Working with Administrative Properties for complete details on using the Utilites menu options.

    1. Log into the ENOVIA system as a user with the Administration Manager role.
    2. From the global toolbar, select > Utilities > Property Registration > Admin Type.
    3. From the Admin Type drop-down list, select Type
    4. In the Un-Registered Admins list, click the name of the new subtype.
    5. Enter values for the properties as needed. If you are usingENOVIA Business Process Services’s convention for symbolic names, use the format [administrative type]_[object name with no spaces]:


      • When entering the version number, use dashes as separators, not periods.
      • When entering symbolic names for custom administrative objects, do not use the exact same naming convention as ENOVIA Business Process Services uses unless you are working closely with ENOVIA Engineering. You can use a slight variation of the naming convention, such as adding an abbreviation for your company’s name. For example, instead of type_Part, a company with the abbreviation ACM could add type_ACMPart.

    6. Click Create Registration.

      The property values are saved and the type is moved into the Registered Admins list.

    7. Click Close.