Creating or modifying regular record definitions

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. In the Properties panel, enter a name and description for the record definition. 
6. To define the scope for a record definition, select Scope/Customization options. You can select any of the following options: 
   • (Default) Application/Library—To limit the use of the record definition within the same application or library.
   • Public—To enable 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.
7. (Optional) To automatically export the record data when the library or application is packed in a bundle for deployment, select Should Export Data checkbox. 
8. (Optional) To enable localization for record data, select the Enable Localization checkbox, and after you select the Enable Localization checkbox, make sure you update the following fields: 
   • Data Translation Source Form—Specify the source form that stores the localized values for this record. For example: PCT:ProductCatalog.
   • Data Translation Source Field—Specify the field ID from the form that is set in the Data Translation Source Form property.
   • Data Translation Parent Fields—List the comma-separated field IDs required to translate the value of the current field. For example: 1000000001, 200000003, 200000004.
9. Click Save. 

To add fields to a regular record definition

1. Select the application for which you want to update the record definition.
2. On the Records tab, click the record name that you want to update.

3. Click New field and select the required datatype for the field.

4. 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.

5. 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.

https://youtu.be/-QWpuvC4hNs

 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:

https://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:
   1. For a record:
      • In the Details section, click Edit beside the Permissions field.The Edit Permissions window is displayed.
      • Click Add Permission.
      • From the Type list, select whether you want to provide permission to a specific group or to a specific role.
      • 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.
      • Click Save.
   2. For a specific record field:
      • Select the record field to which you want to add permission.

      • From the Details section, click Edit beside the Permissions field.

        The Edit Permissions window is displayed.

      • Click Add Permission.
      • From the Type list, select whether you want to provide permission to a specific group or to a specific role.
      • 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). 
      • To assign view-only permission, select the View check box or select the Change check box to assign permission to modify the record.
      • Click Save.
2. Save the 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.
   

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.

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.

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.