Chatta subito con l'assistenza
Chat con il supporto

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

Working With Service Domains

Service domain-specific maintenance tables are displayed in standard maintenance windows, which by default display information regarding your default service domain. You can switch to a different service domain by selecting it in the Domain field located at the top of each window.

Any value you specify in a service domain maintenance table pertains only to the service domain displayed in the Domain field. For example, users working in the Human Resources service domain are not affected by any changes you make to a table pertaining to the Change Control service domain. You can, however, specify the same value for two or more service domains. This is because Stat invisibly prefixes service domain codes to each value, thereby uniquely identifying them in the system. For example, let’s say you define a CSR status named “URG” (for urgent) in both the Change Control and the Human Resources service domains; even though they appear the same to users working in both service domains, internally Stat distinguishes them by the code prefixes of their respective service domains, “CHG-URG” and “HR-URG.”

User class rights control access to each service domain-specific maintenance table. Since you can have a different user class for each service domain, you may have access to a table for one service domain but not for another. It is recommended that system administrators have user class rights to all tables.

Activity Code Maintenance

The Activity Code Maintenance table defines categories of tasks and auto tasks. Each task must be associated with an activity code.

The use of tasks and activity codes is optional in a Stat implementation.

If you choose not to define activity codes for a service domain, you should not display the Tasks tab on CSRs created within that service domain.

Activity code security is controlled by the following user class rights:

The Activity Code Maintenance table is displayed in a standard maintenance window. To open this window, select Maintenance | Domain-Specific | Activity Codes.

Active

Indicates whether the record is activated in Stat

Activity Cd
(Key Value)

A 1-10 character code which uniquely identifies the activity

Description
(Required Value)

A 1-35 character description of the activity

Comment Req’d

If selected, the user will be required to enter a free text comment at the time the task is marked as completed

Allow Descr Edit

If selected, the user is allowed to change the task description. This is commonly used for a miscellaneous task which allows the user to enter a more appropriate description for the task.

Last Update
(Read Only)

The date and time that this record was last updated

Update By
(Read Only)

The user that last updated this record

Application Maintenance

The Application Maintenance table defines the products or facets of your enterprise that can be represented in CSRs. Application codes define available items on the CSR Application drop down list.

Application security is controlled by the following user class rights:

The Application Maintenance table is displayed in a standard maintenance window. To open this window, select Maintenance | Domain-Specific | Applications.

Active

If selected, activates the value in stat

Applic Cd
(Key Value)

A 5-character code which uniquely identifies the application

Description
(Required Value)

A 1-35 character description of the application

Application Tab
(Required Value)

The change management tab displayed on the CSR when the application is selected. Options include PeopleSoft, Oracle Applications, Generic Applications, and None.

Last Update
(Read Only)

The date and time that this record was last updated

Update By
(Read Only)

The user that last updated this record

Application Environment Maintenance

The Application Environment Maintenance table defines subsystems of an application. Application environment codes are used to further define or describe applications.

Not all applications have environments. Defining application environments is optional; you can define environments for all, some, or none of the applications in a service domain.

Application environment security is controlled by the following user class rights:

The Application Environment Maintenance table is displayed in a standard maintenance window. To open this window, select Maintenance | Domain-Specific | Application Environments.

NOTE: For any service domain in which you want to use application environments, be sure to select Use Appl Env in the Service Domain maintenance table. Otherwise, the Application Environment field will be grayed out on CSRs opened in that service domain. For more information, see Service Domain Maintenance .

Active

If selected, activates the value in stat

Application
(Key Value)

Select an application from the list

Env Cd
(Key Value)

A 1 to 5-character code that uniquely identifies the environment for this application. For example, you may have a TEST environment code for several different applications but you can only have one TEST environment code for a single application.

Description
(Required Value)

A 1-35 character description of the application environment

Last Update
(Read Only)

The date and time this record was last updated

Update By
(Read Only)

The user who last updated this record

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione