Hi Manal,

 

There are couple of use case which I can think of wherever we want to restrict it the Glide Record object.

Lets consider a simple scenario where I have custom table which holds the configurations and script which is required in order to drive certain logic in my scripted rest API.

So I have created a function which will expose the Glide record for configuration which then can be used to drive further logic based on the Glide Record information.

Now this Glide  Record is vulnerable to the updates if any one updates the configuration by mistake.

So I will make the Glide Record read only so that they can access the information to drive the process but cannot update the base configuration which makes it error prone.

 

Hope it answers your question.

 

Regards,

Amit Gujarathi

(Technomonk)

 

Technomonk Youtube: https://www.youtube.com/c/TechnoMonkAmit

Amit Gujarathi Linkedin: https://www.linkedin.com/in/amit-gujarathi-98632a175

TheTechnomonk.com : https://thetechnomonk.com/

ServiceNow Community Amit Gujarathi: https://www.servicenow.com/community/user/viewprofilepage/user-id/265565

GitHub: https://github.com/amigujarathi