Chat now with support
Chat with Support

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

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.

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

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.

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.

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.



Cancelled OR Denied

Rule takes effect when trigger events occur on CSRs with a status that is neither Cancelled nor Denied




Rule takes effect when trigger events occurs on CSR assigned to the queue Development (Dev)


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.

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.

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.

Defining Message Content

After selecting the trigger event and optionally specifying rule criteria, the next step is to open the email Message tab and define the content of the email message that is to be sent out when the rule is triggered.

NOTE: If you select the Most Recent Log option and the most recent log entered on the CSR is flagged as confidential, the log is not included in the email message. Also, if you select the Attachments option, any attachments on the original CSR will be forwarded with the email message.

Defining a Distribution List

After specifying the content of the email message, the next step is to specify a distribution list of mail recipients.

In the Send To field, select a value. Send to options are based on a selected rule event and could be different for each rule.
In the Field field, select how you want the message addressed to the recipient.
Options include To, CC, and Blind CC.
If you selected User, Specified in the Send To field, select the Stat user you want in the Other Address field.
If you selected Other Address in the Send To field, enter the email address in the Other Address field.
Click Add.
Click Remove.

Defining a Command to Run

When a Business Rule is triggered, Stat can execute a user-defined command. The command is executed by Stat Central Agent. The command can be used for any purpose, for example, to notify a third party system about a Stat event. To define a custom command, navigate to the Define Command tab.

Stat offers many predefined and custom parameters that can be used to build a command. Predefined parameters can be used when a Business Rule triggers CSR-specific events, for example, a CSR Update. A drop-down list displays the CSR fields available in the Stat Database view CSR_BUS_RULE_PARAMS_VW1. The parameters drop-down list displays the User Parameters defined for the Pre/Post Migration steps.

To add a parameter to a command, select the desired parameter from the drop-down list of predefined parameters and click the Add button. The selected parameter is inserted at the cursor position in the command field and uses the following format: %%PARAMETER%%.

The following is an example of a command:

\"body\": \"CSR: %%SD_CD%%-%%CSR_ID%%:%%TITLE%% - has been updated by %%UPDATED_USER_ID%% on %%UPDATE_DATE%% :)

This command will add a comment to Jira for a case defined in the CSR Tracking number. Notice that JIRA_USERID and JIRA_PWD are defined in the User predefined parameters.

You can also specify a command time-out and specify conditions for the executed command to trigger a “Command Error Notification” business rule.

Trigger “Command Error Notification” when return code... – Select this option to trigger the Command Error Notification business rule if the command errors. Then refine the trigger by selecting specific trigger conditions applicable to your custom command.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating