Forward a job to iDrv4

iDrv4 (Ceres TMS) is the transport-management system that handles dispatch and proof-of-delivery. Forwarding a job from JATT Portals into iDrv4 hands the booking to ops for execution.

When to forward

Forward a job to iDrv4 once:

• The customer and addresses are confirmed.
• The pickup date and cargo are accurate.
• The pricing is locked in.

After it’s forwarded, the iDrv4 booking is owned by Ceres. Edits to the JATT-side connote no longer flow downstream.

How to forward

1. Open /operations/jobs.
2. Click the row of the job you want to forward.
3. In the drawer header, click Send to iDrv4 (paper-plane icon).
4. Confirm the prompt.

The button shows a spinner while the request is in flight (typically 1-3 seconds). On success:

• A Forwarded to iDrv4 (CN…) toast shows the iDrv4 control number.
• The drawer reloads. The Send to iDrv4 button is replaced by a green Forwarded to iDrv4 (CN…) badge.
• The Jobs list refreshes.

Idempotency

Once a job is tagged with an iDrv4 control number, the Send to iDrv4 button disappears and the green badge stays in its place. Clicking the badge does nothing — it’s purely informational. This prevents accidental double-forwards.

If iDrv4 ever needs a re-send (their record was purged, the consignment ref needs to change, etc.), contact your administrator. Clearing the tag is a database operation, not a user action.

Common errors

• iDrv4 integration not configured — environment isn’t set up to talk to Ceres. Contact your administrator.
• iDrv4: missing email (or other field) — the customer record on the JATT side is missing data that Ceres requires for the auto-create flow. Edit the customer to add the field, then retry.
• iDrv4: customer match is ambiguous — the customer matches two records on the Ceres side via different fields (e.g., ABN matches one, email matches another). Resolve by providing a single canonical identifier (typically ABN).
• iDrv4 rejected: STATE1 must be a valid abbreviation — the pickup state on the connote isn’t a clean Australian abbreviation (NSW, VIC, QLD, etc.). Edit the job to clean up the state, then retry.
• Network error contacting iDrv4 — transient connectivity. Wait a few seconds and retry.

Out of scope

• Inbound status updates from iDrv4 are not currently flowing back into JATT Portals. Status changes on the iDrv4 side need to be monitored there.
• Re-syncing a job after it’s been edited is not yet supported. Edit JATT-side fields with the understanding that iDrv4’s record will not reflect them.