Stat 6.2 - User Guide

Selecting a Migration Path

In order to associate objects with a CSR, you must specify the environment you want to copy them from. This is done in the Migration Path tab. In Stat, migration paths are logical groupings of environments that serve as road maps for object migrations. They are set up by your system administrator.

Your system administrator creates migration paths based on your business needs. For different situations you have different paths.

To select a migration path:

Open a CSR and select the Migration Path tab.

Click the Select Migration Path field and select the appropriate migration path. The displayed paths vary, depending on the service domain.


	NOTE: If a workflow that specifies a migration path is assigned to the CSR, that path cannot be changed. For more information on workflows, see CSR Workflows . For more information on migration paths, see Migration Overview .

In the Select Default Developer field select the developer you want assigned to the objects by default.

You can assign different developers to different objects, but this is the person to which most of the object will be assigned.

(Optional) If you want to associate the CSR with a version control management system (VCM) record, select the record you want in the VCM Repository field

This field is enabled only if your system administrator has defined at least one VCM record in the VCM Connection Maintenance table. It lists all the currently defined VCM records. After you add objects to the CSR, this field is disabled and you cannot select a different VCM record.

Click Generate Path.

Stat displays a graphical representation of the migration path. Also, the Objects and Object Management tabs appear.

Each drum represents a PeopleSoft environment. Your system administrator determines which environments are designated as Base and Development. The original, “pre-change” archive of the objects in the CSR is taken from the Base environment. The Development environment is where you change the objects.

After selecting a migration path, select the Objects tab.

Assigning Developers

Before adding the objects to the CSR, you need to decide which Stat user is going to be making the changes to the objects and therefore needs to be assigned the object lock. If the user is the default user in the Assigned To field, then you can just add the objects and the default user will obtain the lock. If another user needs the lock on the objects, select that user from the drop down list in the Assigned To field. When you add the objects, the user in this field is assigned the object locks. See The Object Locking Process .

Selecting Objects

You can select the objects you want to add to your CSR manually, or you can use the various wizards to select groups of objects. The procedure for manually selecting the objects you want to associate with your CSR is slightly different depending on the class of objects.


	NOTE: Workflows can contain status rules that do not allow users to add or lock objects while the CSR is in a restricted status. When this is the case, Stat prevents you from adding or locking objects until the CSR changes to an unrestricted status. Any object reservations that were in place before the CSR was transferred to a restricted status, however, are treated the same, meaning they are converted into locks when the objects become available.

Selecting PeopleSoft Proprietary, Data, and Schema Objects

To select a PeopleSoft proprietary, data, or schema object, first select the PeopleSoft environment, then the object class and the object type.

To select a PeopleSoft proprietary, data, or schema object:

In the CSR window, select the Objects tab.

In the Environment field select the environment that contains the objects.

Note that only the active environments on the migration path are listed. If you need to select objects from an inactive environment, see your system administrator.

The initial object snapshot, the base archive set, always comes from the Base environment. No matter which environment you select in the Environment field, Stat archives the objects from the Base environment. Even if you add objects later, they still come from the Base environment.

Stat gives you this option of environments in order to reduce the number of hits made against your Base, or Production, environment. By selecting another environment, Stat connects to that environment and retrieves the list of objects. Once the objects are selected, the “pre-change” object snapshot is created from the Base environment.

When you select an environment, the Object Type field displays a “Loading...” message. During this time, Stat connects to the selected PeopleSoft environment and checks which object types are available.


	TIP: If Stat returns a large number of objects, you can quickly locate the particular object you want by typing the first few letters of the object name in the Quick Filter field. As you type, Stat filters the list of objects so that only objects with matching names are displayed.

In the Object Type field, select the type of object you want.


	NOTE: If you are adding a schema object type, Stat displays the Select Schema Owner window, which prompts you to specify the object’s schema owner. This reduces the amount of time it takes for Stat to return the list of matching objects. The window includes a Quick Filter field which lets you quickly parse the list to the schema owner you want (including Public). Select the owner and click OK.

Stat displays object types sorted by object class. When you select an object type, Stat displays a list showing all available objects of that type.

In the list of objects, select the object(s) you want. To select multiple objects, hold down the <Shift> or <Ctrl> key as you make your selections.

Selecting File Objects

You can select file objects residing in either a PeopleSoft environment or the assigned developer’s working directory.

To select a file object:

In the Environment field, do one of the following:

•

Select an environment if you want Stat to look through that environment’s source file locations to get the list of file names for a particular file type. Source file locations are the file server directories where file objects reside. You or your system administrator can define multiple source file locations for each environment.

•

Select Working Directory if you want to add files that exist in the assigned developer’s working directory but not in any of the environments to which Stat has access

•

Select VCM Repository if you have associated the CSR with a VCM record and you want to archive and migrate objects that reside in the VCM repository

Note that any environments on the migration path that have been inactivated are not listed. If you need to select objects from an inactive environment, see your system administrator.

In the Object Type field select the type of file you want.

Stat displays a list of all the files that have the matching file extension. No file names are returned if there are no source file locations defined for the selected file type and environment, if no working directory has been defined for the assigned user, or if no matching objects reside in the VCM repository.

(Optional) Select Copy to Working.

If selected, Stat copies the files from the Base environment to your working directory after adding them to the CSR.


	NOTE: This option is selected by default if the Copy Files to Working check box is selected in the Stat User Options window. For information on user-defined working directories, see Defining Working Directories for File Objects .

In the list of files, select the file(s) you want.

Filtering the Object List

If you have added a large number of objects to a CSR, you can filter the list of objects so that only the objects you want to view are visible. You can then save the filter settings so that the object list remains filtered the next time you open the CSR.

To filter the object list:

In the Objects tab, click Filter.

This opens the standard Specify Filter dialog box

Create a filter equation using the Operator tool buttons and statements listed in the Functions and Columns fields.

Click Verify to check the validity of your equation.

Stat displays a message box telling you if your equation is valid or not.

Click OK.

The Objects tab now displays a “Filter On” notification and the number of objects currently hidden by the filter. Any objects you add to the CSR while a filter is on may be hidden from the list of objects.

Optionally, if you want to save the filter for the next time you open the CSR, select the Save Filter option.

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 (PeopleSoft) .

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


	IMPORTANT: When you add an object to a CSR without a lock, Stat does not create a base version for the object or mark the object as having been modified. The object is 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.


	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.

Seleccione su producto:

Con el fin de ofrecerle un mejor servicio, complete el campo Motivo del chat:

Soluciones recomendadas para su problema

Stat 6.2 - User Guide

Selecting a Migration Path

Assigning Developers

Selecting Objects

Selecting Lock Options