サポートと今すぐチャット
サポートとのチャット

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

Queue Assignment Tab

In the Queue Assignment tab, you can add and remove the selected user from work queues. Queues are specific groups of Stat users with similar skill sets or responsibilities and are defined by system administrators. For more information, see Queue Maintenance .

* 
NOTE: You can add and remove users to queues in the Queue Maintenance table as well as in the User Access Information window. For more information, see Editing Queue Membership .

Queues are service-domain specific. For this reason, the unassigned list of queues is organized by service domain. Only the service domains the user has access to are listed (for more information, see Service Domain Access Tab ). Double-click a service domain to open the list of associated queues the user is currently not assigned to.

To assign a user to a queue:
1
In the unassigned list, double-click each service domain that the queues you want to assign to the user are associated with.
* 
TIP: Use the Expand All and Collapse All buttons to open and close the unassigned tree list view.
2
Select each queue that you want to assign the user to or select the parent service domain to grant the user access to multiple queues at once.
3
Click the right-pointing arrow button.
4
To remove the user from a queue, select the queue you want to remove the user from in the list of currently assigned queues and click the left-pointing arrow button.
* 
NOTE: If the user is the owner of the queue, that user cannot be removed.
5
Save your changes by clicking either Apply or OK.

Application Access Tab

The Application Access tab is where you can restrict a user’s access to only specified applications while working within certain service domains. For example, if a user only has access to the Benefits application while in the HR service domain, then that user can only open CSRs that display the value Benefits in their Application field. In addition, when the user creates a new CSR, Benefits will be the only option in the Application field of the CSR window. Leaving this tab blank for a service domain gives the user access to every application in that service domain.

Application access also filters the list of users that belong to a queue. When a queue is added to or modified on a CSR, the list of developers is filtered based on the combined queue membership and application access settings. Only members of the queue who have access to the application are displayed. For more information, see Editing Queue Membership .

Applications are service-domain specific. For this reason, the unassigned access list is organized by service domain, with only the service domains the user has access to included (for more information, see Service Domain Access Tab ). Double-click a service domain to open the list of associated applications the user currently does not have access to.

To set up application access:
1
In the unassigned list, double-click each service domain to open the list of the associated applications the user currently does not have access to.
 
* 
TIP: Use the Expand All and Collapse All buttons to open and close the unassigned tree list view.
2
Select each application that you want the user to access or select the parent service domain to grant the user access to multiple applications at once.
3
Click the right-pointing arrow button.
4
To remove access to an application, select the application in the assigned list and click the left-pointing arrow button.
5
Save your changes by clicking either Apply or OK.

Object Type Access Tab

The Object Type Access tab is where you can restrict a user’s access to only specified object types while operating within a certain change management module and service domain.

The tree view of the unassigned list is organized by each service domain that the user has access to (for more information, see Service Domain Access Tab ), then by each change management module (PeopleSoft, Oracle Applications, and Generic Applications). Each module contains each associated class of objects, while each object class in turn includes each associated object type. This means you can grant users access to all the object types within a service domain at once, or you can restrict access to only individual object types.

To set up object type access:
1
In the unassigned list, double-click each service domain to open the list of change management modules.
Modules include PeopleSoft, Oracle Applications, and Generic Applications.
 
* 
TIP: Use the Expand All and Collapse All buttons to open and close the unassigned tree list view.
2
Double-click a module to open the list of associated object classes.
3
Double-click an object class to open the list of associated object types.
4
Select each object type you want to grant the user access to, or select the parent object class, module, or service domain to grant the user access to multiple object types at once.
5
Click the right-pointing arrow button.
6
To remove access to an object type, select the object type in the assigned list and click the left-pointing arrow button.
7
Save your changes by clicking either Apply or OK.

Environment Access Tab

The Environment Access tab is where you can restrict a user’s ability to migrate objects to only specified environments while operating within a certain change management module and service domain. This also restricts a user’s ability to approve migrations only to environments they have access to. For example, if a user only has access to the Development environment while in the HR service domain, then that user can migrate archive sets only to that environment and can only approve migrations to that environment.

Environment Access also restricts users from viewing and editing PeopleSoft Options.

The tree view of the unassigned list is organized by each service domain the user has access to and which is associated with active environments (for more information, see Service Domain Access Tab ). Each service domain opens a list of one or more change management modules (PeopleSoft, Oracle Applications, and Generic Applications), and each module it turn opens a list of associated active environments.

* 
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.
To set up environment access:
1
In the unassigned list, double-click each service domain to open the list of change management modules.
Modules include PeopleSoft, Oracle Applications, and Generic Applications. Environments are associated with modules through service-domain specific migration paths, which means certain service domains may be associated with one module but not another.
 
* 
TIP: Use the Expand All and Collapse All buttons to open and close the unassigned tree list view.
2
Double-click a module to open the list of associated environments.
3
Select each environment you want to grant the user access to, or select the parent module or service domain to grant the user access to multiple environments at once.
4
Click the right-pointing arrow button.
5
To remove access to an environment, select the object type in the assigned list and click the left-pointing arrow button.
 
* 
TIP: Remember that when you specify one environment, you are configuring Stat to deny the user access to all the other environments in the service domain, unless you explicitly grant the user access to them as well.
6
Save your changes by clicking either Apply or OK.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択