Understand real data and scenarios
A scenario is a working copy where you explore changes before deciding what to transfer to its source. Use it to compare options, prepare a transformation or review several related changes together.
Understand the source and the copy
A top-level scenario starts from Real data. A sub-scenario starts from its parent scenario. That direct source remains the destination when you apply changes.
For example, create a scenario to study replacing an application. Change its properties and relationships, then adjust a diagram to explain the planned transformation. These saved changes remain in the scenario until you apply them.
The copy includes assets and relationships, including archived ones, as well as visualizations, processes, visualization versions, comments and suggestions. Copying these resources does not mean they all transfer back when you apply the scenario.
Pending creation suggestions from the source are not copied. You can suggest new assets inside the scenario and have them approved there. The created asset belongs to that copy; transferring it to the source then requires applying its creation change.
Organization members, roles, permissions and the metamodel remain shared configuration. A scenario does not provide a separate organization configuration. Existing data and content permissions continue to apply inside it.
Computed properties use the scenario's data. A difference marked Computed effect may therefore result from a changed relationship or input, rather than a directly edited value.
Home, guided reviews and the quality report follow the selected context. In a scenario, you can review suggestions, completeness and ownership. Attestation, re-attestation requests, reminders and departed-owner administration remain limited to real data. Freshness indicators are hidden in scenarios, but combined quality scores still include real-data freshness.
Check the active context
The navigation selector displays Real data or the current scenario's name. Open it to display Data context and choose the context you want.
- Check the organization and the name in the context selector.
- Open the asset, inventory or visualization you want to use.
- Before modifying it, confirm that the selector still names the intended scenario.
- To return to the source, select Real data, or select the parent scenario when working with a child.
Changing context does not remove saved scenario changes. Save unfinished work before switching; follow any prompt about unsaved changes.
The browser remembers your context. Reloading a page does not necessarily return you to real data. Conversely, a closed or inaccessible scenario can cause an automatic return to real data. Check the selector after such a return.
Opening a scenario visualization from a comparison can switch your working context. A side-by-side comparison reads each side in its own context; it does not merge the two visualizations.
Choose the operation you need
| Operation | What it does |
|---|---|
| Overview | Reads differences between the scenario and a source or another available scenario. |
| Resynchronize | Refreshes the copy from its current source, then replays the scenario's changes. Conflicts may require a decision. |
| Apply | Transfers selected changes to the direct source. Unselected changes remain in the scenario. |
| Copy | Copies accepted changes into another scenario you manage, through the same review as an application. They also stay in the original scenario. |
| Undo an application | Attempts to reverse selected applied changes while preserving later work that prevents reversal. |
Source content changes do not automatically refresh an existing scenario. Attestation information is an exception: real-data attestations and re-attestation requests immediately update existing scenario copies. Compare and resynchronize when the source evolves. Choosing a different comparison target does not change the application destination.
When application closes a scenario completely, comments created in the scenario are not transferred. Its new pending suggestions are not promoted to the source. Source suggestions accepted in the scenario have specific closure effects.
Understand access and management
Scenarios must be included in your plan and enabled for the organization. An accessible scenario must be active and ready before you can work in its copy.
| Action | Required access |
|---|---|
| Read | Access to the scenario and its data. A Viewer can consult an accessible scenario. |
| Create | Editor or higher, personal permission to create scenarios and room in the organization's shared quota. |
| Edit data | Access to the scenario and permission for the corresponding assets, properties, relationships or visualizations. |
| Manage | Editor or higher and scenario creator, organization Administrator or organization Owner. |
| Apply | Scenario manager, or an Editor designated under Can apply, plus destination data permissions. |
| Undo | Scenario manager; Can apply alone is insufficient. |
Applying a child scenario or undoing its application also requires management access to its active, ready parent.
Sharing a scenario does not grant permission to read or modify all its data. Private restricts its audience, but organization administrators retain access. See sharing and lifecycle before inviting collaborators or closing a branch.