My FormAssembly wish list
I have been a big fan of formAssembly, primarily from the angle of a Salesforce administrator of a complex org. I’m maintaining a running list here of issues and functionality that I hope to see added. [last updated sept 2019]
- provide connector level skip logic on all connectors
- allows for much better management of updates to live forms as can have test-only connectors that are activated by a URL parameter
- error handling
- only option is a single global email address.
- this could be set per form, or better would be to have error connectors so you can really customize what happens
- add excel online connector
- microsoft is back baby…and gdpr means they are our only hope. so if we could submit to excel that would be handy. we built a custom api to do this, and it works, but would be great to see officially supported.
- provide built-in functionality for discount codes and scholarships
- using client side js is easily hacked
- scholarships (100% discount) require are very poorly supported and require a lot of custom js
- add a stack-ranking question type (a list of options that can be dragged into order)
- add limits to selection (select your top 3 ice cream flavors)
- prefill picklist or autosuggest form field from a salesforce object
- this has been built but inexplicably was only enabled for enterprise accounts. it requires the pre-fill connector which is available in the premier account level. the migration from premier to enterprise changes the URL for each form, and is a huge undertaking. this could be a big red flag for the trajectory of this company in terms of not understanding their customers.
- get contact’s account ID and use in dependent steps
- needed in opportunity creation and for adding new contacts to an existing household
- more broadly using a lookup objects fields in dependent lookups would be very powerful.
- clone connector steps on prefill connector (no option to do so)
- enable connector-level variables
- we have a few ‘generic’ forms that we clone often. we use form fields to store values that are mapped in the connector, typically in multiple places, like campaignID. This makes it is easy to update and clear to review. It also exposes all these fields on the client side. Would be much better to allow for connector level variables, which could be referenced in multiple connector steps.
- allow setting currency on stripe connector from a form field, as a single stripe account can have multiple bank accounts in different currencies and stripe can automatically segment deposits by currency.
- this can significantly reduce foreign exchange costs for donor as well as recipient
- allow lookup against sfdc or stripe to find existing customer id instead of creating a new stripe customer for each transaction
- (dream a little dream) - build an endpoint to capture webhooks from stripe (or anywhere) and process them like a form submission. this is complete fantasy, but given that TFA such a solid back-end into sfdc (better than some integration tools i have seen) it could be very useful.
- i cant imagine anyone using it as currently baked. try it yourself
- the ‘or type your name’ option on the signature page is hella confusing to me as its a required field - you have to type it! there is no or! it should say something like ‘replace your signature using your name’
- the ‘incomplete response’ message sure looks like an error message, and it displays before you click submit. i understand that they want you to be clear that there is one more step - but that should be presented as a tip, not an error. and it can be simply reinforced by setting a notification message, which is displayed after submission
- the verification page you are taken to from the email link is pretty sad. the only part of the whole process that is decent is the final ‘summary’ page which looks pretty good!