Global Default Update Set Override

[davidpanson]

Hi all,

I asked a similar question last week but now I've learned more about my problem. I have both the update set picker and application picker active on my Service Now instance. Whenever I pick an application with a global scope (therefore it should switch to global update sets) my instance will switch to a global update and then immediately switch to the last non global application I had selected.

This is what I'm talking about. In this case I had the SSH application selected in the application picker. Then I went to the global application selection in the application picker. The update set should automatically update to the new scope, and it does. It switched to Default[global] but then immediately switches back to the last application selected that was not global. In this case SSH.

I've tried it out on every other instance I have access to and only one of them is behaving this way. I can't replicate the issue on my personal dev instance. I have no idea why this is happening or what to do to fix it. Does anyone have any suggestions or similar experiences?

Thanks

[Michael Fry1]

I've seen this happen on both Geneva and Helsinki. If I change the Application picker to an app I created, and there's not update set available, it creates one named Default with the app name. I was thinking I must have created my update set first, then the app, and thus the Update set isn't in the app scope.

[davidpanson]

Thanks for the reply. I am on Helsinki. But my issue isn't the creation of a default. It's sort of the opposite actually. Instead of creating a default it switches back to something else. It's almost like my update set refuses to admit global scope exists. If I try anything that would cause it to go to any update set of global scope (global default or any created application of global scope) it immediately switches itself back to the last user created app scope/update set such as in my example picture. I tried to switch to a global scope and was immediately routed to the SSH application update set because the SSH application was the last thing I had selected before global.

[BALAJI40]

Hi David,

Please read the 4th point, It will give some information regarding default update set. It may helpful for you.

System Update Sets - ServiceNow Wiki

[davidpanson]

Thanks Balaji but I don't think any of that applies to my case. In each situation listed it talks about the system creating a new default update set as required. My problem isn't the system creating a default for me. My problem is I can not get the system to use or create a global update set at all.

"If you change application scope and: Your preferred update set is Complete or Ignored and there is no In-Progress default update set for the new scope, then the system auto-generates a default update set for the scope."

My problem is basically the opposite of this is happening. When I switch to any application with a global scope my update set will not change to anything global. Or rather it does change to the default global but it reverts back to the scope of whatever was selected before immediately which prevents me from actually doing anything globally.