This documentation supports the 25.1 version of BMC Helix ITSM: Service Desk.To view an earlier version, select the version from the Product version menu.

Adding dynamic menu fields to classic Smart IT views


In BMC Helix ITSM, if you are an administrator, you can add one or more dynamic menu fields that have menus associated with them in Mid Tier. You can configure menu fields in classic Smart IT screens, using the Screen Configuration option. These menu fields are dependent menus such as, Owner Support Company, Owner Support Organization, Owner Group, and Owner. Dependent fields are part of the Mid Tier menu qualification. The Smart IT server requires these fields to expand a menu and fetch menu items. Therefore, you must ensure that these fields are available in classic Smart IT.

Using the Populate value with different field option, you can configure a menu that has a different label and value from one another (as part of the Mid Tier menu definition), where the value is stored in another field. You select this option only when a field has a menu associated with it in Mid Tier.

Note

Before adding dynamic menu fields to classic Smart IT, review the prerequisites for adding custom fields to your views using classic Smart IT. See Adding-custom-fields-to-your-views.

The procedure to add menu fields in the Type-specific area of the Asset view slightly differs from the way menu fields are added in other classic Smart IT views. To add fields in the type-specific area, you must select the asset type and subtype, and then add fields. The fields are added only to the selected asset subtype.

Click the following video to view how to add a Owner Group, which is a dynamic menu field, within classic Smart IT views.



icon_play.png https://youtu.be/GNSLWs0-kKc

Click the following video to view how to add a Vendor Group, which is a dynamic menu field, within classic Smart IT views.



icon_play.png https://youtu.be/Zb4RFOJPjWo

To add a single menu field

  1. From the Configuration menu, select Screen Configuration.
  2. In the Configuration window, select an area in a classic Smart IT view. For example, select Record Summary in the Incident view.
  3. Under Available Fields, click the Add (+) icon for a menu field you want to add.
    The menu field is then displayed under Selected Fields.
  4. Expand the CI list to display options and dependent menu fields.
    Std Query Menu Example.gif
    To add the CI field, all dependent fields must be available in classic Smart IT. In this example, the  z1D_Local_DataSetID and Person ID fields are not available in classic Smart IT. The following table provides more information about dependent menu fields marked with Tick mark.gif and Red Triangle icon.gif icons.

    Icon

    Meaning

    Red Triangle icon.gif

    The field is missing from Action Request System forms and hence not configured in classic Smart IT. Hover over the Red Triangle icon.gificon to view the name of the form from which the field is missing. You must add the missing field to the form and make it available in classic Smart IT. For more information, see Adding-custom-fields-to-your-views.

    Tick mark.gif

    A field available in AR System forms, and also configured in classic Smart IT.

  5. The CI menu field has a menu associated with it in Mid Tier. To know which field to select in the text box under Populate value with different field, you must look for the menu definition in the Developer Studio. On the HPD:HelpDesk form, the HPD:CustomerCIwithoutBusinessService menu is associated with the CI menu field. In the HPD:CustomerCIwithoutBusinessService menu, the value field for the CI menu field is ReconciliationIdentity. In Mid Tier, the value of the CI menu field in active link is set to HPD_CI_ReconID menu field.

    CI field in DevStudio.gif
  6. In classic Smart IT, select the Populate value with different field check box and type HPD_CI_ReconID in the text box. 
  7. Add the z1D_Local_DataSetID and Person ID fields to the forms from which they are missing, and make them available in classic Smart IT.
    For more information, see Adding-custom-fields-to-your-views.
  8. Click Save.

Open an incident ticket to view the CI menu field.

To add multiple menu fields to a group

In classic Smart IT, some menu fields depend on other menu fields to get their value. For example, the Owner Group and Owner menu fields depend on the Owner Support Company and Owner Support Organization menu fields.

Best practice
We recommend that you add dependent menu fields in a group. You must create a group to fulfill the validation filters (if any) to save dependent fields together. You can create a group that consists of only the dependent menu fields.

  1. From the Configuration menu, select Screen Configuration.
  2. In the Configuration window, select an area in the classic Smart IT view. For example, select Record Summary in the Incident view.
  3. Under Available Fields, click the Add (+) icon for menu fields you want to add.
    The added menu fields are displayed under Selected Fields. To add the Owner Group and Owner menu fields in classic Smart IT, the Owner Support Company and Owner Support Organization menu fields must be available in classic Smart IT. For example, in the following image  the Owner Support CompanyOwner Support OrganizationOwner Group, and Owner menu fields have been added. The Owner Support Company is not dependent on other menu fields in this group. However, the remaining three menu fields are dependent in the following way:
    • The Owner Support Organization menu field depends on the Owner Support Company menu field.
    • The Owner Group menu field depends on the Owner Support Organization menu field.
    • The Owner menu field depends on the Owner Group menu field.
  4. Click Create Group.

    Multiple Dynamic QMF 1.gif

  5. Drag and place menu fields in their hierarchical order in the Drop Fields Here placeholder.

    Multiple Dynamic QMF 2.gif
  6. The Owner Group menu field has a menu with different label and value field associated with it in Mid Tier.
    To find the associated menu, see To add a single menu field section in . In Mid Tier, the value of the Owner Group menu field in the active link is set to Owner Group ID menu field.
  7. In the Owner Group menu field, select the Populate value with different field check box and enter Owner Group ID in the text box.
  8. The Owner field also requires a menu with different label and value field associated with it. See the To add a single menu field section in  topic to find out the associated menu. The value of Owner menu field in the active link is set to Owner Login ID menu field.
  9. In the Owner menu field, select the Populate value with different field check box and enter Owner Login ID in the text box.
    Multiple Dynamic QMF 3.gif
  10. Click Save.
  11. (Optional) Open an incident ticket to view the group.

Multiple Dynamic QMF 4.png

To add menu fields to an asset subtype

As an administrator, you want to add the Domain field to the computer system subtype of assets. To do so, follow these instructions:

  1. From the Configuration menu, select Screen Configuration.
  2. In the Configuration window, click Type-Specific Area in the Asset view.
    TypeSpecific Asset.jpg
  3. From the list of asset types, select Computer System subtype.
    A list of available fields is displayed.
  4. Under Available Fields, click the Add (+) icon for the Domain field.
  5. The Domain field is displayed under Selected Fields.
  6. (Optional) Expand the Domain list to select additional options such as, Required, Hide Label, and Populate value with different field.
  7. Click Save. 
    A confirmation message is displayed.

Open an asset with computer system as the subtype to verify that the Domain field is added to the Asset view. 

Examples of configuring the default menu fields

The classic Smart IT does not support active links. In such cases, you might need to import workflow (filters, active links) to support menu fields. If there are any active link interactions on these menu fields, you need to replace them using an equivalent filter. If you have configured out-of-the-box menu fields as part of your business needs, then you must create filters using the following examples. Details about such menu fields and filters are available in BMC Communities.

The following is an example of configuring the Vendor Group menu.

BMC Helix ITSM version

18.05 and later

Menu Name

CTM:SGP:VendorSupportGroup-Q

Dependent fields

Vendor Name

Vendor Organization

Note

To edit this group of fields, you must import the !!!HPD:INC:VendorFieldSetForSmartIT filter available in SampleWorkflowQueryMenuFields.zip in BMC Communities. Extract the files and navigate to: Workflows > 81 > Incident > VendorGroup > VendorGroup-Filter.def.

Follow these steps to configure the Vendor Group menu field:

  1. Add dependent fields to the incident interface forms.

    Note

    By default, Vendor Organization is a "Not in view" in Mid Tier. To make it available for configuration in classic Smart IT, you must add it as an In view field in the HPD:Help Desk form.

  2. On the Configuration window, click Refresh metadata for the Incident view. 
  3. Use the Configuration option to add dependent fields as custom fields in the appropriate panel. 
  4. To create or update the Vendor Group menu field, import the .def file that contains the necessary backend filters from the sample workflow document in BMC Communities
  5. Click Save .


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*