2 |
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 . |
3 |
In the Select Default Developer field select the developer you want assigned to the objects by default. |
4 |
5 |
Click Generate Path. |
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 .
2 |
In the Environment field select the environment that contains the objects. |
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. |
3 |
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. |
1 |
In the Environment field, do one of the following: |
• |
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 |
2 |
In the Object Type field select the type of file you want. |
3 |
(Optional) Select Copy to Working. |
1 |
In the Objects tab, click Filter. |
2 |
Create a filter equation using the Operator tool buttons and statements listed in the Functions and Columns fields. |
3 |
Click Verify to check the validity of your equation. |
4 |
Click OK. |
5 |
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). |
• |
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. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center