Handbook

Studio 301 — Advanced

Optional power-user workflows in Forge Studio: getting the most from embedded views, staying aligned with Classic, and understanding limitations of local builds.

What it is

Optional power-user workflows in Forge Studio: getting the most from embedded views, staying aligned with Classic, and understanding limitations of local builds.

When to use it

After Studio 201, when you are tuning how you work across Studio and Classic or hitting edge cases.

Prerequisites

Advanced scenarios

Scenario Suggested approach
Chart empty in Studio Verify the same project in Classic first; refresh Studio
Conflicting status Pick one surface for status meetings; reconcile before switching
Large workspace slow after restart Wait for scan idle before deep navigation

Limitations and fallbacks

Limitation Fallback
Classic route not in Studio yet Use Classic at / for that report
Experimental Studio feature unstable Same task in Classic until your build catches up

Steps

  1. Charts and data views — Studio may show chart or summary views that mirror what Classic exposes. If a view looks empty, open the same project in Classic and confirm data appears there first, then return to Studio and refresh.

  2. Compare Classic vs Studio — Use Classic when you need a route or report that Studio has not replicated yet; use Studio for newer flows. Keep one source of truth for status (same workspace root, same project selection).

  3. Performance and stability — Large workspaces: give scans time after restart; avoid flipping workspace roots while Studio tabs are mid-request. If the UI stalls, reload the page after the server is idle.

  4. Limitations — Not every Classic route exists in Studio yet; some features remain experimental. Prefer the surface that matches your task rather than forcing an unsupported path.

How to verify success

  • You can complete your advanced workflow without blocking day-to-day use, or you know to fall back to Classic for a specific gap.

What to do next