Stat 6.1 - User Guide

To unlock or release a reservation for an object, select it in the Object List, click Unlock, and save the CSR. Do not remove an object after you modify it. If you remove it, it is removed from all archive sets in the CSR and Stat cannot accurately report on changes to the object.


	NOTE: All objects associated with a CSR are automatically unlocked when the CSR changes to a closed-type status.

You might unlock an object if you want to release the lock on a particular object but also keep the CSR open. This may occur when another developer needs that object immediately, or when you have many objects locked and have finished working on some of them.

Until the Stat Central Agent unlocks the object, the CSR still has the object locked. It appears in the window that you no longer have the lock, but if another user attempts to lock the object, that user will receive a reservation. The Lock summary window for the object will show that your CSR still has the lock.

Re-Prioritizing Reservations

Stat normally processes reservations on a first in, first out basis, meaning the first CSR to request a reservation on an object is the first CSR to obtain a lock when the object becomes available. However, Stat lets you move your reservation to the head of the queue if necessary. This is called re-prioritizing. Access to this feature is usually limited to users responsible for managing development projects.

To re-prioritize object reservations:

Select the objects and click Reprioritize....

Stat displays a message box telling you that the re-prioritization is complete.

Click OK in the message box.

Stat moves the objects to the first reservation position in the selected environments.


	NOTE: Stat re-prioritizes the reservation for an object only in the environment in which you selected it. If you want to re-prioritize a reservation in multiple environments, make sure you select the objects in each of those environments.

Assigning Objects to a Different Developer

To assign an object to a different developer:

Select the object(s) in the object list.

In Assigned To field, select the developer you want to assign the object(s) to.

Click Reassign.

If you are reassigning a file object and the Copy to Working option is selected, Stat prompts you to specify if you want to copy the file object to the new developer’s working directory, and if so, whether to copy the file either from the original developer’s working directory or from the base environment’s source file location.

Select the options you want and click OK.

Save the CSR.

Stat updates the Assigned To field in the object list with the new developer's user ID. The new developer now has the lock on the object(s).


	IMPORTANT: You must save the CSR before the reassignment can take effect

Removing Objects from a CSR

To remove objects from a CSR, select them and click Remove.


	NOTE: You should remove an object only if it was added to the CSR in error. Modified objects should remain associated with a CSR for historical purposes.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação

Selecione seu produto:

Para podermos atendê-lo melhor, informe o Propósito de seu chat:

Soluções recomendadas para seu problema

Stat 6.1 - User Guide

Unlocking or Unreserving an Object

Re-Prioritizing Reservations

Assigning Objects to a Different Developer

Removing Objects from a CSR