System Analyzer Message Categories
The System Analyzer uses categories to classify the messages listed in the main pane, which makes it easy for you to filter the information.
Good to Know:
- Before you run the System Analyzer, define the message categories that you want to track.
- The following message categories are selected by default: Business Object, BusOb Load Timing, Error, One-Step™ Action, Table Validation Timing, Token Expression Error, and Web Service Call. Messages are not selected by default if they generate a large number of messages or are only applicable for 2-tier or 3-tier systems.
The System Analyzer uses the following categories:
|Action Block||Logs Execution Begin, Execution End, Value Input (parameters), and Value Output (parameters).|
|Adaptive Layout||Logs when Business Object forms are resized.|
|App Service call||
Tracks calls that have been made from the CSM Desktop Client to the Application Server.
This type of message is only applicable if you are running a 3-tier system. Logging this type of message might cause unexpected results (example: Pausing on a remote call might cause timeout errors).
|Business Object||Tracks Business Objects, including fields and relationships. Use these messages to find issues related to field changes.||(Incident.Location) value set to "Colorado Springs."|
|BusOb Load Timing||Tracks the amount of time that Business Object operations require to load. Use these messages to track messages related to loading Business Objects and their relationships. It can also be used to improve efficiency by eliminating or grouping operations.||(Customer - Internal) Retrieved Business Object: Tracy E. Aubin, Time: 0.0320019.|
|Error||Tracks various system exceptions and errors.|
|Foreign Key||Logs values set for foreign key fields.|
|Foreign Key Potential Issue||Logs when an expected foreign key does not display.|
|Modify Value||Tracks changes to modifier values.|
|One-Step||Tracks the execution of One-Step Actions.||(Select User) About to execute step Select User.|
Tracks all other miscellaneous messages. These messages are often dependent on the type of system (2-tier or 3-tier) you are running.
|Query (2-tier only)||
Tracks the execution of queries.
This type of message is only applicable if you are running a 2-tier system.
|Session||Tracks session information.|
|Table Validation||Tracks field validation values, which might read from the local cache or cause queries to the database.||Querying for a Lookup value in data cache for Incident Type.Incident Type: Valid value found.|
|Table Validation Timing||Tracks the amount of time that table validation operations require. Use these messages to improve performance by either changing the behavior or marking tables as cacheable.||Retrieved single row for Service.Service Name table validation request: 0.052003.|
|Token Expression Error||
Tracks token expressions.
Token expressions are used for building text and number expressions, which replace tokens and evaluate the results. These expressions are also used to build text (example: Incident.Category). While this is allowed, it can cause performance issues (particularly on forms with multiple token expressions). A check box in the Expression Editor indicates whether or not the expression is calculated. If the token expression error message opens in the System Analyzer, it might indicate that this check box should be cleared.
|Non-valid token Expression evaluation for Field Incident.Matching Text. Value: Printing.|
|Web Service Call||Tracks details related to calls made by the web service One-Step Action.|