The highest-level tree node is the CSR node. When you select this node, all of the objects associated with the CSR appear in the Environment Info table. Second level tree nodes include All Objects, Migration Path, and Developers. For generic applications, this node includes all the file objects associated with the CSR.
The Migration Path node sorts objects by the environments on the migration path. The first node is the Base environment, the second is the Development environment, and the remaining nodes correspond to the additional environments on the migration path. When you select an environment node, the list shows the objects in that environment. The Developers node sorts objects according to their assigned developer. When you select a developer node, the list on the right shows only the objects assigned to that developer.
The Archive Sets button becomes activated when you select any object or developer tree node. If the Archive Sets toggle button is active and you select one these nodes, the Environment Info toggle button automatically becomes active. This is because archive set information is not specific to these nodes and therefore cannot be filtered.
Click Refresh Tree to refresh the tree view if there are changes to the CSR, such as an object reassigned to a different developer or a newly added object.
When you click Environment Info, the Environment Info table appears in the right section of the tab page. This table displays information concerning versions of each object residing in each environment. Click the column headings to sort the rows of information in the Environment Info table.
Indicates if the object is locked or reserved for the particular environment. If the object is exclusively locked by this CSR then the Status column displays a lock icon. If the object is reserved for the particular database then the column displays a reservation icon.
The environment in which the object resides. For each file object in the CSR, the Environment Info table displays an additional row to represent the archiving and migrating activities in the user’s working directories. For these rows, the Environment column displays the value “Work.”
Displays the user name of the Stat user assigned to the object and therefore has the lock on the object. This does not have to be the same user who owns the CSR, and it can vary by object and database.
Stat is an effective source of information about the changes made to an object, but only if they are properly documented. Many processes are automated by Stat, but it is still the responsibility of developers to document their changes.
All information pertinent to a change should be readily available from the CSR. There are several areas in a CSR where you can document your changes. For instance, you can document the reason for the change in the Description tab. The information entered in the Description tab can be standardized through the use of templates. Other places to store pertinent information, such as affected modules and technical specifications, are the Detail Logs tab, the Resolution tab, and the Task/Time tab. You can also add external documents like test scripts to a CSR by inserting hyperlinks.
More object-specific information is documented in the Object List table of the Objects tab, which shows all objects associated with a CSR. The Object List table shows such information as the lock status and object type, the environment in which it is locked or reserved, the assigned user, and the date when it was last modified. You can also read any comments attached to an object and access migration paths.
To sort information in the Object List, click a column heading to have the rows sorted based on that column, or click Sort. This opens the Specify Sort Columns dialog box, in which you can specify a sort order based on multiple columns.
Indicates the name of the object. This is usually the common identifier for the object in PeopleSoft, such as the name of a page. In the case of a file type object, such as a COBOL program, this is the file name.
Indicates whether or not a locked object has been modified. Initially, the field displays the value PND prior to the Stat Central Agent locking the object and determining its modification status. If for any reason the agent cannot add the object to the CSR, it returns a value ERR.
A file object has a modified status of Unk for each environment that contains the file object in at least one of its source locations. For each environment that does not contain the file object in any of its source locations, the file object has a modified status of New. Data objects have the same modified values as file objects, meaning it displays the status Unk if it does exist in an environment and New if it does not exist.
The last date and time that changes were made to this object in Stat, followed by the name of the user who made the changes. If the record was last modified by the Stat Central Agent, the user ID defaults to “SYSTEM.”