Source record · tier 2 current vendor documentation
Create custom desktop layout
- Publisher
- Cisco
- URL
- https://help.webex.com/en-us/article/ng08gqeb/Build-a-custom-Desktop-layout
- Published
- 2026-03-12
- Updated
- unknown
- Accessed
- 2026-09-30
- HTTP status
- 200
- License
- Cisco proprietary; no-redistribution; short excerpts and locators only
Source notes citing this source
- A team on a custom layout, including a re-uploaded copy of the default, probably does not get new Cisco layout features automatically, so the custom JSON must be compared with each new Default Desktop Layout.json. inferred in context
- Cisco's help article puts custom header widgets in area.header and uses advancedHeader for the order and visibility of header icons, while the 2023 developer blog places header widgets under advancedHeader. A builder should extend whichever header structure is in the Default Desktop Layout.json they download, not copy either source verbatim. inferred in context
- The help article describes advancedHeader as the section for customising the visibility and order of the icons on the Desktop's horizontal header. in context
- Each persona in the desktop layout JSON has an advancedHeader section and an area object. The area object holds header, panel, navigation, persistent and headless, plus homePage for the supervisor personas. in context
- The layout article says custom logo, title and illustration images can be hosted on a CDN, an AWS S3 bucket or a similar hosting service. in context
- A layout widget entry can also carry attributes (HTML or component attributes), properties (component-specific data) and wrapper (adds a toolbar with a title and a maximize icon). in context
- The comp property of a layout widget is the name of the custom HTML element (a web component, or any other element used as a wrapper). in context
- The comp value is entered without angle brackets ('<' or '>'). in context
- If the Default Desktop Layout.json is downloaded and uploaded again unchanged, it is still treated as a modified layout. in context
- The Agent Desktop header is only 64 pixels high, and the combined logo and title cannot exceed 304 pixels wide. in context
- The help article's header example defines a header object inside area, with an id, a widgets map (for example head1 with comp header-widget-one) and a layout object that has areas and size (cols, rows). in context
- Headless widgets are hidden and do not appear on the Agent Desktop, but they run logic in the background. in context
- iFrame-based widgets use the agentx-wc-iframe component, with the embedded page URL given in its src attribute. in context
- A panel tab appears only when the agent has an active contact request or conversation. in context
- The Auxiliary Information pane shows tabs for Cisco-offered widgets and custom widgets. Custom panel widgets are defined as tabs with md-tab and md-tab-panel components under the panel area. in context
- Persistent widgets show on every Desktop page. During an active interaction they appear as tabs in the Auxiliary Information pane, and they do not show on the Home page in the same way. in context
- A Webex Contact Center desktop layout JSON has three persona sections: agent, supervisor and supervisorAgent (for users with both roles). in context
- If a new desktop layout is assigned while an agent is signed in, the agent must reload the page to see it. in context
- The script property of a layout widget is required only when the widget or component is loaded from a remote location such as a CDN. in context
- Cisco says not to change the script URL for the same component. If it must change, either have agents clear the browser cache and reload the Agent Desktop, or keep the existing URL and have the JavaScript hosted there dynamically import the new bundle URL. in context
- To pass real-time Desktop data into a custom widget as properties or attributes, the administrator assigns STORE values in the layout JSON. STORE is currently the only data provider. in context
- Examples of STORE references in the layout JSON include $STORE.agent.agentName and $STORE.agentContact.taskSelected. in context
Cite this source record
APA
WarmTransfer. (2026, March 12). Create custom desktop layout. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-help-ng08gqeb-custom-desktop-layout-d
BibTeX
@misc{warmtransfer-cisco-help-ng08gqeb-custom-desktop-layout-d,
title = {Create custom desktop layout},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/sources/cisco-help-ng08gqeb-custom-desktop-layout-d},
note = {Cisco, accessed 2026-09-30}
}