Documentation
Dispatch Routes
Dispatch Routes maintains Edition-Center-specific delivery routes, optional Parent Route hierarchy and transport/contact details used by Circulation operations.
What Dispatch Routes is for
Dispatch Routes maintains Edition-Center-specific delivery/transport routes used by Circulation Agents and Dispatch Label operations.
A Route can optionally reference a Parent Dispatch Route and can contain one or more Transport Detail rows.
Find and open a Route
Open Circulation -> Dispatch Routes.
Search, sort and page by Edition Center, Route Name, Parent Route, Origin, Destination, RTC Permit No. and Status, then click a row.
Create a Route
Choose Create, select Edition Center, enter Route Name and optional Parent Route, Origin, Destination and RTC Permit No., then maintain Route Status.
Transport Details can be added before Save.
Edition Center
Every maintained Dispatch Route belongs to an Edition Center.
Changing Edition Center clears the Parent Route.
A Route already used by Agents, child Routes or Dispatch Label allocations is protected from being moved to another Edition Center.
Parent Dispatch Route
Parent Dispatch Route is optional and is useful when a local/child Route operates under another route.
The Parent must belong to the same Edition Center.
The system prevents self-parent and circular Route hierarchies.
Use the source Open control to inspect the selected Parent Route.
Origin, Destination and RTC Permit No
Origin and Destination describe the Route endpoints.
RTC Permit No records the optional transport/permit reference.
Dispatch Label output can use Route and Parent Route destination/permit information.
Save, Close and Actions
Save persists the Route and the active Transport Details together.
Close leaves Route Details without running Save.
The current Dispatch Route Details screen has no three-dot Actions menu; its operational controls are Save/Close and the Transport Details row controls.
Transport Details
Use the Transport Details tab for one or more transport/contact arrangements.
The fields are Mode of Transport, Contact Person, Mobile Number, Vehicle Number, Charges, Start Time, End Time and Additional Notes.
Mode of Transport, Contact Person, Mobile Number and Charges are required by the reviewed save. Charges must be zero or a positive number.
Add, edit and delete Transport Detail rows
Use the table Add control to stage a new row and edit values directly in the table.
Select a row and use the table Delete control to remove it from the active set.
Transport row changes are persisted by the main Route Save. After successful Save, a deleted persisted row should not return on reload.
Delete a Dispatch Route
From the list, select one or more Routes and choose Delete.
Cancel closes the Confirm Delete dialog without making a change.
Confirm checks each Route. A Route referenced by child Routes, Agents or Dispatch Label allocations is protected from Delete.
An otherwise-unused Route can be removed with its owned Transport Details.
Downstream operational effect
Agents can be assigned to Dispatch Routes.
Dispatch Label generation reads Route Name, Origin, Destination, RTC Permit No. and Parent Route information.
Changing a Route or its hierarchy can therefore affect future Dispatch Label presentation.
Related pages
Frequently asked questions
Why can’t I select this Route as its own Parent?
Self-parent and circular Route hierarchies are blocked.
Why can’t I move the Route to another Edition Center?
The Route is already used by Agents, child Routes or Dispatch Label allocations. Reassign those dependencies or create another Route.
Why must I Save after deleting a Transport Detail row?
Transport Detail row changes are staged inside Route Details and are committed by the main Route Save.
Why can’t I delete a Dispatch Route?
A child Route, Agent or Dispatch Label allocation still references it.
Where is the three-dot Actions menu?
The current Dispatch Route Details screen does not have one. Use Save/Close and the Transport Details row controls.