Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Stat 6.2 - 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

Re-Prioritizing Reservations

Re-Prioritizing Reservations

Stat normally processes reservations on a first in, first out basis, meaning the first CSR to request a reservation on an object is the first CSR to obtain a lock when the object becomes available. However, Stat lets you move your reservation to the head of the queue if necessary. This is called re-prioritizing. Access to this feature is usually limited to users responsible for managing development projects.

To re-prioritize object reservations:
1
Select the objects and click Reprioritize....
Stat displays a message box telling you that the re-prioritization is complete.
2
Click OK in the message box.
Stat moves the objects to the first reservation position in the selected environments.
* 
NOTE: Stat re-prioritizes the reservation for an object only in the environment in which you selected it. If you want to re-prioritize a reservation in multiple environments, make sure you select the objects in each of those environments.

Assigning Objects to a Different Developer

To assign an object to a different developer:
1
Select the object(s) in the object list.
2
In Assigned To field, select the developer you want to assign the object(s) to.
3
Click Reassign.
If you are reassigning a file object and the Copy to Working option is selected, Stat prompts you to specify if you want to copy the file object to the new developer’s working directory, and if so, whether to copy the file either from the original developer’s working directory or from the base environment’s source file location.
4
Select the options you want and click OK.
5
Save the CSR.

Stat updates the Assigned To field in the object list with the new developer's user ID. The new developer now has the lock on the object(s).

* 
IMPORTANT: You must save the CSR before the reassignment can take effect

Removing Objects from a CSR

To remove objects from a CSR, select them and click Remove.

* 
NOTE: You should remove an object only if it was added to the CSR in error. Modified objects should remain associated with a CSR for historical purposes.

Objects in the Base Environment

Objects in the Base Environment

There are several situations when an object may exist in other generic application environments or source file locations on the migration path but not in the Base environment. Since initial archive of objects comes from the Base environment, these objects are not included in the base archive set.

Possible reasons an object exists in one environment but not in others are:

•
You create a new object in the Development environment, which means it would not exist in any other environment
•
You work on an object that was previously created in the Development environment but not yet migrated to any other environment
•
You create a new file object in your working directory, which means it would not exist in any other environment

If you want to archive an object that does not exist in the Base environment, there are two different ways to do it for two different types of situations.

To add objects that do not reside in the Base environment:
1
On the Objects tab of the CSR window, select the environment in which the object exists.
2
In the Object field, select the object.
3
In the Lock in environment field, select Current environment.
To add objects that reside inside and outside the Base environment:
1
On the Objects tab of the CSR window, select the environment in which the object exists.
2
In Object field, select the object.
3
In the Lock in Environment field, select All on Migration Path.

By choosing the second method, the objects that exist in the Base environment are included in the base archive set. Those that do not exist are not added to the base archive set. You can include these latter objects in any interim or final archive sets taken from the environment where they reside.

Stat cannot create a base archive set if the objects in your CSR do not exist in your Base environment. While attempting to locate the objects, Stat permanently displays the value In Process in the Status field of the Archive Set window, and it will be unable to complete the archive set. If this happens, create an interim or final archive set from the environment that contains the objects and use this archive set to update the other environments with the new objects. For more information, see Creating Archive Sets (Generic Applications) .

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation