Runsheets / Mobile Runsheets : Creating, Updating, Archiving, Backdating

Create a Runsheet

POST /mobile-runsheets

{
   "name": "Vehicle zones runsheet",
   "customId": "",
   "dayOfWeek": "SATURDAY",
   "rangeStartTime": "18:00:00",
   "timeRangeStart": "18:00:00",
   "rangeEndTime": "06:00:00",
   "timeRangeEnd": "06:00:00",
   "zonePosition": 1,
   "zone": 3,
   "region": 2,
   "beginDate": "2023-10-21T00:00:00+00:00",
   "endDate": null
}

Notes

zonePosition : these are /positions ID numbers where the account type happens to be a Zone

beingDate : this is ideally from now and future, but you can backdate it. 2024-02-08 You can’t backdate this via the web portal application, only via API


Patching the beginDate or status

2024-02-08 : not available via API. Use the web portal application.


Archiving/Deleting the Runsheet

2024-02-08 : not available via API. Use the web portal application.


Backdating and Web Application caching

2024-02-08 It can happen that after creating a backdated runsheet that the web portal if open at the time on the view where it will appear will only display it as an “archived and expired” item. But if you refresh the view a couple times it will then show up properly without the additional filter.

image (31).png

vs after refresh:

image (32).png

 

 

Was this article helpful?
0 out of 0 found this helpful

Articles in this section