In this release we have focused on adding app customisation, and expanding our integration options.
This release will demonstrate the ability to add custom domains to your apps, integrate into TRIM HPE Content Manager and easily extract submission data for cloud storage.
Custom Domains
All OneBlink apps have a URL that can be used to easily access your apps. These URLs are structured as such https://(account name)-(app subdomain)-(environment name).app.oneblink.io.
This structure can cause URLs to become quite long as well as OneBlink branded. To help assist with this we have added easy self-service functionality to use your own custom domains, allowing you to create a short, easily marketable and brand specific URL.
For more on how to start using Custom Domains check out this article
TRIM / HPE Content Manager
Adding to our growing list of integrations, we have added HPE Content Manager. This functionality has come from local council requests to integrate with their TRIM backend systems. This integration can be set up as a submission event allowing you to create custom integrations between your forms and your TRIM instances.
For more on the HPE Content Manager integration check out this article
Submission Extract
While we have focused on ease of integration with the Productivity Suite, we are not able to create console integrations for every system. To help alleviate this we have made it as simple as possible to extract your form submission data from our cloud form storage. This is done by completing a JSON extract which can also be easily converted into a CSV. These 2 formats cover many possible integrations from simple Excel sheets to complicated Analytics tools and databases.
For more on Extracting submission data and how to utilise it check out this article
If you have any questions or require assistance with any of the features in this release please reach out by creating a ticket at https://support.oneblink.io or email support@oneblink.io
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article