Input to Output Mapper
[ | version 3.0]
Connector
The connector is permitted for use of the platform background agent.
Connector processing type: Row by row!
Allows to map input data structure to output data structure.
See attached Examples for your inspiration how to use this connector
Input to Ouput Mapping configuration
Mapping
Mapping between input data structure and output data structure. Input data can be reffered by using placehoders, ie. ${input.ObjectID} will be replaced by value in ObjectID property.
Example
Input schema
{
"ObjectID": 125,
"ObjectName": "Testing object",
"ObjectJson":
{
"ID": 125,
"Name": "Testing object",
"CreationDate": "2023-03-13T09:16:47.780"
},
"ObjectContent": "VGVzdGluZyBvYmplY3QgY29udGVudA=="
}
| Mapping value | Output value | Description |
|---|---|---|
${input.ObjectID} |
125 |
Value from input schema on property ObjectID |
id155 |
id155 |
Fixed value id155 |
${input.ObjectID} - ${input.ObjectName} |
125 - Testing object |
Concatenation of input schema properties ObjectID and ObjectName |
Warning
Mapping values will be processed according to output schema properties order
Input & Output Schema
Input
Input schema is mandatory but not strictly defined.
Example
| Column | Data type | Allow null | Description |
|---|---|---|---|
| Text | string |
Yes | String value |
| Number | integer |
No | Number value |
| Date | DateTime |
No | DateTime value |
| JSON | JSON |
Yes | JSON value |
| Base64 | Base64 |
No | Base64 value |
Output
Output schema is mandatory but not strictly defined.
Example
| Column | Data type | Allow null | Description |
|---|---|---|---|
| Name | string |
Yes | String value |
| JsonDescription | JSON |
Yes | JSON value |
| Content | Base64 |
Yes | Base64 value |
Release notes
3.0.5
- Plugin binaries update as a result of included connector change.
3.0.4
- Fixed processing input mappings to output values.
3.0.3
- Fixed shared nuget package versions.
3.0.2
- Fixed right processing of nullable properties.