Rules for defining terms and conditions

Some rules for defining terms and conditions are as follows:

• You must limit the Terms and Conditions statement to 32k when you build a service target. Otherwise, the statement will be truncated and your service target will not build.

  Important

  If you are running an environment with double-byte characters, the AR Server could determine that your Terms and Conditions should be less than 32k as the maximum size.

  When you create an SVT by using a locale other than English, ensure that you do not use the localized Terms and Conditions statement.

• You must enter double quotes for strings. Do not include double quotes for integer fields.
• Do not include special characters or carriage returns.
• Do not use fields that change during the life cycle of the request, for example the Status field.
• Do not use the transaction (TR) value in the field because this value will not be true the next time the request is modified.
• Do not use Display Only fields because these fields might not be loaded when the filter processing starts.
• Do not use the Assignee Group field (ID 112) when setting your terms and conditions because this field is used for assigning permissions and the assignee group is stored as a number.

The values that you define in the qualification should match the values in the application form, or View form in the case of compliance-only service targets. For example, in the BMC SLM Sample Application, acceptable values for Priority include Low, Medium, High, and Urgent.