Variables in RITM override the value even though its a read only variableIssue OOB we have a client script that sets read-only for the variable editor by the same name "Variable Editor Read-only". sc_task https://empjpagan5.service-now.com/nav_to.do?uri=sys_script_client.do?sys_id=fa5e5eea87300300e0ef0cf888cb0b46 RITM https://empjpagan5.service-now.com/nav_to.do?uri=sys_script_client.do?sys_id=2bb9da6a87300300e0ef0cf888cb0bdd But when customers have a use case to make these writable. Then you can run into an issue where two users in the same record will override. For example, one user will be on sc_task where a variable is writable in the variable editor. If this user can write on this variable changes the value. In the RITM for this sc_task, another user also has the form open but has not reloaded the page to show the new value. In the RITM the same variable is read-only and this user saves the form without reloading the page to show the new value. This will make the RITM override the value on the sc_task even though the variable was read-only.ReleaseAnyCauseThere is a KB that is similar but uses Inspect Element: KB0748975https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0748975 For this case, when the value of the variable is being changed in sc_task it's saved.But as the sc_req_item page is not refreshed/reloaded, it still shows the old value whereas the backend variable value was already updated,- clicking on save without reloading is becoming equivalent to editing an element using inspect(mentioned in KB) and the value is overridden.ResolutionThe way to resolve this issue and prevent unauthorized transactions on variables is to use the Write roles field on the variables. The following document provides additional details on this field and how to add roles to prevent this issue. https://docs.servicenow.com/bundle/utah-servicenow-platform/page/product/service-catalog-management/topic/p_ServiceCatalogSecurity.html