Hi Community,
I am testing the new Read only option on sys_dictionary in a Personal Developer Instance (PDI).
According to the official documentation, setting a field to Strict Read Only is expected to prevent any updates from UI, Client Scripts, and Server-side APIs.
However, during my verification on a PDI, I observed that the field value could still be updated via server-side execution. Here are the test details:
[Test Configuration]
Table: custom table
Field: custom field
Read only option: Strict Read Only
[Test Results]
Background Script: Executed GlideRecord.update() without using setWorkflow(false). The field value was updated successfully.
Business Rule (before update): Set current.setValue() The field value was updated successfully.
[Question]
Does Strict Read Only only enforce restrictions on the Client/UI layer (e.g., REST API / g_form / Form submission), while bypassing GlideRecord database updates in server-side scripts regardless of user roles? Or is this an unexpected behavior/defect in the current release?
Any insights or official behavior clarifications would be greatly appreciated.
