Default Values from Form Submission
S
Sarah Humphries
This would be great as it would allow me to create multiple forms for the same table and then default the 'category' for the record based on the form used. It prevents the user having to manually select the category. I can then run automations to assign different users depending on the category.
Brian Dollen
Merged in a post:
Default fields applied with forms too
T
Triz bodegalaabs
If a specific field has a default option, apply it also if the record was created via form.
For example, for the assignee option this is not happening at the moment
T
Triz bodegalaabs
For example in the Time-Off Request template, there is a field for "employee = requested by" - this field defaults to "Record Creator", but when created via form, it does not apply it to the person who submits it.
If who submits the form is logged in into SmartSuite, getting that info directly would allow:
- Person not able to submit in behalf of other employees
- Saving time as this info does not need to be included
For other fields, I believe this is ON as the status defaults to "Submitted" and it is applied when record is created via form.
Jon Darbyshire
Hey Triz bodegalaabs, thanks for your feedback! I have a few more questions for you:
- Can you provide an example of a form where you'd like to see this feature implemented?
- Are there any specific default options you're referring to, besides the assignee option?
- How do you envision this feature improving your workflow or user experience?
Larry Baxter
Jon Darbyshire not Triz but our company was interested in this as well. After writing the use cases below, I looked up forms documentation and noticed I missed the release of Hidden Value and “Limit Selection to specific options” which probably gives us all we need for now. My comments echo was Sarah asked for in this thread.
Use Case I. We have a CRM-like app where users can share touchpoints with customers, monthly updates, and change-in-status updates. Rather than three apps, would love to share three distinct forms. “Update Type” would be different for each. That’s more of a hidden/prefilled form field. The “Priority” field would ideally have different defaults per form. Also the Assigned field has different default or pre-fill.
Use Case II. A form for people to express interest. One app but ideally a different form with different questions: one generic form to put on our website, a second form we would share at a conference, a third for a social media share. Interest field and Source field would have different defaults on each form.
How would this improve our workflow or user experience?
* Users land on a form customized to what they want to do, and less data to have to enter
Workflow - love the new dashboard and selector/details functionality! Mgmt wants to see
one* details table with all updates which suggests this one-app multiple-forms approach where a different default or hidden type field Default-per-form would still be nice but now that I see hidden fields are possible, it’s less critical.