Chatta subito con l'assistenza
Chat con il supporto

Stat 7.0 - 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 Enabling Web Client to perform PeopleSoft migrations 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: Oracle Agent: Stat.conf and log4j2.xml configuration Appendix: Custom Report Files

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

PeopleSoft Object Security Setup Instructions

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. By default, the prefix for POL (Physical Object Locking) will be set to STAT. An alternative group name can be change in Maintenance | General | Peoplesoft Connect | Stat PSOPRID column.

To configure physical object locking
1
Create a unique PSOPRID if you have not already done so by navigating to PeopleTools | Security | User Profiles.
2
Create a unique Primary Permission List for each user. In the following example, the Primary Permission List (PPL) is called STAT_NANCIPPL.
3
Open the user profile. In the General tab, in the Primary field under Permissions Lists, specify the unique Primary Permission List for the user.
4
Go to Maintenance | General | PeopleSoft Connect and select the Physical Locking option.
5
(Optional) You can exclude certain object types from Physical Object Locking. This allows a user with a valid PSOPRID/password to open these objects in the Application Designer without locking the objects in Stat.
In the following example, PS/Query, Tree, Tree Structure, and Project will be excluded from Physical Object Locking.
6
Go to Maintenance | General | Service Domains and select PS Locking for the service domain.
7
Go to Maintenance | Stat Central Agent | Job Maintenance and create a new PS Object Lock Sync job. If you could not locate the environment from the drop-down list, verify that the environment is part of the PeopleSoft migration path.
What is PS Object Lock Sync job and why it is necessary to run it?
The PS Object Lock Sync job ensures that the PeopleSoft Object Security groups contain the correct objects. They might not contain the correct objects if, for example, someone has modified the group definitions in PeopleSoft. The job has two steps:
•
Sync objects locked in Stat by Stat developers with the Object Security Groups for the PeopleSoft developers in PeopleSoft.
•
Sync all objects in PeopleSoft with the Stat_Read and Stat_Exclud Groups in Object Security.
There are two key differences between the physical locking that occurs when users lock objects in a CSR and the PS Object Lock Sync job:
•
When a user saves a CSR after locking an object associated with it, Stat Central Agent automatically processes this object lock. It inserts a row in the Assigned Developer’s Object Security Group in PeopleSoft for the locked object. This is not done using the PS Object Lock Sync job. Stat Central Agent does it automatically in the background. Once Stat Central Agent finishes this process, the developer can open and modify this object in PeopleSoft.
•
You can schedule the PS Object Lock Sync job to run for the selected PeopleSoft environment any time you wish. It is recommended to run it once or twice a day during non-peak hours. However, you might need to run the job more frequently depending on the number of new objects created. If new objects are created often, run the job more frequently or on demand, as necessary.
The first time a PS Object Lock Sync job runs, it creates the STAT_READ, STAT_EXCLUD (if object types are selected for exclusion from Physical Object Locking), and STAT_PSOPRID (if at least one object was added via Stat).
8
Log in to the PeopleSoft portal. Select PeopleTools | Security | Permission List and Roles. Locate the user Primary Permission List.
9
Open the Primary Permission List. Select the Definition Security tab and add STAT_READ, STAT_EXCLUD (if object types are selected for exclusion from Physical Object Locking), and STAT_PSOPRID. Set STAT_READ to display only.
10
When the PS Object Lock Sync job runs, it will look at all the objects that were added in Stat. In our example, the job would look at the objects added by the user NANCI and put the objects in the STAT_NANCI group. In this way, only the user NANCI, or a user with the PeopleSoft Admin role, can open these objects.
11
To test if Physical Object Locking is working properly, do the following:
1
Add an object to a CSR. In the following example, an activity called Calculate Retro Pay was added. This object will automatically get added to the STAT_NANCI group.
2
Log in as the specified user (e.g., NANCI). If the user can open the objects, POL is working properly.
3
Attempt to open another object that hasn’t been locked via Stat. This action should initiate a read-only prompt.

Additional Information. In order to be able to open a Record PeopleCode, Component PeopleCode, or Application Engine PeopleCode object, the user must add the parent object along with it. For example, if you add a Record PeopleCode object named AA_COST_RT_JPN.EMPIL (RowInit) in a CSR, then you must add the record AA_COST_RT_JPN in order to open the Record PeopleCode object.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione