Using the Request ID to improve performance or security

This section contains information about using the Request ID to improve the performance or enhance the security of your BMC Remedy AR System environment:

• Working with the Request ID field
• Changing the next available ID for new requests
• Changing the Request ID field length or prefix
• Preserving Request ID field values
• Changing Request ID field values to a new format
• Updating the Request ID field in other AR System tables

Every form defined in BMC Remedy AR System contains a set of core fields. The Request ID core field has a unique field ID of 1. You can change the field's label to something other than "Request ID," but the field ID is always 1.

The Request ID field contains a character string that holds a unique index for each request. The form of this string is an optional prefix, which can consist of any alphanumeric characters, followed by a 0-padded numeral (for example, HD0000000000001 ). The length of the Request ID field must be either 1 or between 5 and 15 characters, inclusive. Specifying a length of 1 causes leading zeroes to be stripped from the value in the Request ID. The prefix can be as long as the total length of the field less five characters.

When new requests are submitted, BMC Remedy AR System generates a new ID for the request by appending the next available ID to the prefix, if a prefix is specified.

The Request ID field contains a unique number sequence. Create other fields to contain information specific to your site instead of using the Request ID field. Overloading the Request ID field with other information can restrict your control of this data and can limit the flexibility of searches on the data.