Today we are introducing a two-way data flow for YOOtheme Pro Dynamic Content, a breakthrough that allows for the incoming form submission data to be mapped to a source with the same convenience outgoing data can be mapped to a layout. And to best illustrate it, we are introducing as well the long-awaited SaveToDatabase action.
Our YOOtheme Pro Form Builder doesn't assume much about the workflow, we try instead to give you full control over what should happen after a form has been successfully submitted. We do so using After Submit Actions, and we wondered if we could use YOOtheme Pro Dynamic Content the other way around to improve the actions workflow. We let the idea mature while learning more with each new addon, and with the recent release of Dynamic Addon and its ability to resolve sources in more versatile ways, we finally got our answer. It turns out, yes, we can!
Hooking into the Dynamic Content workflow we are able to set a form submission as a source and use it to map its data as any other dynamic content. Finally, we had all the tools in place to release a proper SaveToDatabase action!
The new action allows you to choose an existing database table in any of the databases you have access to and save a new record using any submitted data, any dynamic content or even fixed values. But we went ahead and refactored all “save to” actions to support Dynamic Content and introduced the ability to enrich the submission with contextual data or alter it before being saved. You can now add the date & time of the submission, the current page URL or any other information your submission needs!
Executing an action based on dynamic conditions was already possible, but with the submission as a source interesting workflows are doable. You can execute an action based on the submitted data, for example send an email only if a certain checkbox has been marked.
Some actions would be more suitable with a dynamic configuration, for example, an Email Action subject could be set as the current page title: this is now possible for most configuration fields.
Submission data placeholders are still being supported as those are necessary when multiple data is mapped to the same field. But now it is even easier to use them by simply selecting the placeholder from a dropdown list, which will copy the content to the clipboard allowing you to paste it into the field as required.
With the submission as a source and the SaveToDatabase action combined with a Database Source more advanced workflows are now possible. We are excited to get your feedback on this release so let us know what you think in the comments below.
Additions worth mentioning from Essentials v1.7 last releases.