This documentation supports the 22.1 version of BMC Helix ITSM.To view an earlier version, select the version from the Product version menu.

Customized table columns

Table fields enable users to view specific fields and requests from another supporting form or from the original form in a spreadsheet format.

You can add data from a form that is referenced from a table field. You might want to do this to enable the data to be seen in the table, or to use the data in your workflow. Each column title in the table field represents a field from the supporting form, and each row represents an entry from the supporting form.

If new entries are made to the supporting form, the user sees them when the table is refreshed. For more information, see  Defining tables to display data. 

In order to customize table columns, you must create overlays of the AR System form and view that the table fields reside on.

When adding columns, remember that these columns have field IDs and must be added by using the field ID recommendations. Also, follow the naming conventions discussed in User-interface-object-designs to avoid conflicts with column names added by BMC.

  • If you want to make the data visible to the end user, ensure that the table column is visible and in a position that makes sense for users to see.
  • If you are leveraging this data for workflow, ensure that the table columns are hidden.

Best practice
The most efficient way to retrieve data from a table is to include it in the table field and not build additional workflow to obtain the field. This practice is important in tooltips. Use hidden table columns to show data in a tooltip because they reduce the calls back to the system to retrieve record data that you are already displaying.

 

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