立即与支持人员聊天
与支持团队交流

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 .

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.

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.

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.

Modules include PeopleSoft, Oracle Applications, and Generic Applications.

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.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级