Landscapes
What is a landscape?
A landscape is the parent object for:
The shared model (Domains, Objects and connections)
Set of diagrams
Tags & flows
Consider a landscape to be the world you work in, referencing everything that interacts with each other in the real world - These should all be in 1 landscape.
When to split a landscape
We recommend staying in 1 landscape as much as you can
The power of a landscape is the shared model, diagrams that can be drawn from the model and syncing updates across the whole landscape.
There are, however, a few reasons you may want to split out your landscapes. For example:
There is a clear separation of systems and they never/rarely interact
Regulatory reasons - keeping teams/people separate
Consultants - Separating customer-specific designs to share with them
Sandbox - Duplicating to "play" with the design or play with the features of IcePanel
Objects in separate landscapes are not linked in any way, so if you reference a system from another landscape, we recommend that you use the "External system" setting, so people know not to add the main details here. Updates will not be reflected if you edit these referenced objects.
Large or complex systems?
If you are finding that you are struggling to organize your model because of a large and complex architecture (i.e hundreds of apps/stores and many diagrams), we recommend using Domains to split out your systems into logical business areas.
These systems and child objects still remain in a single model, can be shared and synced from other domains, but it reduces the amount you seem on the diagrams and model view. This allows you to focus your conversations and sections of your model to business areas, logical system groupings, segregation of external and internal systems etc. with the reusability of a model.
Duplicating a landscapes
For the most part, we recommend using 1 landscape - as explained above.
If you need to copy, here's how you can duplicate an existing landscape:
Duplicating a landscape in the same organization
If you want to copy your work in the same organization, follow these steps:
You need to be an admin user to do this
Navigate to the overview screen.
Click the landscape dropdown at the top left of your screen.
Select the
...
menu next to the landscape you want to duplicate.Select Duplicate landscape.
You will auto-navigate to the duplicate landscape.
Your duplicate landscape name will have the word "Duplicate" at the end.
Moving or duplicating a landscape to another organization
If you want to move your work to someone else's organization, follow these steps:
You need to be an admin user in both organizations to do this
Be invited to the other organization you want to copy your work to.
Ensure you are an admin user in both organizations.
Navigate to the overview screen of where your landscape lives.
Click the landscape dropdown at the top left of your screen.
Select the
...
menu next to the landscape you want to duplicate.Select Duplicate to organization.
Select the other organization and click Duplicate.
You will auto-navigate to the duplicate landscape and other organization.
Your duplicate landscape name will have the word "Duplicate" at the end.
Merging landscapes
You need to be an admin user to merge
Merging landscapes in a single organization
Navigate to the overview screen.
Click the landscape dropdown at the top left of your screen.
Select the
...
menu next to the landscape you want to duplicate.Select Copy model/diagram between landscapes.
Select the landscape you wish to merge with.
Click Copy.
This adds the landscape as a new Domain. You will then be able to move the object(s) from this new domain to where it makes sense in your merged landscape.
Merging landscapes across organizations
Follow these steps: Duplicate the landscape to another organization.
Then follow these steps to Merge landscapes.
Merging a single object
Currently, we do not support single-object moving between landscapes, only landscape based moving. However, if you want to, say, move 1 system to another landscape, including the objects inside, you can use this workaround.
Follow these steps: Duplicating a landscape in the same organization
Navigate to the Model objects list.
Select all objects (
CMD
+A
orCTRL
+A
).Deselect the objects you want to move.
Use the
...
menu to delete the remaining selected objects.Confirm the deletion (If it's a large model this might take time).
if you see some objects that should have been removed, try refreshing the browser and see if they. are still there.
Then follow these steps to Merge landscapes.
Merging a single object from 1 landscape to another
Currently, we do not support single-object moving between landscapes, only landscape based moving. However, if you want to, say, move 1 system to another landscape, including the objects inside, you can use this workaround.
Follow these steps: Duplicate the landscape to another organization.
Navigate to the Model objects list.
Select all objects (
CMD
+A
orCTRL
+A
).Deselect the 1 object you want to move.
Use the
...
menu to delete the remaining selected objects.Confirm the deletion (If it's a large model this might take time).
if you see some objects that should have been removed, try refreshing the browser and see if they. are still there.
Then follow these steps to Merge landscapes.
Last updated