The Object Management tab displays information pertaining to object development within PeopleSoft. From here, you can view information regarding all the environments in a migration path as well as create and migrate object archives. For more information, see .
This Object Management tab is divided in two sections. The left section is a tree view showing all of the possible groupings of the information that appears on the right section of the tab. The tree allows you to navigate through the objects associated with the CSR as well as all the archives created for the CSR.
The buttons located on the top of the tap page, Environment Info and Archive Sets, control what type of information you see in the right section of the tab. When you click Environment Info, the window displays object information. When you click Archive Sets, the window displays object archive information.
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 PeopleSoft, the All Objects node sorts objects in the CSR by PeopleSoft proprietary object and file object types. When you select one of these nodes, the Environment Info table is filtered to show only objects of the selected type. 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 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 environment then the column displays a reservation icon.
Displays the name of the object. For a PeopleSoft proprietary object, this is usually the common identifier, such as the name of a page. In the case of a file object, such as a COBOL program, this is the file name.
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 environment.
For PeopleSoft proprietary objects, this column displays the name of the PeopleSoft environment that was the source of the object archive. For file objects, the column displays the environment as well as the exact file location from which the archive was taken.
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.