This documentation supports the 21.3 version of BMC Helix Innovation Studio.To view an earlier version, select the version from the Product version menu.

Creating join record definitions

You create a join record definition to combine data that is retrieved from multiple record definitions. The join record definitions are similar to database joins.

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 .

Related topics

Creating-or-modifying-regular-record-definitions

Improving-data-retrieval-performance-by-selecting-a-row-level-security-algorithm


Note

Application business analysts can customize the objects developed in their own 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 like Foundation, Approval, and Assignment cannot be customized in Best Practice Customization mode.

To create a join record definition

  1. Log in to the BMC Helix Innovation Studio and navigate to the Workspace tab. 
  2. Select the application for which you need to create the join record.
  3. On the Records tab, click New and select Join Record.
    The Create New Join Record window appears as shown in the following image:
    Create join record.png

  4. On the Record Definitions tab, specify the properties for the record definition.

    Note

    The Application/Library scoped definitions are marked with an asterisk ( * ).

    The following table provides information about the properties:

    Field

    Description

    Primary record

    The main record for combining the data.

    Secondary record

    The secondary record for combining the data .

    Join type

    The type of join for the record definition. You can select either of the join record types:

    • Inner join—Selects entries only when corresponding values exist in both records.
    • Outer join—Includes all of the entries from the record that you select as primary, even entries for which there are no matching entries in the secondary record.

     

  5. On the Join Criteria tab, specify the expression for joining the records, and click Next.The query for joining the records is restricted to the conditions specified in the expression.
  6. On the Field Selection tab, select the fields from the primary and secondary records that you need to include in the join record, and click Save.
    The following image shows the Field Selection tab:
    Field selection.png
  7. Save the record.

To select a row-level security (RLS) algorithm for join records

  1. Log in to BMC Helix Innovation Studio, navigate to the Workspace tab, and select the application.
  2. On the Records tab, navigate to the record definition to which you want to add RLS algorithm.
  3. In the Security labels section, from RLS algorithm list select the following row-level security (RLS) algorithm option for enhanced row access control:
    • Default
    • RLS Split
    • Combined Likes
    • Subquery
      21310_RLS algorithm for join records.png
  4. Click Save.

Using the Subquery algorithm for Join records

A join record retrieves data from multiple record definitions. To use the Subquery algorithm on join records, you must first set the Subquery algorithm for the primary and secondary records. 

When you enable the Subquery algorithm for a join record, the algorithm waits until the migration (which is the updating of the security table records for the associated parent table records) is complete on the primary and secondary records. If any related records run for a long time or fail, the Subquery algorithm skips the join record, and you might need to run the algorithm once again after the migration is complete. 

consider the following points when you enable the Subquery algorithm on a join record: 

  • Enable the S table for all member records that source the dynamic access fields.
  • Identify the dynamic access fields on the join record.
  • Identify the member records from where the dynamic access fields are coming.