A specific type of savings entered by the user, we use these to categorize all the invoice savings records that come into the system. A service belongs to a specific UDID, each valuelogic UDID string has a code attached to it. When we parse the UDID string we get the UDID number and code, which matched it up to a specific service.
| name | data type | type | namespace | min/max occurs | constraints | description |
|---|---|---|---|---|---|---|
| code | string | element | 0/1 | |||
| descriptionUdid | valuelogicUdidInfo | element | 0/1 | |||
| name | string | element | 0/1 | |||
| needsDescription | boolean | element | 1/1 | required boolean | ||
| softSavings | boolean | element | 1/1 | required boolean | ||
| udidInfo | valuelogicUdidInfo | element | 0/1 | |||
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
<valuelogicUdidService>
<name>...</name>
<code>...</code>
<softSavings>...</softSavings>
<udidInfo>
<udidNumbers>
<number>...</number>
</udidNumbers>
<name>...</name>
<travelType>
<travelType>...</travelType>
<code>...</code>
</travelType>
<description>...</description>
<detail>...</detail>
<id>...</id>
<version>...</version>
</udidInfo>
<needsDescription>...</needsDescription>
<descriptionUdid>
<udidNumbers>
<number>...</number>
</udidNumbers>
<name>...</name>
<travelType>
<travelType>...</travelType>
<code>...</code>
</travelType>
<description>...</description>
<detail>...</detail>
<id>...</id>
<version>...</version>
</descriptionUdid>
<id>...</id>
<version>...</version>
<violations/>
</valuelogicUdidService>