Chat now with support
Chat with Support

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

Associating Objects with CSRs (Generic Applications)

You access and work with 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 the application environment— Stat simply provides tools that manage and track those changes.­­­

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

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

Generic Application Change Management Tab

To begin associating objects with a CSR, select the generic application change management tab. This tab, which can be labeled in any way specified by your system administrator, features tools that connect directly to your generic application environments. It is also service domain-specific. When defining a service domain, your system administrator determines which service domains display the generic application change management tab on its CSRs. Access to this tab is normally restricted to developers and migrators. For more information on security settings, see the book, Stat System Administration, Chapter 3, “Stat Security.”

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 first by selecting a migration path. 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:
1
On the generic application change management tab, click Advanced....
This opens the Change Management/Version Control window.
The first tab of the Change Management/Version Control window, CSR Info, displays in a read-only format the general information fields of the CSR as well as its long description.
* 
NOTE: If the Patch tab is activated on the CSR window, the Change Management/Version Control window displays it as well. Both tabs display the same information and function the same way. For more information on patches and the Patch tab, see Change/Service Requests .
If you want to edit any of the information displayed on the CSR Info tab, click Edit. This opens the CSR window for that CSR.
2
Click the Migration Path tab.
3
In the Select Migration Path field, select the appropriate migration path.
The displayed paths vary, depending on the service domain. You should select the path most suited to your current needs.
* 
NOTE: If a workflow that specifies a migration path is assigned to the CSR, that path is the default path displayed in the Change Management/Version Control window and cannot be changed. For more information on workflows, see Change/Service Requests . For more information on migration paths, see Running a Migration (Generic Applications) .
4
In the Select Default Developer field, select a developer.
You can assign different developers to different objects, but this is the person that most of the objects will be assigned to.
5
(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.
6
Click Generate Path.
Stat displays a graphical representation of the migration path. Also, the Objects and Object Management tabs appear.
Each drum represents a generic application environment. Your system administrator determines which environments are designated as Base (Production) 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.
7
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 Selecting Lock Options for more information.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating