Team-based Development with Versioned Objects
Team-based development is the integration of the Model repository with a third-party version control system. The version control system saves multiple versions of assets and assigns each version a version number. You can check assets out and in and undo the checkout of assets.
The Model repository protects assets from being overwritten by other members of the development team. If you open an asset that another user has checked out, you receive a notification that identifies the user who has it checked out. You can open a checked out asset in read-only mode, or you can save it with a different name.
Use the My Checked Out Assets view to manage assets that you have checked out. For example, you might want to undo a checkout to delete changes to an asset.
When the connection to the version control system is active, the Model repository has the latest version of each asset.
The Model repository maintains the state of checked-out assets if it loses the connection to the version control system. While the connection with the version control system is down, you can continue to open, edit, save, and close assets. The Model repository tracks and maintains asset states.
When the connection is restored, you can resume version control system-related actions, such as checking in or undoing the checkout of assets. If you opened and edited an asset during the time when the connection was down, the Model repository checks out the asset to you.
Versioned Asset Management
When the Model repository is integrated with a version control system, you can manage versions of assets. For example, you can check out and check in assets, undo checkouts, and view assets that you have checked out.
You can perform the following actions:
- Check out an asset.
- When you check out an asset, it maintains a checked-out state until you check it in or undo the checkout. You can view assets that you have checked out in the My Checked Out Assets view. To check out an asset, right-click the asset in the Object Library and select Check Out.
- Undo the checkout of an asset.
- When you undo a checkout, you check in the asset without changes and without incrementing the version number or version history. All changes that you made to the asset after you checked it out are lost. To undo a checkout, you can use the My Checked Out Assets view.
- Check in an asset.
- When you check in an asset, the version control system updates the version history and increments the version number. You can add check-in comments up to a 4 KB limit. To check in an asset, use the My Checked Out Assets view or the object right-click menu.
- Delete an asset.
A versioned asset must be checked out before you can delete it. If it is not checked out when you perform the delete action, the Model repository checks the asset out to you and marks it for delete. To complete the delete action, you must check in the asset.
When you delete a versioned asset, the version control system deletes all versions.
To delete an asset, you can use the My Checked Out Assets view.
My Checked Out Assets View
The My Checked Out Assets view lists all the assets that you have checked out.
You can perform the following actions in the My Checked Out Assets view:
- •Undo the checkout of an asset.
- •Check in an asset.
- •Delete an asset.
To access the view, right-click an asset in the My Checked Out Assets view, and select an action.
Deleting an Asset
When you delete an asset that is under version control, you mark the asset for deletion and then check it in.
1. Right-click the asset in the Library Navigator view or the My Checked Out Assets view and choose Delete.
2. Select the asset in the My Checked Out Assets view and choose Check In.
The asset is deleted from the Model repository.