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

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

Removing or Editing a Parameter

To remove or edit a parameter, select the row and click << Remove. The Agent moves the match string from the list back to the Match String field. You can then edit the match string and add it back to the list.

Reply Tabs

After the Agent creates a new CSR, it can create and send a reply message to the originator. There are two types of reply messages: identifiable customer and unknown customer. When the Agent cannot locate a customer in the Customer Maintenance table, the reply is sent to the originating mailbox. If the Agent can locate a customer, the reply is sent to the customer’s email address. If the customer has two email addresses, the reply is sent to the primary address.

The Reply Message and Reply-Unknown Customer tabs display the same information as the event-specific tabs in the Electronic Mail Interface - Setup window. For more information, see Outbound Mail Configuration .

To define reply messages:
1
Click the Reply Messages tab.
2
In the Fields to Include in Message section, select the check boxes next to the CSR fields you want to include in the message.
3
(Optional) In the Message Header and Message Footer tabs, enter the header and footer you want included at the top and bottom of the reply message, respectively.
4
In the Send To tab, add any additional recipients you want. By default, the reply message is sent to the customer and a carbon copy is sent to the assigned user.
5
(Optional) Click the Reply-Unknown Customer tab and repeat steps 2 through 4 to define the message that Stat sends to the originating mailbox.
6
Click OK to save your work.

Object Security

•
PeopleSoft Proprietary Object Security
•
PeopleSoft Object Security Setup Instructions
•
Frequently Asked Questions
•
File Object Security

PeopleSoft Proprietary Object Security

You can configure Stat to physically secure PeopleSoft proprietary objects in their native environment the moment they are locked in a CSR. This ensures that the developer assigned to the object is the only one working on it. In addition, you can set up the Stat Central Agent to run synchronization jobs at specified time intervals to ensure that the Stat Repository and your PeopleSoft environments remain synchronized.

A PeopleSoft proprietary object can be assigned to one developer for each environment in which it is locked. If an object is locked in two or more environments, this means that multiple developers may be associated with the object.

Object Security (also known as Definition Security) is assigned to the developer of the object. A different developer may be assigned the object at anytime if necessary, and Stat reassigns the object lock to the new developer when the CSR is saved. Any notifications regarding locking/reservations are sent to the assigned object developer, not the user assigned to the CSR.

PeopleSoft Proprietary Object Security takes effect when the Stat Central Agent processes CSR activity after the CSR is saved. The PeopleSoft proprietary object locks are in place virtually at the same time the lock occurs in Stat, even before the Stat Central Agent starts processing the base archive set. The Stat Central Agent also processes synchronization jobs that can be scheduled to fit the needs of each client. These jobs ensure that Stat recognizes when new objects are added to any environment, as well as ensuring that the security information on Stat remains in sync with PeopleSoft and vice versa.

For special PeopleSoft proprietary object security considerations, see the Stat User Guide, Chapter 11, “Change Management for PeopleSoft.”

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択