Offline Mode & Snapshot import

Offline Mode lets you work on a Pod’s rules with no connection to Oracle at all. Instead of Pulling from the Pod, you Import a Snapshot, the EPM Migration (LCM) zip, from disk, and the extension writes the same workspace it would have written from a live Pull: rule files, envelopes, sync state, and the application caches that power dimension and member intelligence.

This is the floor capability the product was founded on: on a plane, behind a client VPN, or inside a locked-down network, an EPM Developer still gets full calc-script intelligence, Metadata context, and native editing.

What works offline

• Full workspace structure: every rule as a native .groovy / .csc file.
• Groovy and calc-script intelligence: completion, diagnostics, hover, formatting.
• Cross-artifact Full Application Intelligence: %Template / %Script expansion and find-references across the imported artifacts.
• Dimension and artifact viewers, and member completion and validation, from the App Core data in the Snapshot.
• BYO-AI: Copilot, Claude Code, or Codex editing the rule files directly.

The live verbs (Pull, Push, Deploy, Execute) stay unavailable in Offline Mode. The round-trip to Oracle is a manual copy-paste until the Pod is given a real URL and credential.

Import a Snapshot

You do not need an existing Pod Folder for the first import:

1. Click the EPM Workbench icon in the Activity Bar, then click Add Pod….
2. Choose the EPM Workbench Root and, if you like, enter a Label and Pod Icon.
3. Under Connection, choose Offline.
4. Click Choose Snapshot… and select the Snapshot zip on disk.
5. Review the application, Domain, service instance, and plan types read from the Snapshot.
6. Click Save & Sync Later. In Offline onboarding, saving creates the Pod Folder and imports the selected Snapshot immediately.

After the Offline Pod exists, EPM Workbench: Import Snapshot from File can import a newer Snapshot into the selected Pod. Both paths run entirely locally, with no Oracle connection, credentials, or network. Import is distinct from Pull because the Snapshot comes from a file on disk instead of an Oracle export.

Working air-gapped, or converting later

A Pod configured for Offline Mode has "connection": "offline" in its pod.json and carries a non-authoritative, editable URL synthesized from the Snapshot (a Snapshot names the Domain and service instance but no reachable host).

When you later have a URL and credential, converting an offline Pod to a connected one is an edit in the Pod editor (add the URL and credential and switch the connection mode), not a migration. The first live Pull then reconciles your imported files against the real Pod.

Note

The sync state written on Import is optimistic: it assumes what you imported matches the Pod. Because the Snapshot may not have come from the live Pod, the first Pull against the real Pod is the honest comparison and surfaces any differences.