CompNow
Book a repair out to CompNow and track it without leaving the submission.
| Category | Repair vendor |
| Authentication | API token |
| Reaches | The CompNow repair API |
| Needs an agent | No |
| Demo mode | Yes |
Capabilities
Section titled “Capabilities”repair.lodge, repair.getStatus
Which lights up the Send to vendor action on a submission, available when the vendor repair workflow feature is on.
Getting the credentials
Section titled “Getting the credentials”CompNow’s API access is arranged per account rather than self-service.
- Contact your CompNow account manager and ask for API access for repair lodgement and status.
- They will provide a base URL and an API token.
If your school buys through CompNow but has never used their API, this is a conversation rather than a form. Expect it to take a few days.
Configuring it in Plugboard
Section titled “Configuring it in Plugboard”Admin, Connectors, CompNow, Configure.
Settings
Section titled “Settings”| Field | Default | Value |
|---|---|---|
baseUrl | empty | The CompNow repair API base URL |
demoMode | false | Return fixture data |
Credentials
Section titled “Credentials”| Field | Value |
|---|---|
apiToken | The API token |
Save and test.
How a vendor repair works
Section titled “How a vendor repair works”- A technician opens a submission and chooses Send to vendor.
- Plugboard lodges the repair with CompNow and records the vendor’s reference on the submission.
- Status is synced back periodically, so the submission reflects where the job actually is without anybody phoning to ask.
- The person’s tracking page shows the submission status, so a device away at a vendor is not a black hole for the family.
Turning the feature on
Section titled “Turning the feature on”Vendor repair is one of the workflow feature switches. If Send to vendor does not appear on a submission, check Admin, Workflow and confirm the vendor repair switch is on.
See workflow.
Practical notes
Section titled “Practical notes”Keep a status for it. Add a status like “With vendor” so the queue makes it obvious which devices are off site. A submission sitting in “In progress” for three weeks because it is at a vendor looks like a problem with your desk.
The loan matters more here. A vendor repair takes longer than a bench repair, so the person is on a loaner for longer. That is fine, and it is worth being deliberate about which pool those come from. See loan groups.
Coverage and cost. The coverage recorded on the repair type determines who pays. A warranty job sent to a vendor should not end up recorded as chargeable just because a vendor invoice arrived.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause |
|---|---|
401 on test | Wrong token, or API access not enabled on your account |
| Send to vendor is missing | The vendor repair workflow switch is off, or no repair vendor connector is enabled |
| Lodges but status never updates | The vendor reference was not returned, or the status sync cannot see the job |
| Fixture jobs appear | demoMode is still on |
Related
Section titled “Related”Apple GSX answers whether a repair is covered, which is a different question from who is doing it. Many schools use both.