The Custom Form can be:
-
Either embedded into another document (Quote, Deal Plan, standalone Custom Form).
-
Or act as a standalone document, with its own list page and detail page.
Here’s the comparison of features provided by the two variants:
| Feature | "Embedded" Form | "Standalone" Form |
|---|---|---|
Menu item to access the list of form instances |
- |
Its own configured menu item |
List Page |
No, they’re managed from inside the parent object’s detail pages. |
Yes, accessible via its own menu item. |
Layout |
Not supported, only a single page with inputs, outputs. |
It can have multiple sections with multiple tabs, where one of them is the page with inputs/outputs. |
Custom Header |
Yes (but likely not reasonable to use, when the parent doc has its Custom header too) |
Yes |
Approval Workflow |
No |
Yes |
Field CustomForm.parentTypedId |
Refers to the document/object, into which it is embedded. |
Not used |