Removing or Deleting a Logical Feature

Removing only removes the selected object from its immediate parent context in the given view but does not delete it from the database. Deleting completely deletes the selected object from the database, thereby removing it from any usage contexts. This topic describes how to remove or delete a logical feature from an object.

Before you begin:

Access the Logical Features summary page.

Note: The Remove option is available on the Logical Features summary page Actions menu only within the context of an object (model, product, logical feature, or manufacturing feature). The Delete option is available on the page Actions menu also when the Logical Features summary page is accessed from the global My Enovia menu.

Related Topics
About Logical Features
Creating a Logical Feature
Adding an Existing Logical Feature
  • To remove or delete a logical feature:

    Remove:

    1. Select one or more logical features, click Enable Edit, then from the page Actions menu, select Remove.
      Remove Logical Feature

      A confirmation alert is displayed:

    2. Click OK to confirm the removal.

      The following validations are performed before the selected item(s) are removed:

      Validation Description
      Frozen Parent If the parent context of the selected object is in a frozen state, an appropriate error message is displayed to block the removal. This condition is also enforced at the schema level based on the policy definition.

      The list of frozen states for the various types is retrieved from the following property in the emxConfiguration.properties file: 

      Configuration.FrozenState.type_XYZ = policy1.state_ABC,policy2.state_123

      Rule Usage If the relationship(s) being removed are referred to in any expression condition for a compatibility, preference, or quantity rule, an appropriate error message is displayed to block the removal.

      In the case of an inclusion rule, the removal is blocked only if the relationship is referred to in the right expression of the rule.
      Product Configuration Usage If the relationship(s) being removed are used in any product configuration, depending on the state of that product configuration, one of the following behaviors is triggered:
      • Pre-Release Configuration—In this case, the removal is allowed and the Product Configuration Selected Option is automatically updated. This also triggers a recomputation of the BOM XML.

        Note: An Action trigger is required to capture the update to the BOM XML cache. For details, see "Triggers" in the Studio Modeling - BPS Administration Guide.

      • Released Configuration—In this case, the removal is blocked. The block is done based on schema definitions. If the product configuration is released, then the product/logical feature context is also released, and therefore the Frozen Parent condition described above captures the blocking condition.

    Delete:

    1. Select one or more logical features from the list, then from the page Actions menu, select Delete.
      Delete Logical Feature
      A confirmation alert is displayed:

    2. Click OK to confirm the deletion.

      The following validations are performed before the selected item(s) are deleted:

      Validation Description
      Frozen Object If the selected object is in a frozen state, an appropriate error message is displayed to block the deletion. This condition is also enforced at the schema level based on the policy definition. In some cases, you may have delete access on the policy, but access may be configured to prevent deletions from the interface.

      The list of frozen states for the various types is retrieved from the following property in the emxConfiguration.properties file: 

      Configuration.FrozenState.type_XYZ = policy1.state_ABC,policy2.state_123

      Rule Usage If the select object is directly used in any expression or is used through associated logical feature relationships in any rule, an appropriate error message is displayed to block the deletion.

      In the case of an inclusion rule, the deletion is blocked only if the relationship is referred to in the right expression of the rule.
      Product Configuration Usage If the selected object(s) being deleted are used in any product configuration through logical feature relationships, depending on the state of that product configuration, one of the following behaviors is triggered:
      • Pre-Release Configuration—In this case, the deletion is allowed and the Product Configuration Selected Option is automatically updated. This also triggers a recomputation of the BOM XML.

        Note: An Action trigger is required to capture the update to the BOM XML cache. For details, see "Triggers" in the Studio Modeling - BPS Administration Guide.

      • Released Configuration—In this case, the deletion is blocked as the parent context objects are already in the Released state. The block is done based on schema definitions. There is no custom error message displayed for this scenario.
      Assembly Configuration Delete If the logical feature is successfully deleted, all associated assembly configurations are automatically deleted. This scenario is likely only when the logical feature is in a pre-release condition as it cannot be deleted in any other case.

      Note: An Action trigger is required to delete all of the assembly configurations. For details, see "Triggers" in the Studio Modeling - BPS Administration Guide.