Chatta subito con l'assistenza
Chat con il supporto

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

Locking Facts

Additional information about locking objects in Stat that you should know:

•
While not all objects can be physically locked in PeopleSoft, all objects can be logically locked in the Stat Repository
•
If an object is locked on a CSR, you cannot lock it on another CSR for the same PeopleSoft environment
•
In order to lock objects physically in PeopleSoft, you must have your PeopleSoft operator ID defined in Stat. This is controlled by your security settings.
•
Stat supports physical locking of file objects, such as SQRs, COBOLs, and Crystal Reports
•
You can logically lock schema objects, data objects, and PeopleSoft proprietary objects that are not governed by PeopleSoft’s Object Security, but you cannot physically lock them

Physical PeopleSoft Locking Option

Physical PeopleSoft locking works in conjunction with Stat logical locking. When your system administrator activates the Physical PeopleSoft Locking option in Stat, any object you lock in Stat is also locked in PeopleSoft. Stat utilizes PeopleSoft Object Security to secure the locked objects in each PeopleSoft environment.

Your system administrator defines the scope of PeopleSoft physical locking at the service domain level. Depending on the service domain, object types as well as PeopleSoft environments may be excluded from the physical locking option. Even specific PeopleSoft users can be excluded from this functionality.

The developer assigned to the physically locked object is the only user that has Write access to the object in PeopleSoft. Other users are restricted to Read Only access. If the object is reassigned to a different user and the CSR is saved, the new user has Write access and the previous user has Read Only access to the object.

An object that is not physically locked on any CSR can only be opened in Read Only mode in PeopleSoft. In order to make any changes to PeopleSoft proprietary objects, you must first open a CSR and physically lock the objects in that CSR. This ensures that all object modifications are documented.

* 
NOTE: For detailed instructions on setting up physical locking between Stat and PeopleSoft, see the Stat System Administration Guide, Chapter 8, “Object Security.”

Physical File Locking Option

Like physical PeopleSoft locking, physical file locking works in conjunction with Stat logical locking. When set up appropriately, physical file locking prevents developers from modifying file objects that have not been locked in a CSR and assigned to them. Stat does this by allowing developers to modify only file objects that are in their working directory. Once a file is locked and assigned to a developer, the developer can only use Stat to migrate the file to their working directory as well as all source directories. This enforces that all changes to the file objects are documented and orchestrated through Stat.

System administrators define the scope of the physical file locking. Source file locations, specific users, and environments can be excluded from physical locking.

Associating Objects with CSRs (PeopleSoft)

If a change request requires modifications to objects, you access and work with these objects in a CSR. The CSR becomes the logical grouping of all the affected objects.

Remember that objects are associated with CSRs as opposed to users. In order to lock, archive, or migrate an object, you must first associate it with a CSR. The modifications that you make to objects are still made in PeopleSoft — Stat simply provides tools that manage and track those changes.

You can manually associate objects with a CSR, or you can use one of three wizards to associate objects en masse. These include:

•
The PeopleSoft Project Read Wizard, which associates the PeopleSoft proprietary objects in a project
•
The Read File Wizard, which associates the file objects in a folder
•
The CSR Read Wizard, which associates the objects associated with another CSR

Objects can also be associated with a CSR using the Impact Analysis Wizard and the Undocumented Object Wizard. For more information, see Object Tools and Wizards .

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione