Chat now with support
Chat with Support

Stat 6.3 - System Administration Guide

Overview of Stat Administration Administrative Utilities Stat Security General Maintenance Tables
System Maintenance Service Domain Maintenance Department Maintenance Issue Tracking Maintenance Country Maintenance Customer Maintenance Object Type Maintenance PeopleSoft Environment Connection Maintenance Pre/Post Migration Steps Parameters Oracle Applications Configuration Oracle Applications Connection Maintenance Generic Application Connection Maintenance Schema Object Parameters Maintenance Data Object Maintenance PeopleSoft Search Configurations Stat Report Definition Maintenance Version Control Management Connection Maintenance
Service Domain-Specific Maintenance Configuring the Stat Central Agent Email Configuration Object Security Appendix: Sample Service Domain Configuration Appendix: User Class Rights Appendix: Creating a Staging Database Appendix: Database Tuning Appendix: Oracle Applications File Type Directory Appendix: Ports and Firewalls Appendix: REST Web Services API Appendix: SOAP-Based Web Services API Appendix: Troubleshooting Chart Appendix: stat.conf Configuration Appendix: Custom Report Files

The User Access Information Window

The Access Information... button opens the User Access Information window. The window features tabs in which you can do the following:

Service Domain Access Tab

Grant users access to a service domain by assigning them to user classes for that particular service domain.

PS Options Tab (PeopleSoft only)

Define the PeopleSoft Operator IDs and passwords that the selected user will need to physically lock PeopleSoft proprietary objects.

User File Directories Tab

Define the selected user’s working file directory for each file type as well as the user’s default working directory.

Queue Assignment Tab

Add and remove the selected user from work queues.

Application Access Tab

Restrict a user’s access to only specified applications while working within certain service domains.

Object Type Access Tab

Restrict a user’s access to only specified object types while operating within a certain change management module and service domain.

Environment Access Tab

Restrict a user’s ability to migrate objects to only specified environments while operating within a certain change management module and service domain.

Pre/Post Migration User Parameters Tab

Define public user-based parameters that can be included in the definition of post migration command steps.

Except for the PS Options and User File Directories tabs, each tab in the User Access Information window displays two lists of access rights. The right side shows all the access rights currently assigned to the user, while the left side shows a tree view of all the unassigned rights organized by service domain (except in the case of the File Server tab). Each group of unassigned rights displays the number of rights it contains. A bold number indicates that all the rights in the group are currently unassigned to the user, while no number indicates that all the rights are currently assigned to the user. The total number of access rights assigned and unassigned to a user is shown above each respective list. Double-click a group of unassigned rights to expand it, or use the Expand All button.

Service Domain Access Tab

You grant users access to a service domain by assigning them to user classes for that particular service domain. New users start out with no access rights to any service domain. In this case, the first step is to assign them a default service domain, which is the service domain that the user will work with most often and will be the default choice whenever the user is prompted to select a service domain, such as when creating a new CSR.

a
In the Default Service Domain field, select the user’s default service domain.

PS Options Tab (PeopleSoft only)

The PS Options tab displays a list of all the PeopleSoft environments defined in Stat. From here you can define the PeopleSoft Operator IDs and passwords that the selected user will need to physically lock PeopleSoft proprietary objects. You do not have to define a password the same time you define a PS Operator ID.

In this tab, you can also configure Stat to do the following:

If you want to configure Stat to perform any of above mentioned tasks, you must specify both the user’s PS Operator ID and password for the selected environment. For auto-migration, you must also define the staging database in a migration path as well as the distribution environment, if any.

In addition to the CLI functionality described above, defining a user’s operator ID and password allows that user to physically lock PeopleSoft proprietary objects in the selected environment:

Staging databases are defined in the PeopleSoft Environment Connection Maintenance table, as explained in the section, PeopleSoft Environment Connection Maintenance . Distribution environments are defined in the PeopleSoft Migration Path Maintenance table, as described in the section, PeopleSoft Migration Path Maintenance .

NOTE: Users can define their own IDs and passwords in the PeopleSoft Options window, which they open by selecting User Options | PeopleSoft Options. In addition, users can share the same PS Operator ID and password for staging purposes if that is how your PeopleSoft environment is configured. For example, you can assign users the ID “PS” or “VP1.”
3
Click the corresponding Enter Password button in the PS Password column.
4
5
(Optional) Select CLI Open for any designated staging database.
6
(Optional) Select CLI Auto-Migration for any environment designated in a migration path as the target environment for a migration.
7
If you selected either CLI Open or CLI Auto-Migration, specify the directory location of the user’s PS Tools executable in the PS Tools Directory field.

User File Directories Tab

The User File Directories tab displays a list of the active file types defined in Stat for PeopleSoft, Oracle Applications, and generic application environments. From here you can define the selected user’s working file directory for each file type as well as the user’s default working directory. Defining a working directory for a file type is optional. If a file type working directory is not defined, Stat places copies of the migrated file objects in the user’s default working directory.

1
In the Module field, select the change management module you are using.
2
In the Default Working File Server field, select the server for the default working directory.
3
In the Default Working File Path field, enter the path of the default working file location starting after the file server’s root or home path.
4
Click Apply or OK.
4
Click either Apply or OK.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating