This documentation supports the 20.02 version of BMC Helix Platform. 
To view an earlier version, select 19.11 from the Product version menu.

Inheriting an existing record definition to a new record definition

You can create a record definition by extending or inheriting the details from an existing record definition.

Following are the advantages of inheriting from an existing record:

  • Prevents you from creating all the properties from the beginning.
  • Makes the record definition process faster.
  • Lets you inherit all the properties and behaviors of the super record definition.
  • Lets you modify properties such as fields and rules in the subrecord definition.

Records are defined as follows:

  • Super record definition: Is the existing record from which the properties and behaviors are extended or inherited.
  • Subrecord definition: Is the new record definition that inherits the properties and behaviors of the super record definition.

Although you can simply modify the inherited properties from the super record definition, the permissions of the super record definition do not get copied to the subrecord definition.You must separately add the permissions to the subrecord definition.

For example, if you have an existing record definition called Ticket, and you inherit this record definition to create a new record definition called Incident, then Ticket is the super record definition and Incident is a subrecord definition.

Note

Inheriting an existing record definition to a new record defintion is not supported for external record definitions.

Before you begin

Before you create and manage record definitions, ensure that you have created a project and deployed it in BMC Helix Innovation Studio. For more information, see Creating a Project using Maven and the Archetype.

Note

Application business analysts can customize the objects developed in their own applications and that are marked customizable by the developers, but cannot customize the objects developed in com.bmc.arsys. For example, objects in core BMC applications like Foundation, Approval, and Assignment cannot be customized.

To inherit an existing record definition to a new record definition

  1. Log in to BMC Helix Innovation Studio and navigate to the Workspace tab.
  2. Select the application or library to which you want to inherit a record definition.
  3. Select Records > New > Regular Record

    The record with default fields is displayed. 

  4. In the Details section, click .
  5. From Record Inheritance section, click Inherit from a Record Definition.
  6. From the Record to Inherit drop-down list, select the record definition from which you want to inherit the preferences.

    Note

    The Application/Library scoped definitions are marked with an asterisk ( * ). Ensure that you follow the guidelines listed in Object definition scope before you select these definitions.

    The following table provides information about the properties:

    ItemDescription
    Core Fields

    Inherits all the core fields from the super record definition to the subrecord definitions.
    If you select the Shared data with inheritors check box, the core fields of the super record definition are inherited by default.

    Note: You cannot remove any core fields from being inherited to the new record definition.

    Rules Inherits all the rules that are associated with the super record definition.
    Field Permissions Inherits all the permissions that are associated with the fields of the super record definition.
    Associations Inherits all the associations that are applied to the super record definition.

    Audit Field Properties

    Inherits all the field-level auditing properties that are configured for the super record definition.

  7. (Optional) Specify the inheritance properties for the record definition.  

    The following table provides information about the properties:

    UI ItemDescription
    Shared data with inheritors Shares a common database with all the subrecord definitions that are inherited from this record definition.
    You can search the database of super record definition and retrieve all the instances of super record definition and its subrecord definitions.
    When you select this check box, by default the core fields of the super record definition are inherited and cannot be modified.
    Make Abstract

    Prohibits the user from creating instances of that record definition.

    For example if Shape is abstract record definition and Circle is inherited record definition then you cannot create instance of Shape record definition.

    Make Final Prohibits the user from inheriting this record definition.
  8. Save the record definition.

Limitations for inheriting existing record definitions

When you inherit or extend an existing record definition to a new record definition, you might encounter the following limitations:

  • The subrecord definition cannot modify or delete the fields of the super record definition.
  • You can inherit only one record definition at a time.
  • You can stop extending or break the inheritance at any time if you have not selected the Share data with inheritors option.
  • You cannot customize the fields that you inherit in subrecord definitions. If you need to customize the inherited fields, you must customize the fields in super record definition and then inherit the record definition.

Related topic

Creating or modifying regular record definitions

Was this page helpful? Yes No Submitting... Thank you

Comments