- Get started with Linked Project Spaces
- Push content from the upstream project space
- Sync content to downstream project spaces
- Linked project space history
- Supported content
- Notable constraints
- Linked Configurations
- Edit linked configurations in the downstream project space
- Unlinking project spaces
- Supported Content Matches
Linked Project Spaces refer to the connection between an upstream project space and downstream project spaces.
The upstream project space is where the original development work takes place, including the creation of master applications and data models. Once the development work is complete, the finished product is pushed to the downstream project spaces for release.
The downstream project spaces are typically where the end-users or downstream developers access the released version of the content. The content that is pushed from the upstream project space to the downstream project spaces is linked, and is referred to as linked configurations.
This connection between the upstream and downstream project spaces is critical to the development process as it ensures that the downstream project spaces always use the latest and approved versions of the application and data models. It also allows users to sync updates from the upstream project space as needed, keeping them updated with the latest changes and fixes.
Upstream Project Space
An upstream project space is the development environment where the master applications and data models are created. These upstream project spaces are linked to downstream project spaces. When the development work in the upstream project space is complete, the content is transferred or pushed to downstream project spaces for release.
Downstream Project Space
A downstream project space is where the final or released versions of master applications and data models are deployed, such as in testing or production environments. The downstream project space is linked to the upstream project space. This allows users to sync updates from the upstream project space as needed.
Content refers to everything that is pushed or synced from project spaces. Read more about supported content here.
Data models refer to Individual components that make up the content. e.g., lookup tables, web user roles, etc. Read more about how to push data models from an upstream project space and sync data models from a downstream project space.
Once content or data models are pushed, they become linked configurations. Read more about linked configurations.
In the context of Linked Configurations, a Match refers to a situation where there are unlinked content items in both the upstream and downstream project spaces that share the same name, ID, or Label. Read more about matches.