Function Library

Processing and bitmappers can become quite complex or can be so boilerplate that you do not wish to burden the users in you Tenant with re-coding or copy-pasting the relevant code. An example of a non-trivial transformation is the conversion of JSON to well-formed XML. An example of a boilerplate transformation is the conversion of JSON to YAML.

Your Tenant maintains a library of Functions that encapsulate this reusable code; it may be found in the Functions tab of your Tenant's settings.

Note - all changes made to a Function will be rolled out to the Nodes that use that Function (unaltered) in near real-time.

System Functions

System functions are provided and maintained by EchoStream and always begin with the echo. prefix. For a list of the currently available System Functions, please refer to your Tenant's Functions libary.

Tenant Functions

Sometimes the System Functions simply aren't specific enough for your processing use cases.

For example, you may have a Tenant Message Type that is highly customized and specific JSON, and you wish to transform that to an application specific CSV format. While you could do this directly in the Processor Node, if you may have multiple Processor Nodes that all perform the same (or very similar) transformations, it may make sense to place this code in a Tenant Function.

In this case, you can create a custom Function for you Tenant (requires admin or higher role). Once this new Function is created, all Users in your Tenant can then use it within Processor or Cross Tenant Sending Nodes.