Drop down lists not working in request items

[Community Alums]

Hello,

We have upgraded a non production instance to Fuji in order to work out all the bugs and get fixes for things that don't work with the upgrade. We went from Calgary to Fuji.

Once of the issues I have run in to and cannot figure out is why some of the drop down lists have stopped working. Particularly they don't work for a certain role, which points me to ACL's but I have tried everything I can think of and cannot get it to work and allow the dropdowns to populate with the choices.

I have attached screen shots of what I am having issues with. Anyone have any ideas? I am sure it is something simple but I am just not figuring it out.

[yetesh_ch]

Hi Kris,

Have you seen ACLs on 'sys_choice' table. Impersonate as System Administrator and go to System Security >> Access Control. Search for *sys_choice in the Name field.

[Community Alums]

I have seen the ACLs on that table. The only think I can see that may be limiting the access is this script

gs.hasRole('admin') || gs.getProperty('glide.sm.default_mode') == 'allow'

Particularly the bold part. I wiki'd the glide.sm.default_mode and it doesn't look like our instance has the high security plugin turned on as there were no options to allow or deny for the glide.sm.default_mode as it states in the wiki.

High Security Settings - ServiceNow Wiki

[manikorada]

Try to create a ACL on sys_choice and provide access to everybody and see if its fixed

[Community Alums · Accepted solution]

ok, got it figured out.

gs.getProperty('glide.sm.default_mode') == 'allow' - This is used with High Security, after reading the Wiki and bashing my head a bit I realized that the upgrade to Fuji did not carry over the High Security plug in. I activated that and retested and now the fields are visible.

Thank you for all of your help, I really appreciate it!

[coryseering]

Hi Kris,

Please get in touch with the Support team. If you had the High Security plugin before you upgraded, you should have had it afterwards. If the plugin was missing after the upgrade, that's cause for concern, because the High Security plugin is the foundation for the security model of your instance.

If you didn't have the High Security plugin before the upgrade, then it's reasonable to think that afterwards, things that assume the plugin is there won't work right. However, it seems like a Problem ticket might need to be opened, because either something is missing a dependency, or something literally went wrong during the upgrade.

No matter which way your instance was configured pre-upgrade, if something as important as your instance's security model was not configured correctly at the end of the upgrade, then that needs to be investigated.