Procedure for Creating an Attribute

Attributes can be used with Types and Relationships. When creating a new application or customizing an existing product, you can create new attributes to meet your business needs. You can use Business Modeler or MQL; this procedure describes how to create an attribute using Business Modeler.

See Attributes for a list of attributes, and for lists of the attributes used for specific types and relationships. For more details on all the options available when defining attributes, see the Business Modeler Guide

  1. Determine if an existing attribute meets your needs. If not, continue with this procedure.

    Note: If you use an existing attribute, do not change its details (data type, range values, and so on). If you do, you could introduce problems to any product that uses that attribute.

  2. Select Object > New > Attribute.

  3. On the Basics tab, enter these details:


    • Name. The attribute name must be unique within the ENOVIA database.
    • Description. Describe the purpose of this attribute: how it will be used and the meaning of the data it holds.
    • Type. Select the data type this attribute will store:
      • String
      • Real
      • Integer
      • Date and Time
      • Boolean
    • Default. If the attribute should be pre-populated with a default value when the type or relationship is created, enter that value here.
    • Dimension. For an attribute with the integer or numeric data type, select a dimension. Dimensions associate units of measurement with the attribute and are used for converting from one units to another (such as from one weight system to another).
    • Max length. For an attribute with the string data type, enter the maximum number of characters that can be entered for the attribute value. The default maximum is 0, meaning that an unlimited number of characters can be entered for the attribute value.

  4. Optionally, add an icon to display for this attribute. Only Business Administrators using Business Modeler see the icon; it is not used in any application that uses the attribute.

  5. Select the check boxes you want to use for this attribute:


    • Hidden. When checked, the attribute does not show in any attribute chooser lists (although it can be specified using MQL). This option can be used to hold values defined by software code, but not entered or viewed by the end user.
    • Multiline. Available when the data type is set to string. when checked, text wraps to tne next line as the user types and is shown in a scrollable text box. When not checked, the data entry field shows as a single line.
    • Reset On. Works with the Clone and Revision checkboxes. When a type that uses this attribute is cloned or revised, this checkbox determines if the value for this attribute is retained (not checked) or reset to the default value (checked). If no default value has been provided, this checkbox is unavailable.
    • Clone. Check if you want to use the default value for the attribute whenever a type that uses the attribute is cloned. Otherwise, the cloned type uses the current value of the original type.
    • Revision. Check if you want to use the default value for the attribute whenever a type that uses the attribute is revised. Otherwise, the revised type uses the current value of the original type.

  6. Define ranges for attributes where the user will select from a list of pre-defined values:

    1. Click the Ranges tab.
    2. Click Add.

      The Add Range dialog box opens. The content of this box is customized for the attribute's data type.

    3. Enter the range value and click OK.
    4. Repeat steps b-c for each range value you want to add.

  7. Add event triggers for the attribute. See Triggers for details on creating trigger programs.

    1. Click the Trigger tab.
    2. Click Add.
    3. Select the needed trigger. You can use the Name box and Filter button to search for the needed trigger.
    4. Click OK.
    5. Double-click the trigger name. The Edit Trigger dialog opens.
    6. 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.

    7. In the Input field for each trigger, optionally define arguments to pass into the program.
    8. Repeat steps f-g for each trigger program.

  8. Click Create.

  9. Register the attribute. See Register Administrative Objects.

    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 Attribute.
    4. In the Un-Registered Admins list, click the name of the new attribute.
    5. Enter values for the properties as needed. If you are using 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 attribute_Color, a company with the abbreviation ACM could add attribute_ACMColor.

    6. Click Create Registration.

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

    7. Click Close.

The attribute can now be added to types and relationships.