text: lucatoeb The concept behind the new forms is their independence from specific technologies. The rendering process at runtime is entirely abstracted, allowing for flexibility in swapping out the underlying technology stack without requiring migration for you or your customers. While the code is hidden, you still have the option to "break out" of the default form framework if it doesn't meet your requirements. In such cases, you transition into the familiar JSF technology stack, where you can customize freely. However, it's important to note that this decision is irreversible—once you break out, you cannot revert to the original form.
  You mentioned the absence of a graphical editor for the old HTML Forms. This is correct, as the graphical editor was discontinued. The decision was based on the numerous challenges it posed for both functional and non-functional requirements, as well as the difficulty of maintaining a separate technology stack for it, which was entirely distinct from the core of Axon Ivy. With the introduction of the new form editor, we believe it offers a much-improved experience for low-code developers, aligning better with modern needs.
  I hope this has answered your questions, and we look forward to any feedback you may have.