A lot of new features have been brought to the EnCo CloudEngine since the beginning of 2019. We thought it might be a good moment to pause for a second and quickly summarize all what we have added as well as give you a sneak peek at what’s coming next.
HTTP module : explicit support of OAUTH2 and internal EnCo API calls
Next to basic authentication and Authorization header, the HTTP module now explicitly supports OAUTH2. It is now also possible to make API calls, using the HTTP CloE module, to any EnCo API. You can use your permanent bearer tokens in Authorization headers as well as OAUTH2.
Why might you find this useful?
- Push your IoT data to Google Sheets, like GoodPlanet does
- Use MyThings API in a script to send a downlink message to a LoRaWAN device
- Create a simple monitoring script to check for CloE script execution errors and warn you by email or SMS
- Use our Address AutoComplete or Address Scoring API from within your scripts
Loopback inbound & outbound modules: calling a CloE script from within a script
We make it now possible to call a CloE script from within another script using 2 new inbound and outbound modules. The Loopback outbound module is used to call another CloE script. This module is qualified with user-defined tags and can pass data to the script being called. The Loopback inbound module is the trigger for called scripts. Scripts are triggered based on the associated user-defined tags.
Why might you find this useful?
- You may have a script performing payload decoding, integration to external platforms or specific data conversion used as a “meta function” by your other scripts
CRON inbound module: triggering scripts based on predefined schedules
Using the new CRON inbound module, CloE scripts can be triggered based on predefined schedule(s). The schedule definition is done in the CloE Settings page, using common CRON notation. The CRON inbound endpoint on CloE is then configured with tags corresponding to the name of your defined schedule(s). For instance, a schedule such as “*/5 8-18 * * 1-5” could trigger a script at every 5th minute past every hour from 8 through 18 on every day-of-week from Monday through Friday.
Why might you find this useful?
- Checking log status at predefined moment
- Send accumulated IoT sensor data as a CSV file to an external system
- Trigger a script to poll data via a HTTP GET to an external system – until now CloE scripts could only be triggered based on incoming events
IoT Store module : storing data in csv structures
A 
module that allows you to persist and retrieve multiple value lines from within your scripts (only string values are supported). Multiple values can be stored with the same key and retrieved as a single concatenated string. This allows for example to store CSV lines when data is received and to retrieve them concatenated with line separators as a CSV file.
Why might you find this useful?
- Accumulate IoT sensor data in CSV files
- Manage multiple data and data keys cross scripts
sFTP outbound module
A simple new transport module allowing you to push files – which you can generate with the IoT Store module for instance – onto an SFTP server.
Why might you find this useful?
Integrate IoT data into legacy systems not supporting modern transport protocols such as HTTP or MQTT.
Are you not using CloudEngine yet, but are you interested? Register on proximusapi.enco.io, read our documentation and get started!
________________________________
What’s coming next?
Over the next sprints we intend to bring you the following new capabilities.
- Script Collections : instead of a flat list of scripts in the CloE overview, we will allow you to group scripts into Collections (think of it as “folders”)
- RTCM Inbound module : receive data from Real Time Crowd Management straight into CloE, and leverage its outgoing modules to stream your audience data to even more platforms.
- Microsoft Azure IoT Hub : make it easier to integrate your IoT sensor data flows and device management with the Microsoft’s leading solution.
We have other things considered for our menu but we’ll tell you later about these… Let’s keep a bit of surprise for later. In the meantime, don’t hesitate to share your new feature desires or requirements with us, by dropping a note to enco@proximus.com