Property reference

`glide.ui.allow_deep_html_validation`

The glide.ui.allow_deep_html_validation property allows administrators to restrict users from saving invalid HTML in journal fields. By default, this property is set to false, enabling the use of irregular HTML tags, which may be necessary for certain workflows.

Default: Not stated
Type: Not stated
Application: Not stated

Key questions about this property

The answers below summarize the purpose, scope, default effect, and review scenarios for this property.

What does it do?	This property prevents the saving of invalid HTML in journal fields, ensuring that only valid HTML is stored.
What area does it affect?	Journal field validation
What does the default mean?	No default value is stated in the ServiceNow documentation.
When should you review it?	Review this property when configuring HTML input restrictions for users.

Property record

Facts stated in the ServiceNow documentation. No out of the box record has been read from an instance yet.

Property name	`glide.ui.allow_deep_html_validation`
Type	Not stated
Application	Not stated
Default value	Not stated
Description	Not stated

Sources

Official references and nearby text excerpts where this property appears.

Brazil docs View supporting context

Context preview Snippet 1

... set to the dependent field. For example, a subcategory field which depends on category field. • Type: true | false • Default value: true • Location: System Property [sys_properties] table glide.ui.allow_deep_html_validation Allows administrators to prevent users from saving invalid HTML in a journal field. • Type: true | false • Default value: false • Location: Add the property to the System ...

Brazil docs View supporting context

Context preview Snippet 2

... This activity allows the use of irregular HTML tags to reference attachments, specifically the [code] tag. Entries in a journal field that use irregular HTML do not work if the glide.ui.allow_deep_html_validation property is true. This property is set to false by default. Note: Task activities run as the user whose actions complete the task the workflow was waiting for and advances ...

More in `glide.ui`

Other properties in the same namespace.

glide.ui.admin_import_xml_roles This property defines which user roles are allowed to execute XML imports, with 'admin' as the default role. glide.ui.advanced This property controls the visibility of key action buttons on forms, allowing users to save or insert records glide.ui.ais.show_all_facets This property controls the visibility of all facets in the Filters list for AI Search results, regardless of t glide.ui.allow.field.dependency.for.templates This property allows the configuration of field dependencies during the application of templates, impacting ho glide.ui.allow_ie_compatibility_mode This property allows Internet Explorer to enter compatibility mode, which can improve functionality for older glide.ui.alm_ai_dataset_digital_asset_activity.fields This property configures the specific fields that appear in the activity stream for the AI Dataset Digital Ass glide.ui.alm_ai_model_digital_asset_activity.fields This property configures the fields included in the activity stream for the AI Model Digital Asset table, affe glide.ui.alm_ai_prompt_digital_asset_activity.fields This property configures the fields that appear in the activity stream for the AI Prompt Digital Asset table,

All 714 properties in glide.ui →