BevQ · How-To
Publish BevQ to TV, widgets, social, and web
Each output has its own eligibility, configuration, preview, and publish state even when it uses the same menu.
What this does
Each output has its own eligibility, configuration, preview, and publish state even when it uses the same menu.
Steps
- Confirm the location and source menu.
- Open TV, Widgets, Social, or the intended publishing surface.
- Choose eligible layout, content, and destination settings.
- Preview the output.
- Save or publish.
- Verify the public URL or Player and troubleshoot that channel independently.
Widget settings
Coverage selects the source location/menu; content filters control eligible items; design controls presentation; Copy Embed Code uses the saved widget identifier.
TV settings
Player, menu, and layout must be compatible. Preview does not guarantee delivery to an offline Player.
Channel independence
TV, web widget, printable, and social publishing retain separate settings and states so one channel can succeed while another requires attention.
Settings reference
| Setting | What it does | Default | Scope | Notes |
|---|---|---|---|---|
| Menu/source | Selects published content | Current selection | location/output | Must contain visible eligible items. |
| Layout/design | Controls presentation | Current template | output | Preview before publish. |
| Widget design and content filters | Configures widget design and content filters. | Current product default shown in the UI | location | Requires bevq editor; displayed choices are authoritative for the current account and release. |
| Layout and display options | Configures layout and display options. | Current product default shown in the UI | location | Requires bevq and devices; displayed choices are authoritative for the current account and release. |
Permissions and scope
- No Access hides or blocks the module. Read Only permits viewing but disables changes. Editor permits the documented create, edit, publish, or administrative actions within the user's assigned scope.
Mobile
- On narrow screens, open the sidebar or overflow menu to reach the same actions; labels and save behavior are unchanged unless this article says otherwise.
Offline and stale content
This control is covered by the Publish BevQ to TV, widgets, social, and web workflow.
Applies to /android/bevq/:deviceId/:id
Create and configure widget
This control is covered by the Publish BevQ to TV, widgets, social, and web workflow.
Applies to /admin/bevq/embeds
Widget design and content filters
This control is covered by the Publish BevQ to TV, widgets, social, and web workflow.
Applies to /admin/bevq/embeds
Copy embed code
This control is covered by the Publish BevQ to TV, widgets, social, and web workflow.
Applies to /admin/bevq/embeds
Public preview and empty states
This control is covered by the Publish BevQ to TV, widgets, social, and web workflow.
Applies to /admin/bevq/embeds
Draft and publish
This control is covered by the Publish BevQ to TV, widgets, social, and web workflow.
Applies to /admin/bevq/social
Provider and validation errors
This control is covered by the Publish BevQ to TV, widgets, social, and web workflow.
Applies to /admin/bevq/social
Layout and display options
This control is covered by the Publish BevQ to TV, widgets, social, and web workflow.
Applies to /admin/bevq/tv
Preview, publish, and offline Player states
This control is covered by the Publish BevQ to TV, widgets, social, and web workflow.
Applies to /admin/bevq/tv
What happens next
Your change is available within the scope you selected.
Warnings
- A public widget URL can be shared externally. Review menu content and location before publishing.
Troubleshooting
- Empty output can mean no published menu, no eligible visible items, wrong location, or an inactive widget.
- TV changes wait for an online Player to receive the new configuration.
- For unavailable menu state, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.
- For empty or unavailable widget, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.
- For offline and stale content, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.
- For public preview and empty states, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.
- For provider and validation errors, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.
- For preview, publish, and offline player states, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.