Instances & Context
Working Context (scope + Update Set)
The extension mirrors the ServiceNow header: your application scope and your Update Set are two independent pickers, with per-scope memory and a push guard.
Your application scope (apps.current_app) and your Update Set (sys_update_set) are two independent settings, shown as two pickers in the Control Panel and in the working-context status bar (scope · update set) — the active instance is shown separately by the profile status bar.
- Select Application Scope sets the current application (Global is always available). The Update Set field then filters to that scope.
- Per-scope memory: each scope remembers the Update Set you last used in it. When you switch scope — or load the workspace — the extension reflects that scope's Update Set automatically (falling back to the most recent in-progress / Default of the scope). This avoids the "scope X with an Update Set from another scope" mismatch.
- Refresh Working Context re-reads and re-aligns everything from the instance — handy after you change scope/update set directly in the ServiceNow browser UI.
Push guard
Before every push, the extension compares your active Update Set with the widget's scope and blocks the push when:
- The active Update Set is Default, or
- The Update Set's scope differs from the widget's scope
The block message includes a "Select Update Set" button. The status bar turns red for Default / no Update Set and amber on a scope ↔ Update Set mismatch.
Make it advisory instead of blocking
The guard is configurable via
enforceWorkingContext (default true; false = warn only). See Configuration.