<update>

This tag defines the update method of a bet. It is a child of the tag <bet> and it is optional. Maximum one <update> tag can be present in a tag <bet>. When the update condition is verified the bet is updated accordingly with size and price specified. A bet can be updated multiple times if the condition is still verified and the bet is not fully matched. If the condition is verified, but the size and price of the existing bet are the same, no update is performed.

ATTRIBUTES:
condition (string)Sql assertion. When it is true the bet is updated.
price (string)Sql expression returning the update price of the bet. It must return a decimal value from 1.01 to 1000.
size (string)Sql expression returning the update size of the bet. The sign of the value will not effect the bet type; if it is negative it will be converted in positive.
offset_min_price (string)Sql expression returning the minimum offset for the price value. So if the price is lower than the minimum offset it will be adjusted to the value of the minimum offset.
offset_max_price (string)Sql expression returning the maximum offset for the price value. So if the price is greater than the maximum offset it will be adjusted to the value of the maximum offset.
offset_min_size (string)Sql expression returning the minimum offset for the size value. So if the size is lower than the minimum offset it will be adjusted to the value of the minimum offset.
offset_max_size (string)Sql expression returning the maximum offset for the size value. So if the size is greater than the maximum offset it will be adjusted to the value of the maximum offset.
update_interval (string)Sql expression returning an integer. This value represents the minimum number of seconds the strategy will wait between two updates.
close_trade_onmatch (y|n)Specify if the trade must be closed when the current bet is matched. Useful to free slots in strategies that manage multiple trades on same race or same horse.
remove_check_onmatch (y|n)Specify if the check manually applied to the horse must be removed after the bet is matched. Useful, for example, in manual strategies that work in in-play races: removing the check it allows the operator to launch a second trade on the same horse.
clear_custom_1_onmatch (y|n)Specify if the custom values 1, manually inserted for the horse, must be wiped out after the bet is fully matched.
clear_custom_2_onmatch (y|n)Specify if the custom values 2, manually inserted for the horse, must be wiped out after the bet is fully matched.
clear_custom_3_onmatch (y|n)Specify if the custom values 3, manually inserted for the horse, must be wiped out after the bet is fully matched.