When using the embedded form for data collection I would like to enable the user to continue working on the same form (record) after logging out and back in again. I need some kind of search function or way for the user to find what record he/she was previously working on, because each form is complex and needs a lot of time to complete. Is this possible?
Hi there,
That is a great question. When dealing with complex forms that require significant time to complete, the ability to “save and return” is indeed a crucial part of a smooth user experience.
To help clarify why the current Web Embed works the way it does, it’s helpful to look at the design logic behind our two primary embedding options:
1. Standard Web Embeds (Database Query, Viewer, and Form)
Our standard web embed tools are designed for specific, streamlined tasks.
- For example, the Form Embed is built specifically for one-way data collection (creating a new record). Think of it as a survey-style interface: once the “Submit” button is pressed, the transaction is complete from the perspective of a visitor.
- Because this tool intended for simple data entry, they currently do not support retrieving or editing existing records by design.
- As for the Database Query and Viewer modes, they also do not support editing existing records.
2. The “Direct Embed” Alternative
If your users need the full Ragic experience—including searching for previous entries and continuing their work—the most effective approach is the “Raw embed” option. This essentially places the full Ragic interface into your website via an iframe. In this mode, users can log in and manage their records with the same tools they would have on the Ragic platform directly.
Design Philosophy: Respondent vs. Editor
The reason we maintain this distinction is rooted in how we categorize user needs:
- The Casual Respondent: Someone providing data once (like a feedback form). They benefit from a minimalist, distraction-free interface because they don’t need to see the rest of the database.
- The Active Editor (Collaborator): Someone managing complex data over time. We’ve found that for “complex forms” like yours, users often rely on the “Professional Toolkit” found in our standard interface—such as Data Filtering to find their records, Version History, and Action Buttons (for sending emails or updating values with predefined rules).
Looking Ahead
While our current “Database Form Mode” is focused on new data collection, we are always interested in how our users interact with these tools.
If you find that the Raw Embed (the full interface) isn’t quite the right fit for your specific use case, you are more than welcome to share more about your workflow requirements. While we cannot guarantee immediate changes, understanding your process helps our product team evaluate potential future enhancements to our embedding options.
We hope this provides some clarity on the current options available to you!