An E-form field loads another E-form inside this one. The embedded form keeps its own fields, its own layout and its own saving behavior; the form around it decides where it appears, which record it works on, and what happens when it is finished.


Use it to reuse a form you already have rather than rebuilding it - an address block, a contact form, a signature page - and to build screens where the user works through several small forms in one place. Dropped inside a Modal Window, it becomes a pop-up data entry form.


Which form, and which record

E-form - The form to load. Custom E-form lets the form be chosen by a value rather than fixed, so one field can load different forms depending on what the user has selected.


Load From Record ID - The record the embedded form reads its data from. Leave it blank to use the record this form is open in.


Save To Record ID - The record it saves into. Leave it blank for the current record, enter 0 to create a new record, or give a specific record's ID. The 0 case is the one to know: it is how an embedded form adds new records - one per submission - from a screen the user never leaves.


Add/Update Document - Whether saving updates the existing document or adds a new one. Where nothing matches, both settings add a new document.


Load Specific Document ID - Loads a particular document into the form. The document must have been created from the same E-form. Leave it blank to use the first document in the record based on that form.


Passing values in and out

Values to Pass In on Load - Values handed to the embedded form as it loads. Set fixed values, or use {field} notation to pass values from the surrounding form - so a child form opens already knowing the customer, the date or the reference.


Dynamically pass field changes into child form - With this on, changes made on the outer form continue to flow into the embedded one. With it off, the values are passed once as it loads. Leave it off unless the child genuinely needs to follow the parent, since it is easier to reason about.


Values to Pass Out on Save or Pull - Values handed back to the outer form when the embedded form is saved, or when the Pull E-form Data action is used. Refer to the embedded form's fields with double braces - {{fieldname}} - which is what distinguishes them from the outer form's own fields.


Reacting to the embedded form

Three settings let the outer form respond. Each sets a field to a New Value, and a Multi-Action watching that field does the rest.


Update Field when Loaded - Once the embedded form has loaded.


Update Field when Saved - Once it has been saved. This is where most of the work goes: pull the values back, add a row to a table, refresh a search, and close the window.


Update Field when Canceled - Once the user abandons it.


Two shortcuts are worth knowing. Sending the value run to a Multi-Action field runs it, so these settings can trigger a sequence directly. Sending close to a Modal Window closes it, so an embedded form inside a modal can shut its own window when it saves. The values passed can also include the child form's own values using the {{field}} syntax above.


Display

Shadow Size - None, Small, Medium or Large drop shadow around the embedded form.


Points to watch

An embedded form inside a Modal Window or a collapsible Panel should normally have that container's Pre-Load Contents turned off. Left on, the child form is loaded once and stays as it was, so the second time the window is opened the user sees the previous entry rather than a fresh form.


An embedded form used on a public form only reaches records the site exposes publicly, the same as any other public field.