Custom Values for Forms
M
Matthew Lundeberg
I'd like to see custom values for forms NOT associated with contacts. Keep them separate. Then we build as many Forms as we need and keep the fields off the contact.
Use Example:
In the medical field:
- each subaccount may have 20-30 different intake forms. We want to build these custom forms for them and not clutter the contact.
- ALSO for HIPAA, we don't want the answers readily seen on the contact fields
- ALSO the same contact may fill out the SAME form 100s of times so the answers and forms need to be separate not updated on each submission.
- Then assign the form to a contact based on a contact field THAT WE CHOOSE!
Patient > customfield (Account Number or ExternalID or Company Name)
A. Appointment today I ask them to fill out Form "Reexamination Questionnaire"
- So they get a blank form to fill out and the form is aware of the contact bc of the customfield I assigned to the form.
- I want to be notified when the form is received and be able to print it out and also be able to access via API to absorb into their EHR system dynamically.
- I DO NOT want it to update the contact info in any way UNLESS I tell it to.
- Each field on the form should be able to set to map to a contact field to update on submission to it OR to do NOTHING at all if not mapped.
This also applies to surveys, appointment forms, chat widget forms, payment links, documents etc..
Thanks!
Log In
M
Matt Galloway
Different use case but I'm currently using forms to update custom values (i.e. at the subaccount level) across landing pages, emails, workflows, etc. in a prebuilt funnel. I use custom values to update copy, date values, and images for monthly webinars, and doing it with forms allows me to use workflows and logic after form submission to dynamically update custom values. Plus, this way I can give someone who's not a subaccount user the ability to update these values (i.e. a copywriter or graphic designer on a different team).
The downside to this is that I currently have to duplicate all of the values as contact custom fields in order to map them from the form to the custom values. I guess I could technically do this through opportunity custom fields instead to keep the contact view cleaner, but the best option would be to have custom values as field options in the form builder so I can use forms internally in this way.
Additionally (and maybe this should be a separate ticket), it would be VERY helpful and save me a lot of time if we had an option in the workflow "update custom value" steps to clear them rather than just update them to a new value.
Y
Yaneck Wasiek
yes, that would be great!