Chat now with support
Chat with Support

We are currently experiencing issues on our phone support and are working diligently to restore services. For support, please sign in and create a case or email supportadmin@quest.com for assistance

Stat 6.3 - User Guide

Introduction to Stat Connecting to Stat Change/Service Requests Stat Consoles Tasks and Time Entries Stat Projects Search Engines Reports and Graphs Personal Rules Object Tools and Wizards Change Management for PeopleSoft
Object Management (PeopleSoft) Object Archives (PeopleSoft) Object Migrations (PeopleSoft)
Change Management for Oracle Applications
Object Management (Oracle Applications) Patch Management Object Archives (Oracle Applications) Object Migrations (Oracle Applications)
Change Management for Generic Applications
Object Management (Generic Applications) Object Archives (Generic Applications) Object Migrations (Generic Applications)
Appendix: Troubleshooting Chart Appendix: Migration Options Appendix: User-Specific Parameters Appendix: Supported PeopleSoft Proprietary Objects Appendix: Stat Reports

Selecting Lock Options

After you select the object(s), you should decide which locking options to use. By default, the objects are set to be locked in all the environments on the migration path, but with proper security rights you can select a different lock option. For more information on object locking, see Object Locking and Reservations (Generic Applications) .

There are four different lock options:

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).
Reserve if locked – This option automatically requests a reservation if the objects are locked by another CSR. If this box is not checked and the objects are locked by another CSR, Stat prompts you for an action.

Adding Objects

After assigning a developer and selecting the object(s) and lock options you want, you are ready to add the objects to your CSR.

1
Click Add Object, or double-click on an object, or drag/drop the object to the object list window.
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.

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

The Read File, Read CSR and Read Project buttons are temporarily replaced by a message indicating how many objects are left to process.
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:

When adding an object, Stat connects to all environments or source file locations on your migration path in order to check for existence. If it finds an object that exists in another environment, but not in the environment that you are working in, it displays a warning message.

Clicking Yes adds the object to the Object List table with a modification status of New. For more information on the Object List table and modification statuses, see CSR Object Documentation (Generic Applications) .

NOTE: 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.

When the CSR is saved, the Stat Central Agent processes the object locks and determines the modification status of the object.

While the Stat Central Agent processes your object locks, the Objects tab goes into Read Only mode. During this time, if you attempt to perform any actions such as adding more objects or removing existing ones, Stat displays a warning. Once the Stat Central Agent has completed the locking of your objects, the Objects tab returns to edit mode.

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. 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 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, 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.

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.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating