This documentation supports the 19.02 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

Table fields

BMC Remedy AR System server supports the following types of table fields:

These fields can be used by the client and the server. Depending on your needs, you might use the same table field in one context as a server-side table field and in another context as a client-side table field. The choice depends on whether you want to process the information about the client or on the server.

When using table fields, remember this important distinction:

  • Active links work on table fields on the client.
  • Filters work on table fields on the server.

Client-side table fields enable users to view fields and requests from a form in tabular format. The set of requests displayed in a table is the result of a search of the table's source form.

A server-side table field is any table field that appears in server-side workflow in filters or filter guides. You can use server-side table fields with filters to perform calculations on a set of records. For example, you can create filters to find a specific row in a table field (such as the last Entry ID) and then perform actions based on specific criteria. You can also use functions with server-side table fields. For example, you can compute how many records exist for a specified user or for all users.

Use filter guides to read the data in a server-side table. On a server-side table, executing a filter without a filter guide will not return any data.

Data in server-side table fields is read-only.

The most important reason for using server-side table fields is networkperformance. When you perform actions on large amounts of data (for example, Push Fields actions), server-side tables improve performance because they do not use API calls from the client to the server. To lessen network traffic, use filters with server-side table fields instead of client-side table fields in this situation:

  • To communicate from a form in a browser through the mid tier to the server and back through the mid tier to the browser.

Chunk control in table fields

Cell-based tables and list view tables support chunking to return all records while limiting the number of records displayed at one time. The chunk control contains a drop-down menu, navigation buttons, and a results string.

Note

Application developers can remove chunk control from the table header by setting the Next Label and Previous Label properties to an empty string or by setting the chunk size to 0.

Following are the appearance and behavior of the chunk control:

  • The chunk control appears on the left of the table header.
  • The chunk control drop-down menu displays the record number (starting and ending record number of the chunk being displayed), and not the page numbers. For example, when you set the chunk size to 10, and navigate to the second chunk, the chunk control displays 11-20.
  • The Number of Entries Returned property in BMC Remedy Developer Studio is set to {2} of {3} results, by default.
    • When chunking is not enabled, BMC Remedy Mid Tier interprets the parameters and displays both the total number of rows returned and also the maximum number of rows that can be returned.
    • When chunking is enabled, BMC Remedy Mid Tier interprets only the {3} parameter and displays only the maximum number of rows that can be returned.
      You can add an additional parameter {4} to the Number of Entries Returned property. For example: Number of Entries Returned = {2} of {3} results {4}. BMC Remedy Mid Tier interprets the {4} parameter and based on the number of records returned, the value set for the Row label or Row label Plural property appears on the table header.
      • If the table contains only one record, the value set in the Row label property appears on the table header.
      • If the table contains more than one record, the value set in the Row label Plural property appears on the table header.

        Note

        If the number of records in the table is less than the chunk size, the chunking control will not be visible.

  • The number of entries displayed on chunk control is right aligned.
  • The results string that displays the total number of records in all chunks appears on the right of the chunk control.
  • The Page label is removed from the table header.
  • The navigation control to move to the previous chunk and the next chunk always appears with the chunk control.
    • When you have selected the first chunk, the pagination control to navigate to the previous chunk is displayed in the disabled state.
    • When you have selected the last chunk, the pagination control to navigate to the next chunk is displayed in the disabled state.
Was this page helpful? Yes No Submitting... Thank you

Comments