Below is a Problem Report Form from a project that has the Exception Collector configuration.
The user defined fields for the project, and how they are used to manage exceptions, are listed below.
Signature Code -- uniquely identifies the exception. It is calculated from the data in the stack trace. This field is configured as a read only field because you shouldn't modify it.
Occurrence Count -- counts the number of times this exception is reported by customers. The Occurrence Count helps you determine which exceptions should have the highest priority to fix. The Occurrence Count is computed by PR-Tracker and is configured as read-only. You should not modify it.
First Version Reported -- specifies the version of software in which the exception was first reported. The field value is supplied by PR-Tracker and is configured as read-only. You should not modify it. If you begin tracking exceptions during software development, this field can help you determine when an error may have been introduced.
Last Version Reported -- specifies the version of software in the exception was last reported.
Version Resolved -- specifies the version of software in which the error was fixed. This version should remain greater than the Last Version Reported. If not, it means that the error probably didn't get fixed. You may want to create a query that lists all problems where Last Version Reported >= Version Resolved.
Stack Trace -- helps one determine what routine the error occurred in. The stack trace also includes information from all inner exceptions.
Error Data -- is data such as user actions (also called events), trace data and configuration data. The data that is collected in this field is determined by how the application source code is annotated with ExManager class methods. See Adding Exception Handling Code To Applications. The amount of data collected in the field could be considerable. You may want to edit this field manually to delete irrelevant data.
Collect More Data -- tells PR-Tracker to keep collecting Error Data for the exception. If this box is not checked, PR-Tracker will stop collecting error data after 20 exception occurrences. Check this box only if you haven't collected enough data to solve the exception. Make sure to uncheck the box when you have collected all the Error Data you need, otherwise the database will become bloated.
Response -- use this field to send a message back to the user reporting the exception. This message may specify a version of software in which the exception was fixed, or it may specify actions that the user needs to take to prevent the exception from happening.
Publish Response -- you must check this box for the response to be sent back to the user. This field is needed because the version of software in which the fix was implemented may not yet be available to the public. When releasing a service pack or an upgrade, use a query to find responses that haven't been published yet.
Note: DO NOT delete any of the above fields from an exception collector project. This will result in error. You may add fields or move fields around on the form.