What Are Scopes?

Scope refers to how and where certain artifacts—like variables, action chains, root pages, and more—can be used within VB Studio.

In a nutshell, where you define something determines where it can be referenced. That is, within an extension, artifacts can be scoped at different levels:

• Extension scope: Artifacts are available to all App UIs, page flows, and pages in the extension. Examples: Root pages in the Root Page folder, as well as resources in the highest-level Resources folder. In addition, anything defined through the far left ribbon in the Navigator—Layouts, service connections, components, and so on—are available to everything in the extension.
• App UI/fragment scope: Artifacts are available to all the page flows and pages in the App UI or fragment. Examples: Resources in the App UI or fragment’s Resources folder; action chains, events, event listeners, types, variables, and Layouts defined at the App UI or fragment level.
• Flow scope: Artifacts are available to only the page flow (and pages) in which they are defined.
• Page: Artifacts are defined at the page level, and thus are available to only that page.

You can also establish settings that are scoped to various VB Studio entities, which control how the entity looks and behaves:

• Extension-Level Settings
• App UI Settings
• Flow Settings
• Page Settings