Stat 6.3 - System Administration Guide

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:

TIP: After defining the access settings of one user, you can use that user as the source for the synchronizing the access settings of multiple users. For more information, see Synchronizing User Access Information .

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.

TIP: Use the Expand All and Collapse All buttons to open and close the unassigned tree list view.

NOTE: If you select a service domain and click the right pointing arrow, the user is assigned to all the active user classes for that service domain.

CAUTION: When modifying a user’s service domain and environment access, be aware that this may affect migrations and patch applications to environments that require the user’s approval. If a user’s approval is required for a migration or patch application to an environment that they no longer have access to (which can be restricted either at the service domain or the environment level), the migration or patch application to that environment cannot be approved.

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

NOTE: If a PeopleSoft configuration file exists for a PeopleSoft environment, you can configure Stat to import it whenever it executes CLI functionality in that environment. This automatically updates the user’s %PS_HOME% variable used during CLI functions. For more information, see PeopleSoft Environment Connection Maintenance .

NOTE: Users can specify the PS Tools directories themselves in the PeopleSoft Options window. For more information, see the Stat User Guide, Chapter 11, “Change Management for PeopleSoft.”

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.

NOTE: For Oracle Applications proprietary file object types, you must define working file directories in the File Type User Directories tab of the File Locations window. After they have been defined there, you can modify their assigned user directories in the Other User Information window. For more information, see File Type User Directories on page 97.

NOTE: Users can define their own working directories in the Stat User Options window. For more information, see the “Object Management” sections in the change management chapters of the Stat User Guide.

NOTE: You can also define a user’s default working directory in the User Default Directories Maintenance table. For more information, see Object Type Maintenance .

NOTE: Make sure you use the proper syntax when specifying working directories. For more information, see File Path Syntax .