Components are not getting retrieved correctly using Custom UI in ATFIssue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> The 'Retrieve Components' is unable to display all the list of available components in a UI Page , when using the 'Set Component Value(Custom UI)' (i.e. ATF is unable to display textarea , buttons ,etc). Using the Manual Page Inspector however confirms that the UI Page components are testable. ReleaseMadridCauseVia the UI Action (of the form) , the script to invoke the UI Page uses the GlideDialogWindow which is non-modal.ResolutionUse the GlideModal to invoke the UI Page. Example: var gm = new GlideModal("<UI_Page_name"); //Sets the dialog title gm.setTitle('Show title'); gm.setWidth(550); //Opens the dialog gm.render(); NOTE: This is a fully-featured replacement for GlideWindow and GlideDialogWindow. Related LinksCustom UI test steps Page Inspector GlideModalV3