The following conventions apply to keyword input formatting:
Prefix every keyword (including PROPERTY) with a percent (%) sign. The percent sign must be in column position one. If the first nonempty line of the input does not have a percent sign at the start of the line, either %DESCRIPTION= or %LOG= is used as the prefix for the incoming data, depending on whether a ticket ID artifact or keyword was found. If %DESCRIPTION is set, the contents of the message up to the first Keyword is posted as a ticket description. If %LOG= is set, the contents of the message up to the first Keyword is posted as a log comment.
Do not use any intervening spaces within the keyword between the percent sign and the keyword, or between the keyword and the equal (=) sign.
Do not quote values; all data after the equal sign is assumed to be the value.
Keywords are not case sensitive.
If the input includes duplicate keywords, the last keyword is used; otherwise, the order in which you specify the keyword/value pairs is unimportant.
Specify keyword values as you would for the corresponding field in the web interface. For example, to specify an Analyst contact type, you use %CONTACT_TYPE=Analyst, even though in the database this value is stored as an integer. The CONTACT_TYPE keyword is defined in text_api.cfg so that it converts the specified value to match the stored value.
Note: Whether the value is case sensitive depends on your underlying DBMS.
