4 results found

1. Visual Builder forms are incomplete when fetched with @optimizely/cms-sdk

   Visual Builder forms are incomplete when fetched with @optimizely/cms-sdk

   In Optimizely SaaS CMS, Visual Builder forms work in the editor, but the content JS SDK (@optimizely/cms-sdk) does not return everything needed to render them on the site.

   When a Form Container is placed on an Experience, the SDK query does not go deep enough to include the fields inside the form (step → row → column → elements). Form Container properties set in CMS — Title, Description, Submit URL — are also missing from the response.

   As a result, forms cannot be implemented with the SDK as-is. We had to patch the SDK locally so the same content query returns the full form.

   Steps to reproduce:

   1. Activate Forms in CMS (SaaS) and create a Form Container with at least one step, row, column, and form elements (e.g. Textbox, Submit).
   2. Set Form Title, Description, and Submit URL on the Form Container.
   3. Add the form to an Experience.
   4. Fetch the Experience with @optimizely/cms-sdk (getContentByPath / standard composition query) and render it.

   Expected: The SDK returns the full form: layout, all form elements, and Form Container properties (Title, Description, Submit URL), so the frontend can render and submit the form with no extra query.

   Actual: Form elements inside columns are missing. Title, Description, and Submit URL are not returned. Only structure metadata (e.g. displayName) is available.

   Impact: Teams using the official content JS SDK cannot ship Visual Builder forms without patching the SDK or writing a custom Graph query. That is not a supported, upgrade-safe path.

   Request:

   1. Make the SDK composition query deep enough for the form structure: experience → form → step → row → column → elements.

   2. Return Form Container properties (Title, Description, Submit URL, confirmation messages) on the form node, the same way other component properties are returned.

   3. Document the supported way to render and submit SaaS Visual Builder forms with @optimizely/cms-sdk.

   Visual Builder forms are incomplete when fetched with @optimizely/cms-sdk

   In Optimizely SaaS CMS, Visual Builder forms work in the editor, but the content JS SDK (@optimizely/cms-sdk) does not return everything needed to render them on the site.

   When a Form Container is placed on an Experience, the SDK query does not go deep enough to include the fields inside the form (step → row → column → elements). Form Container properties set in CMS — Title, Description, Submit URL — are also missing from the response.

   As a result, forms cannot be implemented with the SDK as-is. We had to… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  Forms  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Need the ability to set the TinyMCE Toolbar height

   CMS (SaaS) does not currently expose an explicit height/width setting for the rich-text editor. Unlike CMS PaaS (where the editor size can be set in code via the TinyMCE Configuration API), SaaS is configured entirely through the content-type contract, and the only editor setting available for a rich-text property is the toolbar preset.

   As a developer worried with the user experience, I would like to have the ability to set the text area's height, at least.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  Forms  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Date/time element for forms

   The current supported form types for SaaS CMS do not support a date/time element. This is a common element for dates, DOB etc

   Reference
   https://docs.developers.optimizely.com/content-management-system/v1.0.0-CMS-SaaS/docs/form-elements

   •  

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Forms  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering Feedback  ·  AdminMaheen Neha (Senior Product Manager, Optimizely) responded

   We’re currently gathering additional feedback on this idea. If you have any more context, examples, or specific use cases, please share them - it really helps us understand how this would best support your workflow. Thanks for contributing to the conversation!

4. Allow authorable field names in Forms

   With the new SaaS forms, there is no way to set a custom field name. I can add an additional field to a from field in the CMS, but if I do that, I am blocked from publishing the form field. Field name is essential. When you submit a form in HTML, the 'name' attribute on a property is how the form knows what to submit. The examples you provide suggest formatting the label value. This is insufficient. An example of why this is a problem: If I am submitting a form to a third party service, like Eloqua, the names of the fields MUST match the names of the fields in Eloqua. Currently, there is not a good way to accomplish this.

   With the new SaaS forms, there is no way to set a custom field name. I can add an additional field to a from field in the CMS, but if I do that, I am blocked from publishing the form field. Field name is essential. When you submit a form in HTML, the 'name' attribute on a property is how the form knows what to submit. The examples you provide suggest formatting the label value. This is insufficient. An example of why this is a problem: If I am submitting a form to a third party service, like Eloqua, the… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Forms  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Research & Design  ·  AdminMaheen Neha (Senior Product Manager, Optimizely) responded

   Good news - this idea is now being explored by our product and design teams. We’re researching potential solutions and scoping out what an implementation might look like. We’ll share updates here as our thinking evolves.