Skip to main content

WebApps - Dynamic Field Content

Ability to add other dynamic content (from Modules, WebApps etc) into WebApp fields.

9 comments

Log in to comment and vote

Comments9

  • Matt Walter changed status to In Review
    Team•

    Apr 6, 2022

  • Urszula Richards

    •

    Aug 23, 2021

    Could we get an indication when this may be scheduled?

    • Matt Walter

      Team•

      Aug 23, 2021

      Urszula Richards: It's not on our immediate Roadmap, but is planned for us to look at in the future. It's unlikely to be this year.

  • Matt Jones

    •

    Feb 3, 2020

    I'd be wary of removing this security feature without putting some safeguards in. If WebApps can be submitted with Front End forms, then also allowing them to output and render Liquid could be dangerous- including it would allow attackers to render GraphQL queries and mutations. I'm guessing you'd restrict it to Liquid includes only?

  • Khy Tran

    •

    Nov 19, 2019

    Is this the same as adding a Web App within a Web App? If so, can we get this pushed up by any chance. Nothing worse than not being able to reference another Web App, especially when we're using Web App data source fields!

    • Matt Walter

      Team•

      Nov 19, 2019

      Khy Tran: Being able to have a multiline/WYSIWYG text field that outputs dynamic content. For example, being able to write {% include 'webapp', id: '123', type: 'list' -%} and it actually render the list view. At the moment it would output that literally.

    • Helen Eichel

      •

      May 27, 2020

      Matt Walter: Matt - would that include being able to include any liquid code into WebApp text fields? Thanks

    • Matt Walter

      Team•

      May 27, 2020

      Helen Eichel: Yes, exactly that.

    • Helen Eichel

      •

      May 27, 2020

      Matt Walter: That's great. Any idea when this will kick in? Thanks!