html input component for UI Builder
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2022 09:43 AM
Is there an html input component that I can add to a page in UI Builder? I see text area and input components, and an html input shows up if it is a field in a form component, but I don't see a standalone html input component.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2024 06:22 AM
Hi Michael,
I am looking for the same option. Did you find the HTML editor component in UI builder?
Regards,
Jagadeesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2025 05:29 AM
Hi,
there seems to be a HTML editor component. It's called "now-record-html-editor" and can be found in the sys_ux_macroponent table.
It's not available from the component picker inside UI Builder.
There is no documentation as faras I know.
I've managed to add it to a page by adding it in the sys_ux_macroponent record of my Page variant in the "Composition" field.
I have not managed to make it work in any meaningful way yet: I don't know how to set or retrieve values from it.
Judging by the name and the lack of documentation, the component is probably meant to be exclusive to the Form controller and is handled purely automatically.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
If there are still people that are in need of a solution:
1. There is a component called: "Document Display"
2. Change the Document Type from "Attachment" to "HTML"
3. Mark the "Enable editing" Checkbox
4. Now users can use the Component as a HTML Editor
5. Use the value payload to map the HTML Code
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
This looks interesting, but I'd consider it a workaround at best.
We can't be sure if or when ServiceNow might expand or reduce the functionality of the component. We also can't configure the editor in any way, so no configuring the controls, plugins, etc.