Some element containers offer the possibility to integrate other forms that fit the context, such as data input forms, dashboards or portals (license dependent).

►NOTE◄ Embedded forms are not automatically updated when the original has been changed! This can be done manually via the Auto reload function (see below).

The following image shows the configuration options of the editor.

images/download/attachments/55935919/image2020-6-23_8-29-57-version-1-modificationdate-1592893798790-api-v2.png

1	Opens a dialog for selecting the form to be embedded. The forms that are available here depend on the type of the main form and the licensed modules. The following image shows the dialog for form selection. (A) The type of form to be embedded (e.g. portal, shipment form, etc.). (B) Selection of the desired form. (C) Inserts the selected form into the container element. ►CAUTION◄ This action completely overwrites the contents of the container, without regard to any modifications previously made! (D) Offers the possibility to insert the section elements of the form.
2	Indicates that the selected container already contains an embedded shape. Clicking on this note shows which form it is or warns if it is no longer accessible.
3/4	If a form is already embedded, it can be reloaded via the Refresh (3) button or even discarded completely with Remove (4). ►NOTE◄ When updating, the current version of the referenced form is loaded into the container, overwriting all previous content including any modifications made!
5	If the container embeds a form, the Auto reload option is available. If this option is enabled, the most recent version of the included form will be displayed automatically when it is loaded. The embedding container then displays a corresponding symbol as a notification . Since any configurations within the included form would be discarded anyway when loading, an automatically updated form can also no longer be configured. Only elements can be linked in it. ►CAUTION◄ To be able to guarantee full form functionality when linking elements, it should always be ensured that the embedded form is not manipulated in this way. There are no automated checks for this. Cyclic form dependency When updating automatically, care must be taken not to cause cyclic dependencies between included forms. E.g. Form A → Form B → Form A or also Form A → Form B → Form C → Form A or Form A → Form B → Form C → Form B Since the form would run into an infinite loop when loading in such a case, a warning is displayed by the corresponding container instead:

Element containers that already embed a form will be highlighted in the element tree (see images below).

Further info

When inserting a shape, all element IDs of the inserted elements are prefixed (e.g. "_RT1_"). All references within the sub-form are also adjusted accordingly. This prevents clashes of duplicate IDs while maintaining the form functionality of the embedded form. If the form element itself defines a data field, this is also set to the inserted container.