Edunet
Book a repair out to Edunet and follow the job without leaving the repair.
| Category | Repair vendor |
| Authentication | OAuth client credentials (client ID and client secret) |
| Reaches | Edunet’s ServiceConnect API (/api/v1) |
| Needs an agent | No |
| Demo mode | Yes |
Capabilities
Section titled “Capabilities”repair.lodge, repair.getStatus, repair.addNote, repair.addAttachment
Together these light up Book vendor repair on a repair, the vendor status on the repair page, and the Send note and Attach a photo controls under Vendor & communications once a job is open.
What it syncs
Section titled “What it syncs”| Direction | What |
|---|---|
| To Edunet, when you book | A service job with the device’s serial number, its model, the fault (the repair’s reason, or its repair type), the person’s name, and the repair’s own ID as Edunet’s external reference |
| To Edunet, afterwards | Notes you send and photos you attach, as notes and attachments on the job |
| From Edunet | Whether the job is open or closed, and the job’s notes, including Edunet’s closing notes |
The repair’s ID goes in Edunet’s external reference field, so either side can find the job from the other.
A repair covered by one of the school’s cover agreements is lodged as an insurance claim: the fault Edunet receives starts with the policy number, because Edunet’s job has no separate policy field.
Getting the credentials
Section titled “Getting the credentials”- Sign in to Edunet’s service portal with your school’s account.
- Open API Credentials.
- Copy the client ID and client secret.
If your account does not show API Credentials, ask your Edunet account manager to turn API access on.
Configuring it in Plugboard
Section titled “Configuring it in Plugboard”Admin, Connectors, Edunet, Configure.
Settings
Section titled “Settings”| Field | Default | Value |
|---|---|---|
baseUrl |
https://service.edunet.com.au |
The ServiceConnect API base. Leave the default unless Edunet gives you another address |
organisationSiteId |
empty | Which of the school’s Edunet sites a job is lodged against. Save and test lists your sites with their IDs |
claimType |
empty | Edunet’s claim type ID for the jobs it lodges, if Edunet asks you to set one |
contactResponsibility |
empty | Edunet’s contact responsibility ID, if Edunet asks you to set one |
deviceLocation |
empty | Edunet’s device location ID, if Edunet gave you one |
demoMode |
false |
Return fixture data |
Edunet’s API marks none of these as required, so any you leave empty are left out of the job. If Edunet refuses a job, set the IDs it names.
Credentials
Section titled “Credentials”| Field | Value |
|---|---|
clientId |
The client ID from API Credentials |
clientSecret |
The client secret from API Credentials |
Save and test. A working connection says “Connected to Edunet” and lists
the school’s Edunet sites, for example Senior campus (12). Copy the number
into organisationSiteId and save again.
Authentication
Section titled “Authentication”Plugboard asks Edunet for an access token with the client credentials grant,
posting the client ID and secret as form fields to /api/oauth/token under
the base URL. It sends the token as a Bearer header on each call.
- The token is only ever sent to the base URL’s own address. Redirects are refused, so a misconfigured address cannot carry the token anywhere else.
- The token address is built from the base URL, not discovered. Edunet’s published discovery document names a local development address as its issuer, so it is not used.
- A fresh token is requested for each piece of work, so a status check is two requests.
How a vendor repair works
Section titled “How a vendor repair works”- A technician opens a repair and chooses Book vendor repair.
- Plugboard opens a service job with Edunet, records Edunet’s job ID on the repair, and moves the repair to At vendor.
- On the repair page, the technician can send Edunet a note (what the student reported, what was already tried) or attach a photo of up to 6 MB. Each one is recorded in the audit log.
- The repair page reads the job’s status and notes from Edunet each time it opens. Edunet’s notes appear in the repair’s history, marked Vendor.
- Every hour, Plugboard checks each repair sent to Edunet. A job Edunet has closed moves the repair to Ready for collection, which tells the person it is ready the same way a technician pressing the button would.
The hourly check only moves a repair forward. A repair a technician has already moved past this point is left alone.
Statuses
Section titled “Statuses”| Edunet says | Shown as | Effect |
|---|---|---|
| The job is open | In progress | None. The repair stays At vendor |
| The job is closed | Completed | The hourly check moves the repair to Ready for collection |
| No such job | Unknown | None. The repair stays where it is |
Edunet reports a closed flag rather than a set of states, so any job Edunet closes, for whatever reason, reads as Completed. Check Edunet’s closing note in the repair’s history before you hand the device back.
Turning the feature on
Section titled “Turning the feature on”Vendor repair is one of the workflow switches. If Book vendor repair does not appear on a repair, open Admin, Workflow and check that Vendor repair is on. See workflow.
Limits
Section titled “Limits”- One repair vendor at a time. With two repair-vendor connectors enabled, status checks, notes and photos cannot tell which vendor holds a job and stop with “More than one connector is configured”. Enable Edunet or another repair vendor, not both. A repair lodged as a claim goes through the vendor its cover agreement names.
- Mapped status only. The repair page shows In progress or Completed, not Edunet’s own wording for where the job is.
- Files, not links. Photos are sent to Edunet as the file itself. Nothing is published at a public address to get there.
- Job IDs. Plugboard accepts Edunet job IDs made of letters, digits, hyphens and underscores, up to 64 characters, and refuses anything else before it reaches the request.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause |
|---|---|
| “Edunet needs a client id and a client secret” | One of the credentials is empty |
An Edunet error on test, such as invalid_client |
The client ID or secret is wrong, or the client was removed in Edunet’s portal |
| “Edunet accepted the request but returned no job id” | Edunet took the request without opening a job. Check the site and claim type IDs with Edunet |
| Book vendor repair is missing | The Vendor repair workflow switch is off, or no repair-vendor connector is enabled |
| “More than one connector is configured” | Two repair-vendor connectors are enabled. Disable one |
Fixture jobs appear (EDU-DEMO-1001) |
demoMode is still on |
Related
Section titled “Related”CompNow is the other repair-vendor connector. Apple GSX answers whether a repair is covered, which is a different question from who is doing it.