Hey @Advaitk
For SCTASK variable editing, you need both:
Write ACL access
Client-side logic to remove read-only state
Solution
Create Write ACL
Table:
sc_item_variables_task
Operation:
write
Script:
answer = current.task.assignment_group &&
gs.getUser().isMemberOf(current.task.assignment_group);
This allows users from the task assignment group to update variables.
Display Business Rule on sc_task
(function executeRule(current, previous) {
g_scratchpad.canEdit =
gs.getUser().isMemberOf(current.assignment_group);
})(current, previous);
onLoad Client Script
function onLoad() {
if (g_scratchpad.canEdit || g_user.hasRole('admin')) {
g_form.setReadOnly('variables.variable_name_1', false);
g_form.setReadOnly('variables.variable_name_2', false);
}
}
Important Notes
Admin works because ACLs are bypassed automatically.
Without the sc_item_variables_task write ACL, non-admin users will always see variables as read-only.
Also verify that:
Variable itself is not marked Read Only
No Catalog UI Policy is forcing read-only
No other Client Script is resetting the field state
One additional improvement:
In some cases, variable fields on SCTASK behave inconsistently with individual setReadOnly() calls. You can also try:
g_form.setVariablesReadOnly(false);
and then selectively make required variables read-only again if needed.
*************************************************************************************************************************************
If this response helps, please mark it as Accept as Solution and Helpful.
Doing so helps others in the community and encourages me to keep contributing.
Regards
Vaishali Singh
Servicenow Developer
Linkedin - https://www.linkedin.com/in/vaishali-singh-2273361bb
