A UDID is a record in the GDS that defines a custom information field. This class is mapped in the database to a specific number that corresponds to hard coded values in our GDS scripts. When we import an itinerary, we scan through the invoice for UDID strings, and parse them out. Then we match them up to the UDID information that is stored here to determine what type of savings we are dealing with.
| name | data type | type | namespace | min/max occurs | constraints | description |
|---|---|---|---|---|---|---|
| description | boolean | element | 1/1 | required boolean | ||
| detail | boolean | element | 1/1 | required boolean | ||
| name | string | element | 0/1 | |||
| travelType | clientTravelType | element | 0/1 | |||
| udidNumbers | list of valuelogicUdidNumber | element | 0/unbounded | |||
Properties inherited from baseHibernateEntity |
||||||
| id | long | element | 0/1 | The unique internal ID of the object. | ||
| version | long | element | 0/1 | For internal use only. This is the serialization recorder for optimistic locking of several objects between sessions. | ||
Properties inherited from baseEntity |
||||||
| violations | list of simpleViolation | element | 0/unbounded | A list of constraint violations, if any, that this object has. | ||
Example
<valuelogicUdidInfo>
<udidNumbers>
<number>...</number>
<id>...</id>
<version>...</version>
</udidNumbers>
<name>...</name>
<travelType>
<travelType>...</travelType>
<code>...</code>
<id>...</id>
<version>...</version>
</travelType>
<description>...</description>
<detail>...</detail>
<id>...</id>
<version>...</version>
<violations/>
</valuelogicUdidInfo>