Stat 6.3 - User Guide

Selecting Lock Options

After you select the object(s), you should decide which locking options to use. Your ability to change locking options is determined by security settings. For more information on object locking, see The Object Locking Process .


	NOTE: It is recommended that you keep the default lock setting, All on Migration Path. Locking only in the current environment could lead to version inconsistencies if another developer modifies the same object in a different environment.

Table 1. Lock options
Option	Description
All on Migration Path	The default setting. Select this option to add and lock/reserve the object(s) in all environments. Stat searches in each environment to determine if the object is already locked or reserved on another CSR.
Current Environment	Select this option if you want to add the object from each environment on the migration path but lock/reserve the object(s) only in the current environment. Stat checks for reservations and locks/reserves the object(s) only in the current environment.
None	This option adds the object(s) to the CSR from each environment on the migration path without issuing a lock on any of them. Although you can archive an object that is not locked in an environment, you cannot migrate the object to an environment in which it is not locked. You should select this option if you are associating the object(s) to a CSR for documentation purposes only, and you are not going to make any changes to the object(s). NOTE: When you add an object to a CSR without a lock, Stat does not create a base version for the object(s) or mark the object(s) as having been modified. The object(s) are therefore considered “Undocumented” by the Undocumented Object Wizard.
Reserve if locked	This option automatically requests a reservation if the object(s) are locked by another CSR. If this box is not checked and the object(s) are locked by another CSR, Stat prompts you for an action.

Adding Objects

To add objects:

After you select the object(s), locking options, and assign a developer, click Add Object, or double-click on the object(s), or drag and drop them into the Object List field.

At this point, if you selected the lock options All on Migration Path or Current Environment, Stat connects to the environment(s) and adds the selected objects to the Object List. If Stat is unable to connect to one or more environments, it displays a warning message for each environment it failed to connect to and adds the object to the CSR without a lock.

Click Save on the Stat toolbar or select File | Save.

This enables Stat to finalize your object locks.

While the Stat Central Agent processes the locks, the Archive Sets tab goes into read-only mode and the following occurs:

•

The Read CSR button is temporarily replaced by a message indicating how many objects are left to process.


	NOTE: If the message does not go away after certain amount of time this may indicate that the agent encountered a problem or timed out.

The Workflow tab and certain CSR fields are disabled both in the Stat Windows client and in Stat Web. These include the CSR Type, Application, Status, and Workflow fields. This is done to prevent users from modifying the CSR while the Stat Central Agent is still processing data.

For each object, Stat then:

•

Verifies the object is not already on the list of objects associated with the CSR

•

Checks for any existing locks or reservations for the object by other CSRs

•

Checks for the object’s existence by searching in each source file location defined for each environment along the migration path. If no source locations have been defined for the file type in any of the environments on the migration path, Stat cannot add the object to the CSR.

•

Adds the object to the CSR and locks it

When adding an object, Stat connects to all environments on your migration path in order to verify modification status. If it finds an object that exists in another environment, but not in the environment from which you are working, it displays an advisory message.


	TIP: You can update the lock status of objects displayed in the Object List table by clicking Refresh. This will show if you any of the reserved objects have since received a lock since the last time you saved the CSR.

When Stat adds the object to the CSR, a row for each environment on the migration path is added to the Object List table. Each row displays information concerning the development, archiving, and migration activity that takes place for that object in that environment. For more information on the Object List table, see CSR Object Documentation (Oracle Applications) .

Viewing the Lock Status of an Object

From the Objects tab of the CSR window, you can identify which objects you have locked and which objects you have reserved. Quest® Stat® denotes lock and reserve status in the Flags column of the CSR object list with a lock icon and a clock icon, respectively.

To view all the locks and reservations placed on an object, right-click the object in the Objects tab of the CSR window. In the right-click menu, select View Lock Status. Stat opens the Lock summary window for the object.

This window displays a list of all locks and reservations for the object across all environments. Any reservation or lock for the current CSR is highlighted in yellow. This allows you to see, at a glance, the position of your reservation in the queue.

The window lists locks first, followed by reservations, in chronological order. Each reservation icon is followed by a number indicating its position in the queue. If no locks or reservations exist for the object, Stat opens a window indicating this.

The name listed in the Lock summary window is the developer assigned to the object in the CSR, which may not be the person assigned to the CSR. This depends on your Business practices.

Unlocking or Unreserving an Object

To unlock or release a reservation for an object, select it in the Object List, click Unlock or Unreserve, 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 keep the CSR open but you want to release the lock on a particular object. 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 Stat processes the unlock action, 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.

Selecione seu produto:

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

Soluções recomendadas para seu problema

Stat 6.3 - User Guide

Selecting Lock Options

Adding Objects

Viewing the Lock Status of an Object

Unlocking or Unreserving an Object