Skip to main content

Error handling for routes

Suggest edit Updated on October 6, 2020

Analyze and resolve validation errors during route schedule validation and dispatch to ensure that the routes are scheduled correctly. Validation errors that might occur when you validate route schedules are of two types: route-level validation error and field worker-level validation error.

Types of validation errors

You can encounter two types of validation errors, depending on their origin:
Route-level validation error
An error that is caused by an incorrect route definition. When this error occurs, a warning symbol is displayed next to the route name, and the entire row is highlighted red.
Field worker-level validation error
An error that is caused by the availability issues of field worker. When this error occurs, a warning symbol appears in an individual cell, and the cell is highlighted red. If you do not want to resolve the error, you can override the issue if the following conditions are true:
  • If the assigned field worker is not available or is on leave.
  • If the field worker is assigned to a different route.

Work order processing

The work orders are created based on the PartialAllowExceptions configuration that is available at the implementation layer. You can use the following options:

True
The work orders that do not have any field worker-level error are dispatched. The work orders with field worker-level errors are created with the Exception Unassigned status.Note: The value of the PartialAllowExceptions configuration is set as True by default.
False
All the work orders in a route schedule are created with the Exception Unassigned status, even if only one work order has field worker-level errors.
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us