We shipped a major upgrade to our Connector subsystem over the weekend that will provide major benefits going forward.
For starters, the logs of each connector action are now available for viewing against Form entries.
We’ve been running a “single sign-on” approach on our support portal for a while now and have found that it’s proven more challenging than expected, particularly due to your ability to “log in as” other client accounts and users on our platform.
For a long time, we’ve wanted to provide notifications inside the secure website.
We’ve also seen Data exports as a poor user experience due to waiting for the output to generate.
So we decided to kill two birds with one stone – introducing new Notifications and background exporting functions!
A small update has been released for all apps, containing minor fixes and a file upload improvement.
We’ve enhanced the dynamic placeholder functionality for Connectors, adding support for the full range of placeholder syntax directly in Connector configuration fields
We’re always looking to make our integration API as accessible and easy to understand as possible for developers.
To date this has been achieved by having detailed documentation on each API endpoint and option, but today we’ve released a new way to discover and understand our APIs – introducing the API Explorer!
We’ve begun submitting new app updates for Android and iOS for all customers.
This release contains a number of bug fixes and minor improvements that are worth checking out.
We’ve added support for two new built-in placeholders that give you more flexibility when creating data templates for use across multiple clients.
After months of stop-start work on the Tasking area, we’re excited to announce that Task Templates are now live.
Templates bring a number of new, highly demanded features to Tasking including the ability to preset fields on Tasks created from Templates.
Bottom line: If you use Tasks, you will want to check out Task Templates right away!
Basic workflows in Form screens have always been possible through our Form Task field type.
Over time though, it became clear that Form Tasks were simply too limited for many scenarios.
So we went back to the drawing board in December, and built a more powerful replacement – the Process Step field type.