UI Formatters are not working in SOWIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } UI formatters exist in Standard change template, standard change proposal and problem but, not working in SOW, what's the option to bring it in SOW?Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } AllResolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Below is the clarification and recommended approach shared by the product team : 1. **Templates in Workspace Forms:** > Formatters that utilize Jelly scripts (typically through UI Macros) are not supported in the Workspace environment. > Furthermore, standard change templates, change proposals, and problem records do not inherently support templates. > However, the Standard Change Proposal form includes a specific form element configured as a 'Template Value' type field. > This field is interpreted by the form component to render template details using the `sn-record-template-value` component. If the objective is to display a template on a Workspace form, this can be accomplished by creating a template field and incorporating it directly into the Workspace form layout. 2. **Formatter Support in Workspace:** > While documentation is limited, formatters are technically supported in the Workspace environment. > When creating a UI Formatter, you have the option to select a 'Seismic Component.' > This feature enables you to attach a custom-built component—deployed via the ServiceNow CLI—to the formatter, allowing it to render correctly within the form. As an example, we successfully configured an 'Audio Player' component linked to a UI Formatter and incorporated it into the form layout, as demonstrated in the attached screenshots. 3. **About ServiceNow CLI:** > The ServiceNow Command Line Interface (CLI) is a development tool that facilitates efficient management of your ServiceNow instance through command-line operations. > It allows developers to automate tasks such as creating, deploying, and updating custom components and applications directly from their local environment. In this context, the ServiceNow CLI is utilized to deploy custom components (such as Seismic Components) into the instance, enabling integration with UI Formatters and rendering within Workspace forms. **Summary of Configuration Steps:** * Link your custom Seismic Component to the UI Formatter configuration. * Configure the Formatter within the form layout. * Ensure your component is properly built and deployed to appear on the form. NOTE:Please feel free to reach out to us by logging a HI case if you would like assistance with this configuration or have any additional questions.