Best practice on variable editor? Make it read only or editable?

Suggy
Giga Sage

What is the Best practice on variable editor? Make it read only or editable for the IT operators who work on SCTASK?

Will there be any scenario to make it editable? We are planning to make them read only.

Looking for best practice.... Thx..

3 REPLIES 3

Murthy Ch
Giga Sage

Hi @Suggy 

You can use UI policy and make it read only depending on your conditions:

For making a variables read only you can use below code:

g_form.setVariablesReadOnly(true); //will make all variables read only

Hope it helps..

 

Thanks,
Murthy

Mike_R
Kilo Patron
Kilo Patron

It's really up to your organization. Will there be any scenarios where the technician needs to enter or change a variable? If not, then make it read only.

 

If this is a new deployment of the request module, I would definitely make it read only. And then if you start getting feedback from people that they need to edit the variables, then try to understand why they need to edit, and if it warrants making it editable, then you can make it editable.

scott barnard1
Kilo Sage

Personally I'd set the default value on the role  on all variables to admin. That way unless they are specifically changed then only full admin can change them.

You may have a specific use case where a single field is set on submit but an agent needs to change it afterwards. In this case you just add to role for the agent to the specific variable.

 

Generally speaking you don't want the variables changing from their original values. However you may have some specific use cases but if you do move away from locking them down you may need to do more in the audit and history of them.

 

Regards