You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MasterLog needs to be generated as JSON because querying for past loads is unreliable, as users may change their names/equipment/weights/etc which means the data in the master log doesn't accurately provide a snapshot of that day.
Suggest creating an interaction that builds a JSON snapshot of all necessary data, and running this at midnight every day for each dropzone, and if it's speedy enough, maybe every time a load is cancelled or marked as landed as well.
Additionally, we need a way of rendering this snapshot, which means building GraphQL types to retrieve the data, e.g Types::MasterLog::Load, Types::MasterLog::Slot, etc, and adapt the master log screen to query and render this data, and a PDF template to create daily master log PDFs to download at the end of each day
The text was updated successfully, but these errors were encountered:
MasterLog needs to be generated as JSON because querying for past loads is unreliable, as users may change their names/equipment/weights/etc which means the data in the master log doesn't accurately provide a snapshot of that day.
Suggest creating an interaction that builds a JSON snapshot of all necessary data, and running this at midnight every day for each dropzone, and if it's speedy enough, maybe every time a load is cancelled or marked as landed as well.
Additionally, we need a way of rendering this snapshot, which means building GraphQL types to retrieve the data, e.g
Types::MasterLog::Load
,Types::MasterLog::Slot
, etc, and adapt the master log screen to query and render this data, and a PDF template to create daily master log PDFs to download at the end of each dayThe text was updated successfully, but these errors were encountered: