Docs.bmc.com will undergo a brief maintenance outage 27 March 2025. The site will be unavailable for ten minutes starting at 6:30 AM CDT/5 PM IST.

Creating or modifying regular record definitions


A regular record definition is an entity that stores your business process information. For example, if you have a process to onboard new hires, you will need information such as the first name, last name, and ID of the employee. A regular record definition stores these details for your business process.

You can create a new record definition or copy and customize an existing record definition. 

Before you begin

Make sure 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.

Important

Application business analysts can customize the objects developed in their applications and that are marked customizable by the administrator, but cannot customize the objects developed in com.bmc.arsys in Best Practice Customization mode. For example, objects in core BMC applications such as, Foundation, Approval, and Assignment cannot be customized in Best Practice Customization mode. For more information, see Customization-layer.

To create a regular record definition

  1. Log in to BMC Helix Innovation Studio and navigate to the Workspace tab.
  2. Select the application or library where you want to create a record definition.
  3. Click Records.
  4. Select New > Regular record.
  5. Click New field and select the required datatype for the field.
  6. In the Details section, enter the field name and provide the following additional details:

    Field

    Description

    Name

    Enter the name of the record field.

    Important: Make sure that the name of any field is not the same as the ID of any other field in the same record definition. If the field name is the same as the field ID, and this record definition is used in any process, it causes the process execution to fail. 

    Description

    Provide the description for the record field.

    Required

    Select to mark the field as required for the record definition.

    Allow anyone to submit

    Select to allow any user to submit new requests.

    Important

    When you add a text field, you must provide the field length in characters and not in bytes. The default length is 254 characters.

    Text fields with more than 1000 characters in a record definition are converted into a Character Large Object (CLOB) field after saving the record definition for Oracle.

    In BMC Helix Innovation Studio, all field lengths for record definitions have the same magnitude but with character units instead of byte units, except for the following fields which remain byte semantics:


      • 1 = field ID CORE_ENTRY_ID
      • 179 = GUID
      • 379 = RECORD_ID

    Field ID range specifies the limit for values that you can assign (or is assigned automatically if you do not assign any value) to the Field ID. You can assign the value to Field ID within the Field ID range. You cannot assign the lower limit value of the Field ID Range to a field. For example, if Field ID Range is 1000:2000, the minimum value that you can assign to a Field ID is 1001. 

    To resolve the issue of the field ID not within the specified range

    If you create a new field whose ID is not in the range defined in Field ID Range, the new field is still created with a warning message:

    WARNING (471): Field ID given by the user is not within the specified range.

    To resolve this issue, delete the field and create a new field whose field ID is within the range specified in Field ID Range.

  7. Click Save

The following video helps you to create a record definition.

The video shows an older version of 

BMC Helix Innovation Studio

. The previous product name was BMC Helix Innovation Suite. Although there might be minor changes in the UI, the overall functionality remains the same.

icon-play.pnghttps://youtu.be/-QWpuvC4hNs

Copying a record definition

You can copy the record definitions within an application or to a different application or library. By copying the record definition, you can reuse the record definition in multiple applications without having to create a new record definition. 

The Copy option does not apply to the following record definitions:

  • External record definition mapped to event statistics 
  • Audit record definition type, which gets automatically created when the main record is copied

Important

  • Before you copy the record definition, make sure the definition scope for the referenced objects like base or inherited record definition is public.
  • You can view and select only those applications or libraries that you can access.
  • Make sure you do not change the name of the record definition if you are also copying the rule that uses this record definition.

The following image describes how the objects are referenced after you copy the record to the target application or library:

22_1_copy_record.png

To copy a record definition

  1. Log in to BMC Helix Innovation Studio and navigate to the Workspace tab.
  2. Select the application or library from which you want to copy the record.
  3. Click Records, select the record definition that you want to copy, and click Copy.
  4. In the Copy definition dialog box, enter the following details:

    • From Target application/library, select the target application or library where you want to copy the record.
    • In the Definition name field, type a name for the record definition. 

    22_1_Copy record definition.png

    The copied record is saved in the target application.

To update the existing fields in the record definition

  1. Select the field in the record definition.
  2. In the Details section, modify the field details.
  3. Save the changes. 

To add permissions to a record definition

The following video describes the procedure to add permissions to access a record definition or a view definition:

icon-play.pnghttps://youtu.be/y0UEfO4PKJU

By default, a record definition is visible only to the administrator users. To make a record available for other users, you must provide the permissions to a specific group or a role to access the record. You can also restrict any field in a record by updating the permissions to the record field.

  1. Perform the following steps to add permission:

    • For a record:


      1. In the Details section, click Edit beside the Permissions field.The Edit Permissions window is displayed.
      2. Click Add Permission.
      3. From the Type list, select whether you want to provide permission to a specific group or to a specific role.
      4. From the Group (or Role) list, select the group to which you want to provide permission.The field will be displayed only to those users who belong to that group or role.
      5. Click Save.

    • For a specific record field:


      1. Select the record field to which you want to add permission.
      2. From the Details section, click Edit beside the Permissions field.

        The Edit Permissions window is displayed.

      3. Click Add Permission.
      4. From the Type list, select whether you want to provide permission to a specific group or to a specific role.
      5. From the Group (or Role) list, select the group to which you want to provide permission.The field will be displayed only to those users who belong to that group (or role). 
      6. To assign view-only permission, select the View check box or select the Change check box to assign permission to modify the record.
      7. Click Save.
  1. Save the record definition.

Important

Make sure you do not delete the permissions of a customizable record definition.

To add indexes for record definitions

  1. In the Indexes section, click Add Index.
  2. Perform one of the following steps:
    • To enable each index to return only a unique search result, select the Each index to resolve a unique result check box.
    • To define a unique index and allow Null values in multiple records, select Ignore blank values check box.
      Important: This check box is applicable only for the Microsoft SQL Server.
  3. From the Available Fields list, select the fields that you want to index and then click the Move side button.
  4. To arrange the fields in decreasing priority order, use the Move Up or Move Down buttons and click Save.
     If a composite index exists on fields F1 and F2, the records are sorted first by F1 and then by F2.
    22_1_add index.png

By default, a record contains an index for the GUID field and you cannot modify or delete the index. You can modify the indexes for the other fields.

Important

Make sure you do not delete the indexes of a customizable record definition.

To define the scope for a record definition

  1. In the Details section, click Scope/Customization Options.
  2. From Definition Scope, select the scope for a record definition.
    You can select any of the following options: 
    • Application/Library (default)—Limits the use of the record definition within the same application or library. 
    • Public—Enables the record definition to be used by all the applications or libraries. Additionally, users can customize the record definition properties, such as fields, permissions, and search indexes.
  3. To enable users to customize the record definition, perform the following tasks:
    1. From the Customization Options area, select the Allow future customization to this record definition check box. 
    2. In the Allow future customizations to: section, select whether you want to enable users to customize the record definition's properties, fields, permissions, or search indexes.
    3. From the list of available record definition fields, select whether you want to enable users to customize the field's properties or permissions or both.
  4. Click Save.

To export record data with a bundle

You can automatically export the record data when the library or application is packed in a bundle for deployment.

  1. Log in to BMC Helix Innovation Studio and navigate to the Workspace tab. 
  2. Select the application for which you want to export record data.
  3. On the Records tab, click the record name you want to use.
  4. In the Details section, click Edit Edit icon.png.
  5. Select the Should Export Data check box.

To associate and display field values for record definitions

Associate fields to record definitions, so that during runtime, the associated field values are displayed instead of GUID values. This configuration enables you to make the record definitions readable, as it is difficult to read and understand the information just from the GUID values.

To associate fields with record definitions, perform the following steps:

  1. Select the record definition.The record definition details are displayed.
  2. In the Display Value section, click the Associated Display Value list and select the field that you want to associate with the record definition.

Important

You can configure only a direct association between the record definitions. For more information about direct associations for record definitions, see Creating-record-associations.

If you do not associate any field value for a record definition, the record definition displays GUID values for the field. For example, in an Approval application, the Leave Request record definition displays the Requester as GUID value AGGAA5V0FMWPEAOZPNJAOYTJICQIRY.

If you associate field value with a record definition, the record definition displays the associated field value and not the GUID value. For example, in an Approval application, the Leave Request record definition displays the Requester as Britney.

To copy fields in a record definition

You can copy custom fields from a regular record to the same record.

You cannot copy the following fields and record definitions:

  • Core fields
  • Inherited fields
  • Join records
  • Audit records 

The following properties of the field are not copied:

  • id
  • name
  • customId
  • developerId
  • lastChangedBy
  • lastUpdateTime
  • optionLabelsById
  • overlayDescriptor
  • overlayGroupId
  • owner
  • version

To copy fields from a record:

  1. Log in to BMC Helix Innovation Studio, navigate to the Workspace tab, and select the application.
  2. On the Records tab, click the Regular type record name in which you want to copy fields. 
  3. Select the custom field on the record definition that you want to copy. 
  4. Select Copy. 

    Important

    The Copy button is enabled when you select one custom field.

    The Copy button is disabled if you select multiple custom fields or core fields.

    A copy of the selected field is created as Copy of <selected field name>.

For example, you have a record definition that has a field Official email address. You want to add another field for an alternate email address. You can copy the Official email address field and rename it to Alternate email address.