Attribute Descriptions
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.
| Field | Description |
|---|---|
| Name | Attribute name. |
| Data Type |
Attribute datatype |
| Integration Element |
Semantic element for routing rules |
| Lookup |
Inbound/outbound lookup config. |
Note
The max length for any attribute is 300.000 characters after which it will be truncated
Datatypes
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.
| Datatype | Usage |
|---|---|
| STRING | Series of characters that are interpreted literally |
| NUMBER | Number string |
| BOOLEAN |
Data type with two possible values: true or false. |
| CDATA |
XML character data. |
| DATE |
Formatted according to the configured pattern |
| ATTACHMENT |
Any form of attachment data. |
| XML_FRAGMENT |
An XML fragment is an XML document with no single top-level root element. |
| JSON_FRAGMENT |
JSON fragment is a JSON that does not have an Object or an Array as the root. |
| ARRAY |
Data structure that contains a group of elements. |
| JSON_EMBEDDED |
Only usable for inbound messages as www-form-urlencoded. There, one or more form fields can contain embedded JSON.
|
Lookups
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.
Comments
Please sign in to leave a comment.