Page metadata
Every CloudPage can declare metadata in its <head> that CloudPages reads to
decide how the Page is titled, where it appears, and how it launches. All tags
are standard <meta name="..." content="..."> elements.
CloudPages parses only the <head> (first ~10 KB), so declare these near the
top.
<head> <meta charset="utf-8"> <title>Receiving Summary — browser tab title</title>
<meta name="fb_title" content="Receiving Summary"> <meta name="fb_path" content="Reports:ILC Products"> <meta name="fb_modules" content="Receiving,Purchase Order">
<meta name="fb_button_show" content="true"> <meta name="fb_button_text" content="Receiving"> <meta name="fb_button_icon" content="img/button-24.png">
<meta name="window_width" content="1100"> <meta name="window_height" content="750"></head>Identity and placement
Section titled “Identity and placement”| Tag | Content | Notes |
|---|---|---|
fb_title |
Display title | Shown in the Available Pages list, module dropdowns, and window title. Falls back to the filename when absent. |
fb_path |
Folder:Subfolder |
Placement in the Available Pages tree, :-separated. Administrators can override per install. |
fb_modules |
Comma-separated module names, or all / * |
Which Fishbowl modules list this Page. all (or *) means every module. |
A Page has no description meta tag. The description shown in the Available Pages list is set by an administrator in CloudPages → Edit → Details, or supplied by a manifest source.
Module names: Sales Order, Purchase Order, Part, Product, Work Order, Manufacture Order, Bill of Materials, Customer, Picking, Shipping, Receiving, RMA, Transfer Order, Pricing Rule, Reports, Vendor, Inventory, Consignment, Calendar, Carrier, Currency, Custom Field, Data, Discount, Import / Export, Location, Location Group, Payment Terms, Checkout, Class, Tax Rate, UOM, User, User Group, Company, Accounting Integration.
Toolbar button
Section titled “Toolbar button”A Page can promote itself to a button on the toolbars of the modules it belongs to. An administrator’s explicit choice always wins over the Page’s declaration.
| Tag | Content | Notes |
|---|---|---|
fb_button_show |
true / false |
Declare the button on by default. |
fb_button_text |
Label | One word, max 20 characters. Required for the button to render. |
fb_button_icon |
Image reference | Optional. A page-relative path (img/button-24.png) or a data: URI. PNG/GIF/JPG — no SVG. Rendered at 24×24. |
Icon resolution order: fb_button_icon → the Page’s favicon
(<link rel="icon" href="...">) → the stock CloudPages icon. The same image is
used as the Page window’s title-bar icon, so a larger source (for example
64×64) renders crisper there.
Window behavior
Section titled “Window behavior”| Tag | Content |
|---|---|
window_width / window_height |
Initial window size in pixels. Set both together. |
window_state |
normal, minimized, or maximized. |
window_style |
normal (toolbars and status bars) or minimal (browser only). |
Per-install overrides
Section titled “Per-install overrides”Administrators can override title, description, modules, folder placement, and the toolbar button per install from CloudPages → Edit. Overrides are stored with the Page and win over the Page’s declared defaults. Blank an override to revert to the declaration. See Administration.