Dealing with Lost Objects in TOSCA
This Article describes how to deal with Lost Objects in Tosca (which can for example lead to errors during repository migration)
Situation
What is a Lost Object
An object that is no longer attached to the object tree because it has lost the relation to its parent object.
That means it can no longer be addressed regularly but still exists otherwise.
How do Lost Objects occur
The most common situation is that Lost Objects are created via a "Revoke Checkout" and subsequent deletion of an object.
Lost Objects normally exist locally but can also be transferred into the Common Repository if the affected object was changed or newly created.
Solution
Checking Lost Objects in again
To connect Lost Objects with the object tree again the following steps need to be done:
1.)Search for Lost Objects in the Repository via the context menu on the Project Root: Search all --> Lost Objects
2.)If the object is still checked out it can either be checked in again via its respective Workspace or optionally it can be resetted into its original checked in state via "Revoke Checkout" (in this case changes are lost though)
3.)After all Lost Objects are checked in again they can be checked out once more and attached back into the object tree via drag & drop. (or deleted)
To connect Lost Objects with the object tree again the following steps need to be done:
1.)Search for Lost Objects in the Repository via the context menu on the Project Root: Search all --> Lost Objects
2.)If the object is still checked out it can either be checked in again via its respective Workspace or optionally it can be resetted into its original checked in state via "Revoke Checkout" (in this case changes are lost though)
3.)After all Lost Objects are checked in again they can be checked out once more and attached back into the object tree via drag & drop. (or deleted)