Working with life cycles is an iterative process. Like version-controlled objects, iterated objects are checked in and out of shared locations; however, unlike version-controlled objects, they cannot be revised. Instead, any change to an object creates a new and separate iteration when it is checked in. Earlier iterations, which may still be in use, are unchanged and unaffected by the new iteration. Only the latest iteration is available for new uses.

To make changes to a life cycle template, you must check out a copy. While it is checked out, no one else can check out a copy, but the original can be viewed or selected to manage an object. When you have completed changes to the checked-out copy, you must save it and check it in, so it is available to others. It then becomes the latest iteration.

Objects that are being managed by an earlier iteration continue to be managed by that iteration. They are not affected by the newer iteration.