Stat 7.0 - System Administration Guide


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

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

To select a trigger event:

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.

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.

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.

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

Defining Rule Criteria

After selecting the trigger event, you can specify additional criteria that qualify the trigger event under your rule definition. Stat needs to know what values the CSR must display for the rule to take effect.

You specify the criteria by selecting criteria types (CSR fields) and the matching values. You may concatenate multiple CSR values.


	NOTE: Be sure to create a Stat Central Agent job for each type of “past due” event triggered by either a business or personal rule. Also, when scheduling the job, be aware of the timing of the rule. For example, if you want CSRs that are more than 1 hour past due to trigger an email, scheduling the job to run every 2 hours could result in an email being sent 3 hours after the trigger event.

Field

Fields correspond to certain types of information contained in a CSR. The Field list displays the following options:

•

Application Environment

•

•

•

•

•

•

•

•

•

•

•

•

•

NOTE: Depending on the trigger event, the Field list may include different options:

•

For business rules triggered by past due escalation events, the list above also includes options specific to that event. For example, for the event Past Due Task Escalation, the list includes the option Assigned User of Task.

•

For migration events, the list includes the Migration Status, Migrator, Module, and Target Environment.

•

For the Oracle Apps business rules, OraApps Patch Application Complete and OraApps Patch Rollback Complete, the list of fields includes the option Process Status, which corresponds to the field in the Oracle Applications Patch Management Console.

Operator

After you select a CSR field type, you need to establish its relationship to a value or set of values you specify. Options include:

•

Is – Select if the CSR field must equal the specified value, meaning a match must occur

•

Not – Select if the CSR field cannot equal the specified value. This tells Stat to initiate the rule whenever a trigger event occurs in a CSR with a value different than the one you specify.

•

Change From – Select if upon saving the CSR, the field has changed from one specified value to another

•

Not Change From – Select if upon saving the CSR, the field has not changed from one specified value to another. In this case, the rule takes effect when a trigger event occurs on a CSR with a field value that has not changed exactly as specified.

Value

The list of value options depends on the CSR field you select. If you select the Is operator, the corresponding value found in the CSR must match your selection for the business rule to take effect. Likewise, if you select Not, the corresponding value cannot equal your selection.

The table below shows some examples of rule criteria. You can define several criteria for one business rule.


Value	Operator	Value	Explanation
CSR Status	Not	Cancelled OR Denied	Rule takes effect when trigger events occur on CSRs with a status that is neither Cancelled nor Denied
Assigned Queue	Is	Dev	Rule takes effect when trigger events occurs on CSR assigned to the queue Development (Dev)
Application	Changed From	Self Service to HR, Benefits to Pay Roll, or HR to Benefits	Rule takes effect when trigger event occurs on CSRs where the Application has changed from Self Service to HR, or Benefits to Pay Role, or HR to Benefits


	NOTE: For the operators Change From and Not Change From, Any is a permitted value for the From field, and Any and Any except original value are permitted values for the To field. However, using the Any value in both the From and To fields will not trigger the rule. Instead, use the Any value in the From field and the Any except original value in the To field.

If you define more than one set of criteria for a business rule, each set must be met for the rule to take effect. The exception to this is when you define more than one value on a CSR field. In this case, the rule takes effect if the CSR field matches one of the possible values.

For example, let’s say you add a business rule based on an Open trigger event that uses each set of criteria shown in the preceding table. This means that everyone on the email distribution list will receive an automatic email notification whenever a Stat user or the Stat Central Agent opens a CSR with a status that is anything but Cancelled or Denied, is assigned to the Development queue, and an application value that has changed from one specified value to another.


	NOTE: For past due rules you may want to exclude closed CSRs from the rule. Otherwise closed CSRs will continue to be evaluated.

To add criteria to a rule:

In the Field field, select the CSR field you want.

In the Operator field, select an operator.

In the Value field, select a value for the field.

Click Add.

Your new criteria appear in the window with an indicator that it has been added to your rule.

Repeat for each additional criteria.

To remove criteria:

Select the row and click Remove.


	NOTE: To edit a rule, select the rule in the Business Maintenance table and then click Rule Details. Stat opens the Rule Editor window where you can edit the rule as needed.

Seleziona il prodotto:

Per una maggiore efficacia, compilare l'Obiettivo della chat:

Soluzioni consigliate per il problema

Stat 7.0 - System Administration Guide

Business Rule Maintenance

Defining Business Rules

Selecting a Trigger Event

Defining Rule Criteria