The Custom Form can be:
-
either embedded into another document (quote, deal plan, standalone custom form)
-
or act as a standalone document, with it’s own list page and detail page
Here’s the comparison of features provided by the 2 variants
| Feature | "Embedded" form | "Standalone" form |
|---|---|---|
Menu item to access the list of forms instances |
- |
Own configured menu item |
List page |
no, they’re managed from inside the parent objects detail pages |
yes, accessible via own menu item |
Layout |
not supported, only single page with inputs, outputs |
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 |
unused |