News & Updates
October 25, 2020
May 11, 2021
News & Updates
October 25, 2020
May 11, 2021
April has brought important news to further personalize your flows: new functions for data hashing, internal SDK methods to build custom interactions, wildcards when verifying email addresses and the possibility of recalling variables from flows in your forms.
These features open up a huge range of options in terms of customization and data sharing between forms and flows. Keep reading!
Now you can use and reference custom state variables anywhere, also in forms, opening up almost endless possibilities.
For example, you can use them to configure field settings in dynamic pricing use cases, or to pre-fill form fields with data from external services like Clearbit or your own API.
Just add the ‘Store state variable’ action to your flow and define in it the ID of each custom variable and which output it corresponds to. Then you will simply have to reference the proper {{state.variableId}} wherever you need it.
We have added the md5(string), sha1(string), sha256(string) and sha512(string) functions to hash data in flows using the MD5, SHA1, SHA256 and SHA512 algorithms.
In addition, we have included the toTimestamp() function to return the current UNIX timestamp and toTimestamp(date) to parse the provided date to timestamp. The latter supports date in ISO8601/RFC3339 (eg. 2021-04-30T10:02:50.876Z) and RFC1123/RFC2822 (eg. Fri, 30 Apr 2021 10:03:47 GMT).
Block and allow all emails and subdomains of a domain using wildcards in the ‘Verify email’ action, placing an asterisk before the domain to configure this option. We have added +80,000 domains to our database of disposable and free email domains.
Build custom interactions with the form via JavaScript thanks to the new $form method. Pass variables to the hidden fields or include them in the HTML blocks with it. It is automatically available only in the inline <script> that you include in the HTML blocks.
You can also use the new $root method to search HTML elements in the form. Simply use $root.querySelector('#card-verifier') instead of the standard document.querySelector('#card-verifier'). This will allow you to find HTML elements in the current form, regardless of whether it is embedded in several places or there are other elements that fit the query.
Do you want to learn more? Stay tuned for related tutorials to come!