Customizing the Part Specification Type

In Engineering BOM Management, specifications are objects connected to a part with the Specification relationship. Specification types are: CAD Model, CAD Drawing, Drawing Print, and Part Specification. CAD Model, CAD Drawing, and Drawing Print are types for those three kinds of drawings.

This task shows you how to:

Creating a Type as a Subtype to Part Specification

As business administrator, you can create a type of specification by extending the Part Specification type to include any kind of document that users want to connect to a part with the Specification relationship.

  1. To create the subtype, extend it from the abstract type Part Specification.
  2. Register the new subtype. For details, see Legacy ENOVIA Web Apps Customization Guide:Registering Your Own Administrative Objects.
  3. In the emxFrameworkStringResource.properties file define the string resource for the new subtype. Use this format for the definition:

    emxFramework.Type.<New_Spec_Type> = <New Spec Type Name>

    For example:

    emxFramework.Type.Test_Specification = Test Specification

  4. Create a small icon image to represent the new type. Use the following format to name the image:

    iconSmall<NewSpecType>.gif

    Store the image in the common/images directory.

  5. Optionally, set up autonaming so users creating new specification objects of this subtype can select the Autoname option to have specifications automatically named and numbered. For information about how the autonaming process works and how to configure autonaming, see Legacy ENOVIA Web Apps Customization Guide:Configuring Automatic Business Object Naming.

Creating a New Specification Type

Instead of creating a new type of specification as a subtype of part specification, you can create a new specification type. This type can include any kind of document that users want to connect to a part with the Specification relationship.

  1. Register the new subtype. For details, see Legacy ENOVIA Web Apps Customization Guide:Registering Your Own Administrative Objects.
  2. In the emxFrameworkStringResource.properties file define the string resource for the new subtype. Use this format for the definition:

    emxFramework.Type.<New_Spec_Type> = <New Spec Type Name>

    For example: 

    emxFramework.Type.Test_Specification = Test Specification

  3. Create a small icon image to represent the new type. Use the following format to name the image:

    iconSmall<NewSpecType>.gif

    Store the image in the common/images directory.

  4. Modify the following relationships:

    • Part Specification
    • New Specification - Specification Revision
    • Request Specification Revision
    • Raised Against ECR

  5. Define the Check Create option for the relationship Part Specification such that the system checks that the policy of the specification object is compatible with that of a specification. (The specification object should have these policy states: Review, Approved, and Released. See Part Specification Policy States.)
  6. To have the ECR Find Specification form display the document type that you created, modify the eServiceEngineeringCentral. Types property in the emxEngineeringCentral.properties file. To this property, add the new document type.

    eServiceEngineeringCentral.Types=[existing types],<New Type>

  7. Optionally, set up object generation and autonaming so users creating new specification objects of this type can select the Autoname option to have specifications automatically named and numbered.

Part Specification Policy States

To use a document as a part specification, the document policy must have the following states mapped:

  • state_Frozen. This must not be the first state in the policy.
  • state_Approved. This must come after state_Frozen.
  • state_Released. This must come after state_Approved.

For example the Type "Technical Specification" currently has the following states:

  • property = state_Draft value Draft
  • property = state_Frozen value Peer Review
  • property = state_FormalApproval value Formal Approval
  • property = state_Issued value Issued
  • property = state_Obsolete value Obsolete

To connect this Type as a Part Specification, add these symbolic names to the Technical Specification policy:

  • property = state_Frozen value Peer Review
  • property = state_Approved value Formal Approval
  • property = state_Released value Issued

Register these symbolic names as described in the Legacy ENOVIA Web Apps Customization Guide.