New beta form editor and developer functionality

[Dadams]

We've recently released a beta version of a new form editor tool. The new editor has several new features for HubSpot users building forms and embedding them onto the HubSpot CMS and external pages

It's important to note that forms built using this new editor do not support the existing developer features that can be used with forms created with the legacy form editor. These features include:

• Customizing the embed code
• Global form events
• Manipulating form fields using jQuery

Any other custom code written to work with older forms should not be expected to work with forms built using the new editor. As the code for new forms is still being developed, we do not recommend writing code to work with new forms at this time.

Existing forms will continue to function as they previously have. If you need to use any of these developer features, you should continue to use the legacy editor for new forms for the time being.

Developer features similar to the existing features for legacy forms are planned to be supported for forms created with the new editor in a future update.

Please let us know if you have any questions by replying below.

[NayanD]

We were using legacy forms with the Row HTML version. Will the Legacy Form Editor be discontinued in the future?

[DRodgers]

The opt-in, data privacy features forces you to add text that is completely unnecessary. I can't use this builder if we cannot update this.

[JawsTitan]

Hi! What is the timeframe for this beta and also when does HubSpot intend to support Global form events such as embed code callbacks?

[MTSUWD]

Hi @Dadams 

I also don't understand why the whole thing was realized via iframe, it makes so many things more difficult. In our case, the Embed Code customization is very important, we urgently need options for: sfdcCampaignId, goToWebinarWebinarKey, onFormReady and onFormSubmit for the new forms.

[jnishanthbabu]

Form Editor Beta & custom JS

The new beta form editor is promising, but the lack of embed code customization and third-party library support makes it tough to switch from legacy forms. Loading forms in an IFRAME adds more issues than benefits—accessibility through the primary domain should be the default.

When can we expect the new Beta Form Editor to support these features.?

[ClearoutIo]

We assist HubSpot Forms in validating, enriching form fields in real-time. However, without allowing to customize the embed code, form events, manipulating with 3rd party library it is hard to switch to new form from legacy. Please bring back these features, also dont understand why to load it in IFRAME, it creates more problem just merely solving a content isolation. I believe, by default the form & its fields must be accessible by first part domain and can only be loaded in isolation if necessary

We also noticed, the same issue with the CTA forms. More here https://community.hubspot.com/t5/HubSpot-Ideas/Allow-loading-new-CTAs-Beta-outside-of-iframe/idi-p/8...

[lere]

Hi, @Dadams! Any news or estimated deadline about Global form events?

[lere]

Ok, my workaround:
- Configure Cloudflare Zaraz as a server-side tag manager, in order to send data to GA4 and other services (difficulty: medium)

- Use HS Actions to send an HTTP Request to the Zaraz Endpoint when the form is filled.

[WBHydrosense]

any update on the embed/custom html/javascript functionality? I moved from the legacy to the new beta form so that I can leverage the extended dependant field functionality, after setting up my form with the new editor, adding in all my logic etc I am extreamly annoyed to find that it doesnt icnlude embed code features! Its one step forward two steps back with hubspot! The only reason i need custom html is becuase for some reason hubspot doesnt nativley support extreamly basic functions like a slider! 

[WBHydrosense]

still nothing?

[MGeorge758]

The dropdown field is currently a pain to work with in the new form editor. You can only edit the dropdown items in the UI and not the sidebar, and you also can't add more than two options in the dropdown.

[kgwozdz]

Hi, 

I have two questions regarding the new form.

1. Do we get a "Set as raw HTML" option? We usually need more than the styling options that are available in the builder, which is why I always use this option

2. The new form is now available as a built-in module - will it stay that way?

[Azza2]

Hey I'd love to use the new form beta, but I'm curious to know if there's a timeline on adding things like: 
- custom styling

- form events

I don't think I can use it at this point, and would love to know a very rough timeframe of when these might be available? 

[joshm]

Agree with @Anton. Iframe feels like a step back. Ability to have raw HTML version/apply custom CSS would be a minimum. All sites I manage HubSpot forms on would be on legacy versions for a while if those options missing above were not implemented.

[Dadams]

Hi @Anton and @remingtonbegg ,

For the moment I'd recommend using the legacy form builder for any uses that rely on any of the developer features. The legacy form builder is still available even for accounts in the beta, and forms created with the legacy builder will work the same as any previously created forms, and will continue to support the existing developer features.

An updated version of the embed feature for the new beta form builder is coming soon, and will include the ability to embed the form in a page without using an iframe. The updated code will not immediately support modifying the embed code or manipulating fields using JavaScript, but those features are planned for new forms.

[Anton]

Thank you for the update @Dadams.

Looking forward the updated version

best, 

Anton

[Anton]

Hey @Dadams, 

first of all I really like the beta and the new "look & feel" of the form creator. Makes the form creation really nice and easy, it's a very nice improvement and multi-step forms are something that was way overdue. 

On the other hand the fact that it doesn't support embed-code customization, form events and jQuery manipulation feels like a punch in the guts.

Manipulating the embed code was THE feature when you've embedded the form on an external page. 

It is nothing else than a "must have feature" and should be possible. 

Also - loading the form inside an iframe feels like an imense step backwards.

It's almost like "you'd like to modify something? Please feel free to invest a lot more time and write extra code accessing the/an iFrame".  

Please don't get me wrong but unless the previously supported features are supported, no advanced use-case is applicable and partners/developers most likely won't use the new form builder.

I would totally dig a "developer" area while creating the form(in the settings) which would allow devs to add modifications to the form - or make it even more global by adding the same options to Settings/Marketing/Forms. Kinda like the "add code to header/footer" in the pages settings. 

+1 on @remingtonbegg's comment about the notice time.

Thank you

best, 

Anton

[bradhave]

☝️

[remingtonbegg]

Hello friends.

This gives me some major heartburn. One of the first things come to mind -- if someone creates a new form and connects it to HubSpot module that is currently leveraging some of these features from a development standpoint (IE:

• Customizing the embed code
• Global form events
• Manipulating form fields using jQuery

)

What happens. Does it just "brick"?

If So, when will developers be given more than (less than) a week's notice for potential breaking change updates that HubSpot is implementing? I'm all for platform improvement, but this seems short-sighted to "launch" without enabling past functionality that got HS to where it is. How can this not be a "requirement" for launch in general?