Object Structure Element
Additional Considerations
Boolean columns
Encrypted fields
Character encoding
Date format
Null columns
Number format
76
In inbound transactions, a tag that represents a boolean field must contain a value
of 0 (false) or 1 (true). If the tag does not contain a 0 or a 1, the object generates an
error. If the XML does not include a tag for a boolean field, the object updates the
corresponding database value with the default value (0 or 1) that is defined for
that column.
In inbound transactions, the attribute that represents the maxencrypted field
must contain a value of 0 (false) or 1 (true). When the attribute value is 1 the
system applies a decryption process to the received data. When the attribute
value is 0 the system does not decrypt the received data.
If the attribute does not contain a 0 or a 1, the system does not decrypt the
received data. If the XML field does not include a tag for an encrypted field, the
system does not decrypt the received data.
The integration XML uses UTF-8 encoding. If an inbound transaction specifies
any other encoding, the entire message must use that encoding. If an error is
encountered during the processing of an inbound transaction that uses encoding
other than UTF-8, the entire error XML that is written is encoded as UTF-8.
<?xml version="1.0" encoding="ISO-8859-2"?>
The integration XML supports the following ISO 8601 date format.
2004-12-06T10:11:58-05:00
If a tag in an inbound transaction contains no value, the processing logic updates
the corresponding database column with a null value. If the XML does not
include a tag for a particular field, the processing logic does not update that field
in the database.
Regardless of the locale setting of the application server or the database, all
decimal fields must use a period (.) as the decimal placeholder. Do not format
numbers to the left of the placeholder. This format applies to inbound and
outbound data.
$1,738,593.64 must be in the following format: 1738593.64
Integration Guide