... | ... | @@ -37,7 +37,7 @@ For example, say we have a channel with a `json_document` import which expects a |
|
|
"name" : "This is the document name",
|
|
|
"body" : {
|
|
|
"title" : "Document Title",
|
|
|
"body" : "Doc Body"
|
|
|
"message" : "Document Body"
|
|
|
}
|
|
|
}
|
|
|
]
|
... | ... | @@ -53,6 +53,17 @@ It can transformed as : |
|
|
}
|
|
|
```
|
|
|
|
|
|
Or to take the previous email forwarder example :
|
|
|
|
|
|
```
|
|
|
{
|
|
|
"subject" : "[%374d9a1d-cc84-456d-9dad-e1e3065e8c4d#payload[1].body.title%]",
|
|
|
"body_text" : "[%374d9a1d-cc84-456d-9dad-e1e3065e8c4d#payload[1].body.message%]"
|
|
|
}
|
|
|
```
|
|
|
|
|
|
Easy, right?
|
|
|
|
|
|
## Bip metadata exports (_bip|_client)
|
|
|
|
|
|
Additional metadata exports are available depending on the type of Bip that is evaluating. These exports are set in `_bip` and `_client` exports which can be discovered by calling the [`/rpc/describe/bip`](https://github.com/bipio-server/bipio/wiki/Describing-Models) RPC.
|
... | ... | |