Overall, the new form editor with enhanced conditional logic is a VAST improvement with tons of promise, two big drawbacks in current beta state that are preventing us from actually testing in a client-facing capacity though - Hidden Fields: Currently, you cannot use hidden fields in the same way that you can with the legacy forms editor. You can hide fields when certain conditions are met, but in the old from, it was really helpful to be able to use hidden fields to pass values along to contacts/companies/tickets upon submission. Theoretically this is still possible with workflows (contact has submitted "x" form, populate with "y" values), but there's a lot of reasons why it would be better to accomplish this natively in the form as opposed to through workflow. Both because of maintenance/number of workflows, and to keep a stronger hold on permissions around workflows in general. Non-contact/company properties: Currently, this is the big blocker in allowing us to actually test this beta with a public-facing form in the new editor. The new logic is a VAST improvement over what we had previously, but we're primarily trying to create tickets based on form submissions to take advantage of this logic. In current state, the only way we could do that is creating a bunch of contact properties that we don't have much use for and syncing them over to a ticket. Ideally, we'd be able to ask for ticket properties in the form editor same as we can in the legacy editor. Sync fields (with their various limits) is not a good solution here either, because we'd still be creating contact properties that have no use other than to be a container to sync over to a ticket, which is not ideal.
...read more