Replication Status (Legacy)

Note: During normal use (i.e., when issuing violations), it's expected that tables like VehicleTransfer and ViolationsTransfer may become temporarily out of sync. This indicates that new data (e.g., violations or vehicles) has been captured on your device and will need to be synced to the server.

• Blue Exclamation Point: This indicates thereThere is currently no table data that needs to be synchronized between the handheld and the server.

Replication

During Actions

Thereuse are(i.e., when actively issuing violations), it is completely expected that tables like VehicleTransfer and ViolationsTransfer may temporarily display a numberRed ofX. actionsThis simply indicates that cannew bedata performedhas been captured on your local device and is waiting in the queue to be pushed to the server.

Replication StatusActions area(Table-Specific)

You holdingcan downperform withtargeted your fingeractions on individual tables if they are stuck or experiencing issues.

1. Tap and Hold an individual table:table to open a pop-up message with additional options.

2. PLEASETap NOTE: None of these options should have to be used if your unit is working correctly. We suggest logging in and outone of the applicationfollowing as needed for proper synchronization. Please contact OPSCOM Support if there are any issues before performing any replication status functions as detailed below.actions:

   • Push table data to the serverserver:

     • This will attempt to manually upload the local devicesdevice's table data to the serverserver. (i.e. synchronize) andThis is generally safe to dodo, as nothing is overwritten or removed, though if you do push table data make sure all tables marked with a red X are synchronized.
     removed.

   • Rebuild and retrieve table datadata:

   Warning: This option will delete/droppermanently delete the local table data and retrieve the newest available table data from the server. This could result in violations and/or vehicle data that hasn't yet been synchronized to the server and is still only on the local handheld from being lost. If a table is showing as out of sync never rebuild and retrieve table data unless instructed to by us.

   • Delete local table datadata:

   Warning: This will permanently delete the local table data but has no effect on the server. Similar to the above this could result in the loss of local table data if not synchronized to the server first. Never select this function unless told to by us.

   • Email debug details to TomahawkTomahawk:

     • This will send an email log file to usOPSCOM Support containing helpful information for debugging/troubleshooting issues.
       Select if requested to by us, or notify us first before sending if possible.

Replication Options

There are additional system-wide options available into manage the Replicationentire Statusdatabase areaat accessibleonce.

selecting
1. your

   Tap devicesthe options/menu button (Menu icon located in the top right-hand corner):corner of the screen.

2. Tap one of the following actions:

   • Rebuild database:

   WARNING: This will delete ALL local table data but has no effect onacross the server.entire This could result in the loss of local table data if not synchronized to the server first. Never select this function unless instructed by OPSCOM Support.device.

   • Synchronize all:

     • This function is safe to select and is similar, if not the same as logging in or out of the device. The device will attempt to safely synchronize ALL table data with the server. We still recommend logging in and out instead of using this function in case another option is selected by accident.

   • Send config to Tomahawk:

     • This will send ana comprehensive email log file to us containing helpful informationsupport for debugging/troubleshooting issues. Select if requested to by us, or notify us first before sending if possible.
     debugging.

   • Download new config:

     • When selected theThe device will re-download all relevant system settings on(e.g., nextorganization startup (organization,details, device name, ticket footer,footer) etc.).on the next startup.

Best Practices and Considerations

• Rely on standard login for synchronization: If your unit is working correctly, none of these manual options should be necessary. We highly recommend simply logging out and logging back into the application as needed, which acts as a safe, natural trigger for proper synchronization.

• Avoid unauthorized rebuilds or deletions: Never select the rebuild or delete functions unless explicitly instructed by OPSCOM Support. Doing so without manually pushing your data first can result in the permanent loss of violations or vehicle data that has not yet been synchronized to the server.

• Communicate before sending logs: If you need to use the Email debug details option, please notify the OPS-COM support team first if possible, or only select it when actively requested by a support technician.