$core_v2_dynamicForm.RenderForm takes a parameter ConfigurationXml

Unfortunately, Telligent.DynamicConfiguration.Components.PropertyGroup has never been an officially supported part of the public API. Telligent.Evolution.Extensibility.Configuration.Version1.PropertyGroup has been in the API since 10.x, though it doesn't include XML parsing and serialization. The XML format has been considered the primary, first-class, configuration format since the move to supporting property templates.

Unfortunately, Telligent.DynamicConfiguration.Components.PropertyGroup has never been an officially supported part of the public API. Telligent.Evolution.Extensibility.Configuration.Version1.PropertyGroup has been in the API since 10.x, though it doesn't include XML parsing and serialization. The XML format has been considered the primary, first-class, configuration format since the move to supporting property templates.

So how do we construct dynamic forms then? showstopper for quite a few client projects.

You can still strongly type configuration forms for purposes of defining plugin configuration. For other use cases, the recommendation has been to use XML, whether it's part of the widget, theme, automation, etc, along with script-defined property templates. You can also template XML that gets passed to RenderForm.

If you share some more about the use case, I could log this for review.

I've logged this for consideration as TE-19696. I'd still recommend creating XML instead, as it's the first class representation of configuration and is easy to template in script. It's potentially worth also noting that also since 10.x, strongly typed names of .net property types in configuration XML are also no longer preferred, which also helps with crafting of XML directly.