Parsing Symbols Used in the Depends On Field

Fare type variations can be created based on dependencies defined using specific parsing symbols.

For example,For information on how to parse values for different factors, which describes the symbols and parsing options that are available in the Depends On logic of fare type variations.

Table 1. Parsing Symbols Used in the Depends On Field
Field Type Parsing Example
Boolean =,<> =1; <>0
Currency =, <, >, <> <12.50; =500
Numbers =, <, >, <> =22; >0
Date =,<, >, <>, Age(X), MON2FRI, WEEKEND =20040126;>AGE(16);=WEEKEND
Time =, <, >, <>, >< >19:00;><19:00-06:00
String =, <> =Peter; =Peter,John,Andrew
Table 2. Parsing Examples for the Depends On Field
Symbol Description
= Equal to; on strings like Mobaid, you can have more than one ‘equal to’ value. If set to =AM, WH, a Mobaid string containing just one of the values would be considered a match.
< Less than
> Greater than
<> Not equal to
>< Between, used on time fields. For example, >< 19:00-06:00 means from 7:00 P.M. to 6:00 A.M. Both times are inclusive.
Age(X) On date fields such as Date of birth, use this function to allow for dependencies like >Age(16). This means that a client must be more than 16 years old to have this variation.
MON2FRI On date fields, use this to qualify on day types. If set to =MON2FRI, this means that the booking date must be on a Monday, Tuesday, Wednesday, Thursday, or Friday to qualify.
WEEKEND On date fields, use this to qualify on day types. If set to =WEEKEND, this means that the booking date must be on a Saturday or Sunday to qualify.