The following diagram shows how a project uses an asset. In this example, the base versions of assets A and B are revised in a project and deployed to a site. The deployed version of each asset becomes version 2 of the asset in the repository.
The following list describes the stages in the lifecycle of an asset.
Add assets to a project
When you add an asset to a project, a working version of the asset is automatically created. If the asset is new, it exists only as a working asset; no checked-in version exists, and it is visible only within the project.Edit the project asset
An asset is accessible only from a project, where it can be viewed, edited and saved. Changes that you save to a working version are visible only within the project, and are not accessible to other projects.Deploy and check in project assets
Project assets are checked in to the versioned repository after deployment to the target site is complete and verified. The checked-in asset becomes the latest version that is available to projects and users. For more information, see Versioning Assets.
