This writes to FleetRock. Dry run shows exactly what would be sent and touches nothing.
Send actually posts to the repair order — use a test RO. Nothing here runs on a schedule;
every send is a button you press.
What are you testing?
Both proven on RO 5145436, 9/2/26. Custom data was tried and dropped — FleetRock
returns only the custom fields configured in FleetRock, so notes and attachments are the whole
of what we write. The fault-to-RO link comes off our own case ledger instead.
1 The repair order
The ro_id UpdateRO writes to.
GetRO searches by created date, so the read-back needs the day the RO was made.
2 The note
FleetRock appends when notes already exist, so each send adds a line rather than replacing what is there.
3 Attachment — optional, this is the v2 test
A PDF or image, sent as base64. Capped at about 4 MB of file — bigger ones are refused
with the size named rather than sent truncated and arriving corrupt.
Dry run first. Always.
Read-only — mints a token for each login and reads the last two weeks of repair orders with both. The RO above is optional. Writes nothing.