When to have to constantly switch between 5+ scopes to implement a module...how are you dealing with

corbettbrasing1
Mega Guru

We are implementing Security operations and am finding that we constantly are having to switch between scopes all the time, and sometimes 5 or more.

 

Sec Ops has in its scope..

- Security Incident Response

- Security Incident Response UI

- Service Order (Global)

- Threat Intelligence

- Threat Intelligence Common

..and many many more.

 

We are deploying using the internal app repo (which helps immensely) but I am just curious how everyone is dealing with this reality which is becoming more and more the case.  

 

Any tips and tricks?

1 REPLY 1

Hayo Lubbers
Kilo Sage

The same indeed for the GRC environment.

What eases the pain a bit is using SN Utils browser plugin and enabling the "Allow saving metadata after scope has changed." in the settings. At least you don't get the error message stating your scope has changed in another tab and the record couldn't be saved.

We used batch update sets, which can have children from other scopes, instead of the app repo.