Documentation  >  Admin  > 

Reprocess Tickets

This screen is used to schedule tickets for reprocessing. Reprocessing includes: updating due dates based on current due rules and holidays, updating whether the ticket is after hours based on the lastest business hour configuration, and updating the legal due date parsed by a new parser format.

The Reprocess Tickets screen is shown below:

You can change the columns that are displayed on the Reprocess Tickets pane by configuring the grid.

Click the New button to open the new request dialog box, shown below. Use this box to create a new ticket reprocessing request. Next, specify the date range by entering the dates or selecting a time space from the drop-down box located to the right of the Date Range fields. To specify what feeds are reprocessed, highlight the desired feed(s) in the Available box, and click the right arrow located between the two boxes. To remove feeds from the Feeds to Reprocess box highlight the desired feed(s) and click the left arrow. Click the Schedule button to save the request.

New Request Dialog Box

Once a request is scheduled, it is divided into smaller requests. New requests are displayed with the "new" status.

After the request is scheduled it is tested the next time the reprocess tickets process runs. The status of the request is changed to "Tested(Pending Approval)" after it is tested.

Once the request has been tested, a notification is sent. More information about configuring the notification is located here. The notification includes the following info about the request:

  • feed name
  • date range
  • number of tickets
  • ticket number
  • after hours value before and after ticket is reprocessed
  • the old due date and new due date for the locates on each ticket

This same information is displayed on the Test Log tab, shown below.

After reviewing the test log or notification for the request and verifying that the changes are correct, click the Approve button. The request is processed the next time the reprocess tickets process runs. The status of the request is changed to "Success" once the request is processed.

After the request is processed, a notification is sent. This data is also displayed in the Commit Log tab, shown below

The status of the request is changed to "Test Failed" if the test fails. To reschedule a failed request, highlight the failed request, and click the Reschedule button. A new request that is duplicate of the failed request is added to the list.

Interpreting Log Files & Notifications

The first section contains the feed, date range, and the number of transmissions for the request.

First Section of Log File

Next, the changes that are made to each transmission after reprocessing is shown. The first line displays the ticket number. The second line displays whether the ticket was originally received after hours and if the ticket is considered as received after hours after being reprocessed. The next lines display the original due dates for each locate and the due dates after the ticket is reprocessed. The value before the arrow is the original due date and the value after the arrow is the due date after the ticket is reprocessed. There are two due dates shown for each locate:

  • "ourDueDate" - the due date calculated based on the implemented due rules for the feed
  • "legalDueDate" - the due date that is parsed from the ticket

Ticket Info Section Of Log File

The last section contains the number of errors that occurred during the ticket reprocessing request, and the number of tickets that were changed during the ticket reprocessing request. It also shows whether the changes were committed.

Last Section of Log File