{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":42026,"path":"platform-user-interface/adoption-services/limitations-of-guided-tour-designer.md","title":"Limitations of GTD","bundle":null,"doc_type":null,"release":"australia","body":"\n# Limitations of GTD\n\nLearn about the limitation of the Guided Tour Designer.\n\nThe GTD does not currently support the following areas.\n\n-   **Standard Forms and Lists UI**\n    -   Flow Designer\n    -   Agent Workspace\n    -   Pop-up windows\n    -   Connect Chat and Embedded Help on the GTD sliding panel\n    -   Select2 elements\n    -   SVG elements\n    -   Custom Tags\n    -   Standard UI pages that have custom UI elements, such as Contextual search.\n-   **Service Portal**\n    -   Service Portal pages that contain IFRAMES\n    -   The Service Portal Branding Editor, which also contains IFRAMES\n    -   Select2 elements\n    -   SVG elements\n    -   Custom Tags\n    -   Seismic components \\(shadow dom\\).\n\n        For example: sn-search-combobox - AI search box, sn-search-results-container - AI search results, ci-chat-components.\n\n    -   Tours when loaded in the Next Experience UI.\n-   **Workspace**\n    -   Only the following app shell experiences are supported:\n        -   Breadcrumb App shell\n        -   ACE Unified Nav App shell\n        -   Workspace App shell\n        -   Custom App shell\n    -   Experiences with an empty app shell are not supported.\n    -   Tours that start in a custom app shell and go to the Polaris app shell are not supported.\n    -   Not recommended to create tours on Workspaces in UI16\n    -   Variants\n    -   Callouts inside iframes in a workspace\n    -   Guided Tours that start in a standard UI or workspace and go to a service portal\n    -   Guided Tours are only supported within a page, if a link opens in a new tab the tour does not continue\n\n        **Note:** Admins must add the right action for the callout on elements that can open in a new tab.\n\n    -   Guided Tours are not supported in mobile view\n    -   Callouts on elements inside visualisation components or par widgets\n-   **Technical limitations**\n    -   Elements that are loaded in DOM by scrolling the page effect Guided Tours. The admin must inform the user to scroll further when the form is present.\n    -   If there is no click action on the elements that are selectable while creating the tour, place the callout on the parent element.\n\n"}}