Performing User Tasks › How Generating Elements Works › How Generating Elements Affects the Signout Status

How Generating Elements Affects the Signout Status

Your CA Endevor SCM administrator can enable a signout capability on a system-by-system basis. When you create an executable form of an element using the Generate Elements action, CA Endevor SCM performs the following actions and causes these effects:

• If the element exists up the map (with copyback), a fetch is performed.
  • If your CA Endevor SCM administrator has 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 out to you.
  • If your CA Endevor SCM administrator has not enabled Signout Upon Fetch, there is no change in the signout status, and the target element is signed out to you.
• If the element does not exist up the map (without copyback), a fetch is not performed.
  • If your CA Endevor SCM administrator has enabled Signout Upon Fetch, there is no change in the signout status of the target element.
  • If your CA Endevor SCM administrator has not enabled Signout Upon Fetch, there is no change in the signout status of the target element.

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