Creating a Configuration Feature

To create a configuration feature, do one of the following:

• From the global My Enovia menu, under Variant Configuration, select Configuration Features, then from the page Actions menu, select Create Configuration Feature. This creates a stand-alone configuration feature that can be reused across multiple contexts using the Add Existing option.
• From the global Actions menu, under Variant Configuration, select Create Configuration Feature. This creates a stand-alone configuration feature that can be reused across multiple contexts using the Add Existing option.
• In the context of a product, product line, product variant, product version, or configuration feature, from the Configuration Features page, select the desired context object, click Enable Edit, then from the page Actions menu, select Create Configuration Feature.
• In the context of a model, from the Configuration Features page, on the Candidate Configuration Features tab, from the page Actions menu, select Create Configuration Feature.

In all cases except from the global Actions menu, a Create New Configuration Feature slide-in window opens on the right side of the screen. In the case of the global Actions menu, a popup window opens.

Edit the fields as follows:

• Basics section:

  Name

  This field is required. Uncheck the AutoName check box to enable the Name field for editing. Leave the box checked if you want to allow the system to assign a name automatically.

  The following special characters are prohibited in names.

  Special Character	Description
  @	Commercial At Sign
  ,	Comma
  *	Asterisk
  ?	Question Mark
  [	Left Square Bracket
  ]	Right Square Bracket
  #	Number Sign
  $	Dollar Sign
  {	Left Curly Bracket
  }	Right Curly Bracket
  \	Backslash
  "	Double Quotation Mark
  <	Less-Than Sign
  >	Greater-Than Sign
  |	Vertical Line
  %	Percent Sign
  ;	Semicolon
  &	Ampersand
  =	Equals Sign

  Note: If you should need to use any of these special characters in a name, you can edit the emxFramework.Javascript.NameBadChars property in the emxSystem.properties file located in SERVER_INSTALL\managed\properties\ (Windows) or SERVERHOME/managed/properties/ (UNIX).

  Type

  This field is required. The default type is Configuration Feature.

  Revision

  This field is required. The default is based on the policy definition (see Policy field, below).

  Description

  Enter a description for the new configuration feature.

  Display Name

  This field is required. The default is the same text that was entered in the Name field. See above for rules regarding use of special characters.

  Display Text

  Enter any text to be used for display purposes in the product configuration.

  Owner

  The default owner is the current user. Click to select a different owner.

  Design Responsibility

  Enter the Responsible Design Organization (RDO) for the configuration feature. Click to select an RDO from a list of available organizations. Click Clear if you want to erase the field and start over. The default design responsibility is based on the context. If there is no context (i.e., the page was accessed from the global MyEnovia or Actions menu), then this field is initially blank.

  Policy

  The policy (lifecycle) is that defined for a Configuration Feature object. This cannot be changed.

  Vault

  The vault in which the new configuration feature will be created is displayed. Click if you want to select a different vault.

• Configuration Criteria section:

  Selection Type

  Select Single or Multiple.

  Key-In Type

  Select one of the following key-in types:
  

  • Input
  • Date
  • Real
  • Text Area
  • Integer
  • Blank (the default)

  The key-in type enables user-defined values for configuration features. For example, if a configuration feature Color has child configuration features Red and Black as choices, you can allow an additional choice of a user-defined color by providing another child configuration feature with a key-in type of Input.

  The key-in setting is allowed only on leaf-level configuration features (not configuration options). In other words, multi-level configuration feature structures are not allowed under a configuration feature that has a key-in type definition. This means that once a key-in type has been defined for a configuration feature, its children can only be configuration options. Attempting to create or add a configuration feature under another configuration feature that already has a key-in type definition will produce an error message.

  When a configuration feature is enabled for key-in:
  

  • If the Selection Type is Single, the entry removes any previous selection made.
  • If the Selection Type is Multiple, previous selections are retained and the entry is made available as the last choice.

Click Done to save your selections.