Product Updates - April 2019

Introduction
Product Updates - April 2019

We used to send product updates via newsletter but now, we will also publish them in our blog so all our work and news will be publicly available.

During this month, we were working on improving our platform instead of focusing on delivering new features (but we have few surprises 😜) as we wanted people to have a better experience using our platform and to easily combine forms with flows. We listened your feedback and here we are with new changes.

Create custom validation flows in your forms

This new section allows you to configure validation flows that will be executed before proceeding to the next form step or before submitting your form.

As an example, we've configured an email verification flow that's executed before proceeding to the second step and verifies if the provided email address is valid or not.

If the user provides a valid email address the flow execution ends with a success status code, otherwise, it goes to the false branch and we return a non success status code with a failure message that will be automatically shown in our form.

This validation flows are specially useful to connect your forms with 3rd party services and create custom registration flows like verifying if an email address is already registered in our database, create a one-time password with an SMS code that users have to provide on the next form step, create a real sign-up form that authenticates the user to your application, etc.

Remember you can also view all your flow executions and check all inputs/outputs/errors of every flow action. This is very useful for debugging purposes.

Launching approval forms  🎉

We are excited to announce that now we are supporting approval forms. You can find this new option in your form editor.

By default, if you enable this option, it creates 3 main form status: Pending, Approved and Rejected. But that's not all, you can add new status based on your business needs (e.g. Require documentation, Signature required...), trigger different integrations flows when your submission goes to a new status (e.g. sending a personalized message when you approve a submission or create a user in your database), define which state goes your submissions by default and last, define which form status are a final state, once you set a form status as a final state, you can't modify it's status again.

After you configure your approval form, you can go to your Submissions tab and start interacting with your submissions.

GDPR & Data storage form settings

We've added this new section on our form builder and now, you can configure if you want to store your submissions in Arengu and also if you want to collect IP addresses of users that submit a form.

If you disable data storage in Arengu, remember to configure an integration flow or enable your form notifications, otherwise, you won't be able to see your form submissions data neither recover it.

Launching modal popup forms  🎉

Some people hate them but others love them. We've decided to support a basic version of modal popup forms, so now you can embed them in your website using our JavaScript SDK and our open source modal library.

You can find your embed code in your Share tab.

Our lightweight modal library is written in pure JavaScript and it has two methods to start using it: the first one is adding data-arengu-modal-form-id attribute to any HTML tag, this will bind a click event on it so when someone clicks it will trigger your modal form. The second one, is calling our show and hide methods that allows you trigger or hide your modal using only JavaScript.

Trigger integration flows after someone submits a form

Many people were asking how they could integrate their forms with 3rd party services. It wasn't actually very clear how to create an integration flow that is triggered when someone submits a form.

Now, we have added Integration & Notifications settings that allows you to easily configure the integration flow that will be executed after someone submits the form directly in your form editor.

Remember that when an integration flow is executed it passes all form fields data through it, so you can use that information to replace it in your different flow actions. Here's an example that sends a Slack notification and subscribes the user to a MailChimp list.

Renamed flow types

When we started with our flows module we had two flow types, synchronous and asynchronous, this was a bit confusing and technical name even it describes it's internal behaviour executing tasks. Now, we renamed them to Validation and Integration flows.

A validation flow executes tasks and hold you up until you receive a response. Meanwhile, integration flows, run tasks in background and you don't have to wait for a response.

Log in using your account to try the new features or schedule a demo for a 1:1 product walkthrough with a product expert to see Arengu in action.

If you have any questions, feedback or just want to say ‘hi’ you can reach out to us any time. We'll really appreciate it!

See you on next product updates! 👋

Author

Jacobo Vidal

Co-Founder @ Arengu. Data & Technology geek. Curious about everything.

View Comments
Next Post

How to develop and implement an AMP form on AMP pages

Previous Post

5 signup form best practices to provide a clear road to conversion