Creating a view for associating records
You can use the Association element in a view definition to design a user interface where you can create or edit associations between the record definitions. The Association element consists of the following modes to design the layout for selecting the record instances while creating or editing associations.
You can add the Association element while creating a view or while editing an existing view definition.
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. For more information, see Customization layer.
To design a view for creating record associations:
- Log in to BMC Helix Innovation Studio and navigate to the Workspace tab.
- Select the application for which you want to create a view.
- From the Palette, drag the Association element to the Record editor component.
In the Properties pane, click the Settings icon, and then specify the properties.
The following table provides information about the properties:
Property Description Record definition to associate
Specify the name of the record definitions for which you want to create the association view.
Association to use Display the list of associations available for the record definition. Association editing mode Select the layout for your association and choose from the following options:
Important: The Dropdown option is available only for associations with cardinality as one-to-one or many-to-one.
Display label Specify the label for the association component. Disabled Specify to disable the record field under specific conditions, such as, at all times or when a specific condition is met. Hidden Specify to hide the record field under specific conditions, such as, at all times or when a specific condition is met. For a View mode, provide the following properties: View for selecting associated records Specify the view for selecting the existing associated records. View for creating associated records Specify the view to create new associations. Show/Hide fields Add the record fields that should be displayed on the view definition for the associated records. For a Dropdown mode, provide the following properties: Field to display Specify the field in the associated record definition whose values should be displayed in the drop-down list. For example, Company Name. Filter by association Filters and displays the associated records at runtime based on the record selected in the related association drop-down list. Record ID Provide the record ID of the record definition that the users must edit. Using Click to build an expression, specify the record ID of the record definition.
- Click Save.
An application uses three record definitions: Ticket, Company, and Support Group. The record definition Ticket is associated to the Company and the Support Group record definitions by using the following associations with the cardinality of the association as many-to-one:
- Ticket to Company (many-to-one)
- Ticket to Support Group (many-to-one)
- Company to Support Group (many-to-many)
The following examples demonstrate how to create both view-based and dropdown-based associations.
Example 1: To create view based associations
The following video demonstrates an example of how to create view based associations. 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:
Example 2: To create drop-down based associations
The following video demonstrates an example of how to create drop-down based associations. 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: