Chatta subito con l'assistenza
Chat con il supporto

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

Auto Task Maintenance

Auto Task Maintenance tables define tasks that Stat automatically creates based on certain application, type, and status values selected on a CSR. As soon as the user makes a selection in one of these fields, Stat determines if there are auto tasks defined for that particular code. If so, Stat adds them to the task list.

Stat features a separate maintenance table for each of the three values on which you can define auto tasks. All three tables are displayed in a standard maintenance window and include the same set of fields or columns.

Auto task security is controlled by the following user class rights:

•
Auto Tasks - Add
•
Auto Tasks - Edit

To open the Auto Tasks by Application table, select Maintenance | Domain-Specific | Auto Tasks | Application Tasks.

To open the Auto Tasks by CSR Type table, select Maintenance | Domain-Specific | Auto Tasks | CSR Type Tasks.

To open the Auto Tasks by CSR Status table, select Maintenance | Domain-Specific | Auto Tasks | CSR Status Tasks.

Value
Description

Active

Indicates if this task will be automatically generated or not

Source Application, Source CSR Type, Source CSR Status
(Key Value)

Depending upon the type of auto task you are maintaining, one of these fields will be displayed. Select a value from the drop down list that, when selected on a CSR, will generate the task

Activity Code
(Key Value)

Select an activity code from the list

Assignment
(Required Value)

Select one of the following:

•
A particular user who has access to this service domain
•
{Prompt for User} requires the user to select a name from the list prior to saving the CSR.
NOTE: In the Stat Web Console, the {Prompt for User} setting defaults to the user assigned to the CSR
•
{Assigned User} assigns the task to the person assigned to the CSR
•
{Current User} assigns the task to the person currently editing the CSR
•
{Open User} assigns the task to the person listed in the Open By field on the CSR

Due Date
(Required Value)

Select an option that defines how Stat calculates the due date for the task. Due dates are based upon either the CSR Open Date, Due Date or the Current Date. The '+' and '-' options calculate the date plus or minus the number of days specified.

Hrs Est
(Required Value)

Enter a default value for the estimated number of hours it will take to complete this task

Description
Override

Enter a description in this field to override the description associated with the task

Comment

If you want to have Stat automatically enter a comment with the task, enter it here

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

Business Rule Maintenance

The Business Rule Maintenance table defines sets of instructions which, based on a combination of trigger events and specified criteria, direct Stat to send out email notifications to a list of users and customers and/or execute user defined commands.

The Business Rule Maintenance table also displays personal rules defined by other users within the same service domain. Business rules are identical to personal rules with two exceptions:

•
You must define a distribution list to which the email is sent.
•
The owner of a business rule is always the special ‘SYSTEM’ account.

Business rule security is controlled by the following user class rights:

•
Business Rules - Add
•
Business Rules - Edit

With proper security, you can also edit personal rules from the Business Rule Maintenance table, including those belonging to other users. For more information on personal rules, see the Stat User Guide, Chapter 9, “Personal Rules.”

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

Value
Description

Enabled

If selected, activates the value in stat

Rule ID
(Key Value)

A 1-10 character code that uniquely identifies this business rule

Owner

By default, the owner of a business rule is “System.” For personal rules, this field displays the owner’s user ID.

Description
(Required Value)

A brief description of the rule

Event

The event that triggers the rule

Last Update
(Read Only)

The date and time that this rule was last updated

Update By
(Read Only)

The user who last updated this rule

In Stat, outbound email is processed by the Stat Central Agent. You configure the Stat Central Agent that you want to process email in the Electronic Mail Interface - Setup window. For more information, see Configuring the Stat Central Agent for Email . In addition, for the Stat Central Agent to process outbound email, you must assign to it the Send Queued Outbound Mail job. How this job is scheduled is up to you, but it is recommended you have it run frequently in order to promote real-time processing. For more information, see Defining Agent Jobs .

Defining Business Rules

To define a business rule, click New. Stat opens the Rule Editor window. In the Rule Definition tab, you select a trigger event and specify rule criteria the same way you do for personal rules.

The System ID is automatically displayed in the Owner ID field. The Rule ID field displays (New) until you save the rule. When you save, Stat assigns it a unique number.

Selecting a Trigger Event

Selecting a Trigger Event

Every business rule is triggered by a specific, predefined event.

To select a trigger event:
1
In the Description field, enter a brief description of your rule, such as “New PeopleSoft CSRs.” The Subject in an outgoing Business Rule email will include the Business Rule description.
2
In the Event field, select an event.
Available events include:
•
Any – When any of the events mentioned below occurs. This is the default event for business rules.
•
Command Error Notification – Sends an email when a triggered business rule has a defined command that completes with an error.
•
CSR Close – When a CSR changes from an open status to a closed status
•
CSR Open – When a new CSR is entered into the system by either a Stat user or the Stat Central Agent
•
CSR Open-Entry – When a new CSR is entered into the system by a Stat user
•
CSR Open-Mail – When a new CSR is created by the Stat Central Agent in response to an email from a customer or another application. Customers can email their requests to a predefined Stat Central Agent email address. Upon receiving the email, the Stat Central Agent automatically opens a new CSR for that request.
•
CSR Re-Open – When a CSR changes from a closed status to an open status
•
CSR Update – When a change is made to a CSR.
•
Migration Notification - When a migration occurs or is scheduled involving specific migration statuses, migrators, modules or target environments.
•
OraApps Patch Application Complete – When the Stat Central Agent for Oracle Apps is done processing the Patch Application request
•
OraApps Patch Application Scheduled – When a Patch Application is scheduled via a CSR or Patch Mgmt Console
•
OraApps Patch Rollback Complete – When the Stat Central Agent for Oracle Apps is done processing the Patch Rollback request
•
Past Due CSR Escalation – When a CSR is past due for a specified amount of time
•
Past Due Migration Approval Escalation – When a migration has not been approved or rejected after a specified amount of time
•
Past Due OraApps Patch Approval Escalation – When a patch application has not been approved or rejected after a specified amount of time
•
Past Due Post Migration Step – When a post migration step has not been completed after a specified amount of time
•
Past Due Project Escalation – When a project is past due for a specified amount of time
•
Past Due Status Approval Escalation – When a status transfer that has not been approved or rejected after a specified amount of time
•
Past Due Status Transfer Escalation – When a status transfer that has been marked as Ready has not been transferred after a specified amount of time
•
Past Due Task Escalation – When a task is past due for a specified amount of time
•
Unopen CSR Escalation – When a CSR has remained unread by the assigned user for a specified amount of time
* 
NOTE: The fields Type and Value appear whenever you select a past due escalation-type event. Here you specify the amount of time that the item must be past due to trigger the rule.
3
If you selected a past due escalation-type event, select the type of time interval you want to use in the Type field.
Options include Business Days, Days, and Hours. Then in the Value field, enter a numerical value for the time interval. For example, if you select Hour and enter a value of 6, the business rule is triggered when the item is six hours past due.
4
(Optional) Select Fire only once per CSR.
This configures the Stat Central Agent to fire the rule the first time the rule criteria are met for a CSR and no time thereafter. In the case of past due escalation events, this option applies to the specified approval, task, project, and so on. To illustrate, consider a business rule based on an Update trigger event and a CSR status of In Process. If you do not select Fire only once per CSR, everyone on the mail distribution list will receive an email each time a user saves a CSR with a status of In Process. By selecting Fire only once per CSR, users will receive an email only the first time a CSR is saved with an In Process status. The same is true when a Business Rule has a defined command. Later changes made to the CSR will not trigger the rule.
* 
NOTE: Selecting Fire only once per CSR adds the History tab to the Rule Editor window. This tab displays a list of CSRs that have triggered the business rule. Deselecting Fire only once per CSR removes the History tab from the window. For more information, see Viewing Rule History .
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione