t_Message_Parts_Value

Value : Message Part

A value (or primitive) message part.

Description A value message part is also known as a primitive message part. It has a primitive type, such as string, integer, date, ... It shares it's format type with the message's root part but it has its own mapping that defines how it is marshalled between internal and external format. Values cannot have child message parts. Properties

description : string

Message description.

maxCount : nonNegativeInt

Maximum count of occurrences of this part (0 for unlimited).

Valid values based on“int”.
0 (minInclusive)

minCount : nonNegativeInt

Minimum count of occurences of this part.

Valid values based on“int”.
0 (minInclusive)

name : messagePartIdentifier

Part name, unique within the parent part.

Valid values based on“string”.
:?[\p{L}_][\p{L}\p{N}\.\-_](:[\p{L}_][\p{L}\p{N}\.\-_])*	Value must begin with a letter, colon, or an underscore. Case and length are not restricted. Letters, numbers, underscores, dashes, colons and periods are allowed. Spaces and other punctuation characters are not allowed.

type : primitiveType

Value part type.

Valid values based on“string”.
string	Sequences of characters that represent text. String values are surrounded by double quotation marks. For example, the value "Hello World!" is a string. Strings may contain letters, numbers, and symbols. The symbols " and \ are special characters that cannot be written directly in a string. If you want to write a double quotation mark in a string, use the token \". If you want to write a backslash in a string, use the token \\.
binary	Binary data of arbitrary length.
integer	Whole numbers that do not include a decimal place. For example, the value 2 is an integer, while 2.0 is not.
long	Values that represent a 64-bit integer. Longs can be used to store numeric values that are too large to be stored in an integer data type.
decimal	Numeric values that contain decimal fractions.
currency	Numeric values that represent a monetary value. Currency data types are persisted as decimals.
float	Values that represent a single-precision 32-bit floating-point number. They can be either whole numbers or numbers that contain a fractional component. For example, the values 2.0 and 2.1 are both floats.
double	Values that represent a double-precision 64-bit floating-point number. Doubles can be used to store numbers that are too small or large to be stored in a float.
percentage	Values that represent a percentage. Percentage data types values are persisted as doubles. In the user interface, percentage data type values are formatted as percent when a field or label is bound to the attribute.
timestamp	Values that represent a specific date and time. Timestamp values differ from date values in that they include a time component and can be mapped to time zones other than UTC.
date	Values that represent a calendar date. Date values cannot include a specific time value and persist at 0 hour UTC.
boolean	Either true or false. Boolean values are typically the result of logical expressions. For example, the expression 5 < 10 returns the Boolean value #t, and the expression 5 > 10 returns the Boolean value #f.
any	Any type of data.

Content

Sequence of:
- t_Message_Parts_Value_Enumerations [0..1] - Value message parts may have enumerations defining a list of values that the part can take.
Sequence of:
- Choice of:
  - t_BaseMessage_ObjectMapping [1..1] - Maps message parts to attributes in class instances.
  - t_BaseMessage_FixedMapping [1..1] - Maps message parts to record fields in a fixed length file, or flat file database.
  - t_BaseMessage_JSONMapping [1..1] - Maps message parts to JSON objects, arrays or primitives.
  - t_BaseMessage_AvroMapping [1..1] - Maps message parts to Avro objects, arrays or primitives.
  - t_BaseMessage_HL7Mapping [1..1] - Maps message parts to segments and fields in a Health Level Seven (HL7), v2.x file.
  - t_BaseMessage_CSVMapping [1..1] - Maps message parts to columns in a CSV file.
  - t_BaseMessage_XMLMapping [1..1] - Maps message parts to XML elements, attributes or values.
  - t_BaseMessage_ZipMapping [1..1] - Maps message parts to files in a Zip file archive.
  - t_BaseMessage_VCardMapping [1..1] - Maps message parts to elements in a vCard file.
  - t_BaseMessage_Mapping [1..1]

Parents

t_Message_Parts - A message is represented internally (in canonical form) as a tree of parts.

t_Message_Parts_Value_Enumerations
Value message parts may have enumerations defining a list of values that the part can take.
t_BaseMessage_ObjectMapping
Maps message parts to attributes in class instances.
t_BaseMessage_FixedMapping
Maps message parts to record fields in a fixed length file, or flat file database.
t_BaseMessage_JSONMapping
Maps message parts to JSON objects, arrays or primitives.
t_BaseMessage_AvroMapping
Maps message parts to Avro objects, arrays or primitives.
t_BaseMessage_HL7Mapping
Maps message parts to segments and fields in a Health Level Seven (HL7), v2.x file.
t_BaseMessage_CSVMapping
Maps message parts to columns in a CSV file.
t_BaseMessage_XMLMapping
Maps message parts to XML elements, attributes or values.
t_BaseMessage_ZipMapping
Maps message parts to files in a Zip file archive.
t_BaseMessage_VCardMapping
Maps message parts to elements in a vCard file.
t_BaseMessage_Mapping

Parent topic: t_Message_Parts