Chat now with support
Chat with Support

Quest has tools and processes in place to identify, protect, detect, and remediate vulnerabilities and incidents when they occur, including external security partners. As part of our standard security operations, Quest does not use CrowdStrike in any of our operations. We are reviewing our third parties, and so far, there is minimal affect. It is Quest's policy not to provide further technical details unless they directly impact customer data.

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

Info Request Processing

As discussed in the preceding chapter, you can configure the Agent to send an email message to customers notifying them that a new CSR has been opened. Customers can then send a reply message via email requesting more information about the CSR.

Included at the bottom of the original message is an encrypted special identifier line. This line is specially formatted and contains information on the service domain, CSR number, and sender, as shown below:


For the Agent to recognize the inbound email as an information request, you must specify a match string in the Special Processing tab that includes part of this special identifier line. The match string should not match the special identifier line completely (which is CSR number and sender specific), but should at least include “<<Stat”, and possibly the service domain as well, for example, “<<Stat|CHG”, where “CHG” is the service domain code.

If the special identifier line is not present in the inbound email or has been modified improperly, the request is ignored and the Agent continues processing the email. If it is not picked up by any other filters it is treated as a new CSR request.

If the Agent recognizes a message as an information request, it retrieves the most recent CSR information and sends an email back to the originating mailbox with that information.

Adding a Parameter

In the Match String field enter the keyword variables you want the Agent to search for.
In the Special field, select the processing parameter you want.
Click Add>>.

Order of Processing

The Agent processes the values in the order they are displayed. If a match is found, it processes the email appropriately, ignoring any subsequent items.

You can change the processing order by selecting the item you want to move and clicking Move Up or Move Down.

Removing or Editing a Parameter

To remove or edit a parameter, select the row and click << Remove. The Agent moves the match string and processing parameter from the list back to their respective fields.

If you want, you can then edit the match string and add it back to the list.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating