Route Instances
Access a Route Instance
Procedure
Results
Access a Route Instance History
Procedure
Results
Note: When a route is in progress, the instance will not be moved to Instance History. However, if the route is marked as finished, then the route will be removed from Open Instances and added to Instance History.
Access Route Instance Details
Procedure
Results
Create a Route Instance
Procedure
Results
Delete a Route Instance on Rounds Pro Manager
Procedure
Results
Print a Route Instance on Rounds Pro Manager
Procedure
Results
Filter a Route Instance List
Procedure
Results
Sort Data in a Column in Route Instances
Procedure
Results
Note: Sort criteria is not affected by filtering. For example, if you sort the routes by the LOCATION column and then filter by STEP COUNT, the sort order remains unchanged.
Show Routes Columns in Route Instances
Procedure
Hide Routes Columns in Route Instances
Procedure
Create Ad-hoc Route Instance
Procedure
About Expired Instances
The Expired Route Instances functionality helps manage route instances efficiently by automatically closing older instances where readings haven’t been taken, even after the scheduled time defined at the Route Master level has passed.
This process uses the value specified in the Maximum Open Instances field during Route Master creation.
When a Route Master is due, the Rounds Pro service checks the value in the Maximum Open Instances field. If the number of open instances (excluding ad-hoc and checked-out instances) meets or exceeds this value, the oldest instance is marked as Expired and closed. A new instance is then created.
The following actions are performed:
- A route instance execution history is created with:
- Checked Out By: blank
- Checked Out On: blank
- Checked In On: current date and time
- Checked In Status: Expired
- Checked In By: System User
- The route instance is marked as Completed and is available in the Instance History tab.
- Expired instances cannot be checked out, as they are considered completed.
- Compliance Track data is not updated for expired instances.
Important: Periodically review expired instances and consider adjusting the schedule to a lower frequency to avoid unnecessary expirations.