Diagnostic Messages
The Diagnostic Messages screen displays error messages generated as a result of processing.
Filters can be used to limit the number of records that are displayed.
If an employee is calculated from the employee record and an error occurs, the user is given a message and has the option to view the details and reset the employee through the system health monitor.
Note:
Employees can be reset by selecting the check box to the left of each run-time error record and then clicking the Reset Selected button in the left pane.
Depending on the page displayed, the following fields may be available. Click on the link to navigate to the description. |
The following related topics are available: |
Category
Filters the list by the type of transaction being processed that generated the message. The options available depend on whether the filter is set to Diagnostic Messages or Invalid Transaction Posts.
-
When the filter loaded is for Diagnostic Messages, the processing options here are: current calculation, future calculation, deduction calculation, productive posting, non-productive posting, education posting, deduction posting, call entry posting, or LaborView finalization.
-
When the filter loaded is for Invalid Transaction Posts, the transaction options here are: clocking, calendar, adjustment, projection, deduction, custom, request, or education.
-
When the filter loaded is for Pending Calculation, the processing options here are: current calculation, future calculation, and deduction calculation.
Created Date Range Begin
The first date of the range to be included in the filter when searching for transaction errors.
Created Date Range End
The last date of the range to be included in the filter when searching for transaction errors.
Has Been Resubmitted
Filters the list by whether or not the record has been resubmitted for processing (Yes/No).
Host Name
The name of the workstation or server where the process was run, that created this error.
What Happened
The description of the error.
When Created
The date and time when the process was run, which created this error.