Create and use a scenario

Create a scenario when you want to prepare changes without immediately modifying their source. Give it a recognizable name and check its context before editing assets or visualizations.

Check availability

You need an Editor account or higher, permission to create scenarios and an available place in the organization's scenario quota. Your plan must include scenarios, and an administrator must have enabled them.

The quota is shared across the organization. Scenarios still being prepared already consume a place. If creation is unavailable, ask an administrator to check these conditions; creating another account does not provide a separate quota.

Create a working copy

1. Open Data context in the navigation.
2. Choose New scenario to start from real data.
3. Check Branched from in the dialog. To branch from an existing scenario, use its Actions > New sub-scenario instead.
4. Enter a name that describes the hypothesis, such as “Application consolidation — option A”. Add an optional description explaining its purpose.
5. Choose Visibility. Organization is the default; choose Private to restrict access and select members under Share with. Optionally select Editors under Can apply to delegate application.
6. Click Create and wait for preparation to finish.
7. If the context has not switched automatically, open the selector and choose the ready scenario.
8. Confirm that its name appears in the navigation before making changes.

The name is required and accepts up to 300 characters. The description accepts up to 2,000 characters. A large copy may continue preparing after the dialog closes; it cannot be opened until ready.

Selecting New scenario creates a branch from real data even when you were viewing another scenario. The displayed Branched from source is the reference to check.

Sharing a private scenario grants access to the scenario, subject to existing data permissions. It does not delegate application rights. Set Can apply during creation or later through scenario sharing. In a private scenario, selecting someone under Can apply also adds them to Share with.

Work with assets and visualizations

Use the usual inventory and asset procedures in the scenario context. You can change properties, prepare relationships and inspect the resulting visualizations. Required values, uniqueness constraints and permissions still apply.

Open a visualization in the intended context before modifying it. Follow that editor's normal saving behavior: some editors save automatically, while others require an explicit save. Wait for saving to finish before leaving.

For example, change an application's planned status and update its relationships in the scenario. Then open a diagram in that same context to explain the target organization. Merely opening the diagram does not apply the asset changes.

A scenario export reflects the selected context; it does not apply changes. Keep its context clear when sharing the resulting file.

Find what you changed

In tables that offer it, enable Scenario changes only to focus on changed items. This returns the table to its first page. The filtered table is not a complete list of every transferable operation.

Open the scenario's Actions menu and choose Apply, Copy or View changes, depending on your access. The review brings together asset, relationship and visualization changes.

Use comparison to distinguish your scenario changes from changes made in the source since branching. If the source has evolved, assess whether to resynchronize before continuing.

Return to real data

1. Save unfinished work in the current editor.
2. Open Data context.
3. Select Real data.
4. Check the navigation label, then reopen the relevant asset or visualization.

The scenario remains available with its saved changes. You can select it again later. Reloading the browser alone does not reset the context.

To transfer the changes, follow apply and undo. To free an active place without applying changes, review archiving and reactivation.