This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

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

The status history table for a form


In BMC Remedy AR System 7.0.00 and later, status history tables are optional and are set through form properties, so status history tables are not always available for regular forms.

The status history table contains all the information for the Status History field. Each status history table or view (for join forms) is named with an H followed by the unique ID for the form (for example, H3 ). The ID is the same ID that the main data table or view uses, and the name of each also remains unchanged. Every main data table has an associated status history table. In AR System Data Dictionary: Forms, Fields, VUIs, and Sample Forms, the status history table is labeled Hn.

The most important column in this table is the entryId. It provides a reference to the C1 column of the main data table. (Column C1 is always the Request ID.) This column is followed by a series of one or more column pairs. There is one pair for each state defined for the Status field. The columns are named with a prefix followed by the numeric representation for each state. The prefixes are U for the user name and T for the time the entry was last changed to the corresponding state. The numeric value is zero-indexed. For example, a form with three states for the Status field would yield a table with seven columns: entryId, U0, T0, U1, T1, U2, and T2.

If status values are added, appropriate columns are added to this table to reflect the new states. If states are deleted, the columns are left in the table, enabling the states to be added again in the future. The data for the status values is stored in the database as an integer that relates to the order of the choices. If you add values at the beginning or in the middle of existing values, other values in the list might change.

Unlike in regular forms, for join forms, the Status History field is optional. If it is present, the Status and Status History fields must be from the same base table. If there is no Status History field in the form, the Status History table does not exist. If a Status History field is present, it is defined as an exact duplicate view of the status history table or view of the base form to which it is connected. The only difference is the name of the view. For more information about the Status History field, see Setting form view properties.


View and vendor forms do not have corresponding status history tables.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.