This form will allow you to add a levels definition.

^errormsg^

Code A very short identifier for use with queue. (no space, no special character, max of 16 characters) Name The name of level for identification. Detail The detailed description of the level definition. Options ^options^ Level specific options. This is similar to Flow Management Options.
Format:
{PRECONDITION}{COMMAND}
{COMMAND} Format:
<TYPE>[<FIELD>]=<AOP><VALUE>,<OPTION>
Where:
<TYPE> - type of command
• A to change the value of the Level Rate
• F to change the value of a field on cdb
<FIELD> - is an optional variable only used with type F.
<AOP> - the arithmetic operation to use
• A for addition
• S for subtraction
• M for multiplication
• D for division
<VALUE> - the value to modify the original Level Rate in case of type A or field value in case of type F.
<OPTION> - used by type A,
• F to modify the fixed value of level rate
• P to modify the percentage value of level rate
Examples:
{seqCBTEST=checked}A=S5,F
CBTEST is a field name, the command is executed only if CBTEST has a string value of 'checked'
the command to execute is A=S5,F which will subtract 5 to the fixed value portion of the level rate
A means perform arithmetic operation on the level rate value.

{seqCBTEST=checked}A=A10,P
this will add 10 to the percentage value portion of the level rate

{seqCBTEST=checked}FNUMTEST=A5
F means perform operation on the field. In this case, NUMTEST is the field name. The command will add 5 to the existing value of NUMTEST field.
NOTE! Field values are stored in pure integer (for performance purposes), UI interprets 1000 as 1 and 500 as 0.5. In this example, if NUMTEST field does not contain any value, and the command A5 is used, it will store 5 on NUMTEST field but will be interpreted as 0.005. It is up to the admin to multiply the values by 1000 to adjust the values. Example, FNUMTEST=A5123 will add 5123 to the field NUMTEST but is interpreted as 5.123.