Skip to content
Vectis

Send failed inspections to your ERP as work requestsNew

Choose which service requests from failed prestart inspections go to your ERP as work requests, and see their numbers and progress in Vectis.

When a prestart inspection fails, Vectis raises a service request. On a connection that raises work requests, those service requests are also sent to your ERP so your workshop sees them without anyone re-keying.

The Work requests card only appears on connections that raise work requests. You need the Manage ERP connections permission to change it.

Choose what is sent

  1. Open the connection

    Go to Settings → Integrations → ERP connections, open the connection and stay on the Overview tab.

  2. Pick the severities

    Under Severities that go out, switch on the severities to send: Critical, High, Medium, Low or Informational. High and Critical are on by default.

  3. Decide whether to read status back

    Switch on Read work request status back, and close the service request when the ERP closes it if you want progress to come back to Vectis.

  4. Check the status map

    The ERP status → Vectis status table says which Vectis status (Open, In progress, Completed, Closed or Cancelled) each of your ERP's statuses means. The defaults for your ERP are shown beneath it. Change a row if your ERP uses its own wording.

  5. Select Save

Statuses only move forward. A work request that has moved on in your ERP does not go back to an earlier status in Vectis.

Where you see the work request

The ERP's work request number appears on the inspection detail and outcome on the web, and in the vehicle's inspection history. Drivers see it on their inspection result in the mobile app: “Work request WR-… in <connection>”, or “Being raised as a work request in …” until the ERP has given a number.

When your ERP closes the work request, the service request closes in Vectis with a note saying so.

Delivery history

On the Delivery history tab each item is labelled Work request, Usage, Odometer or Engine hours. A vehicle that is not linked to an asset in the ERP shows as rejected with a message that it isn't mapped to an asset. Map it on the Asset mapping tab (Map vehicles to ERP asset numbers), then select Resend.

Troubleshooting

A failed inspection did not create a work request

Check that the severity of the service request is switched on under Severities that go out, and that the vehicle is mapped to an asset.

The work request number never appears

Look at the item on Delivery history. If it was rejected, the reason is shown. See Read the sync status screen and fix failures.