Description of an attribute on an inbound or outbound message and can be configured on entity type or message type level. If an attribute does not have a description, it will be handled as STRING.
Semantic element for routing rules
Inbound/outbound lookup config.
The max length for any attribute is 300.000 characters after which it will be truncated
Several data types are available for use in ONEiO, below a complete list and usage guidance. These describe how ONEiO will handle the data in these fields.
|Series of characters that are interpreted literally
Data type with two possible values: true or false.
XML character data.
Formatted according to the configured pattern
Any form of attachment data.
An XML fragment is an XML document with no single top-level root element.
JSON fragment is a JSON that does not have an Object or an Array as the root.
Data structure that contains a group of elements.
Only usable for inbound messages as www-form-urlencoded.
You have the possibility to enrich the payload through the use of lookups, available both inbound and outbound. This uses a query to GET information from the target/source system to f.ex retrieve the sys_id when only the name is known. Below is an example from ServiceNow, showing an outbound lookup for the assignment group sys_id.