Variable Editor variables cannot be set to Read-Only via Client Script or UI Policy on extended Cust

[Henrique_sch]

Context: We have created a custom task table (x_odsa_demanda_op_demanda_task) that extends the native task table. This custom table is inside a Scoped Application (Demanda OdontoPrev). We use the Catalog Builder Formatter (Variable Editor) to pull service catalog variables into this custom task form.The Issue:We need to make all variables inside the Variable Editor read-only on the custom task form, but all standard platform approaches fail.What we have already tested and didn't work:g_form.setVariablesReadOnly(true);: Fails silently. It seems this API is hardcoded to only work on out-of-the-box tables like sc_req_item and sc_task, ignoring extended custom task tables.Catalog UI Policies / Catalog Client Scripts: Even with "Applies on Catalog Tasks" checked, the rules do not trigger or map correctly when rendered inside this specific custom task table.DOM Manipulation Scripts (document.querySelectorAll, etc.): Completely blocked by Scoped App security guidelines, throwing Cannot read properties of null (reading 'querySelectorAll') in the browser console (even with Isolate Script = false).g_form.getEditableFields() and g_sc_form APIs: Do not return or recognize the Formatter fields (IO:sys_id) on this extended table context.Request:Is there any Out-of-the-Box property, specific macro configuration, or standard API that enables g_form.setVariablesReadOnly() to work seamlessly on custom task tables inside Scoped Applications? How can we lock these variables dynamically without hitting scope security barriers?