Fields from Extended Table Not Available in UI Policy ActionsIssue When creating a UI Policy on a scoped application table that extends another table (e.g., task), fields from the parent table are not available for selection in UI Policy Actions.SymptomsUI Policy is created on a scoped application table.The table extends from a parent table (e.g., task).Fields from the parent (extended) table do not appear in the list of available fields in UI Policy Actions.User is unable to apply actions such as "Hide," "Mandatory," or "Read-only" to those extended fields.Release All releasesCauseThis issue occurs when the UI Policy is being created outside the table's application scope (e.g., in the Global scope), which restricts visibility to the extended fields.Resolution To access extended fields when creating UI Policy Actions: Switch to the Correct Application Scope Navigate to the Application Picker in the top-right corner of the ServiceNow interface.Select the scoped application (e.g., Test ABC) that owns the table. Create the UI Policy With the correct scope selected, create the UI Policy.Fields from the extended table (e.g., task) will now be available in the UI Policy Actions section. Example If you are working on table x_abc_custom_table, which is part of the Test ABC application and extends the task table: Ensure that Test ABC is the active application scope before creating or editing the UI Policy.This allows access to all inherited fields from the task table.Related LinksApplication scope