Performing User Tasks › How Moving an Element Between Inventory Locations Works › How Moving Elements Affects the Signout Status

How Moving Elements Affects the Signout Status

Your CA Endevor SCM administrator can enable a signout capability on a system-by-system basis. When you move an element from one inventory location (environment, stage) to the next location on a map route, CA Endevor SCM performs the following actions and causes these effects:

• If the element exists up the map, a fetch is performed.
  • If your CA Endevor SCM administrator has enabled Signout Upon Fetch, the fetched (source) element (the element at the FROM location of the action) is signed out to you, if the element is not signed out to someone else. In addition, the target element is signed in.
  • If your CA Endevor SCM administrator has not enabled Signout Upon Fetch, the fetched (source) element is signed out to you, if the element is not signed out to someone else. In addition, the target element is signed in.
• If the element does not exist up the map, a fetch is not performed.
  • If your CA Endevor SCM administrator has enabled Signout Upon Fetch, the target element is signed in.
  • If your CA Endevor SCM administrator has not enabled Signout Upon Fetch, the target element is signed in.

  Note: For more information, see Actions and Signout Status in the chapter "Action Processing" in the CA Endevor Software Change Manager User Guide.