Skip to main content

Replication Status - OPSCOM Enforce App

System Status

The Replication Status screen within the OPSCOM Enforce App displays the synchronization state of all local database tabletables against the central server. Its primary purpose is to help identify connectivity issues and allow users to manually manage data onsynchronization yourwhen unitnecessary. This article is intended for OPS-COM administrators and whetherfield orenforcement staff.

Setup and Configuration

The Replication Status feature is built natively into the application and does not require backend configuration.

Admin Side: No administrative setup is required.

User Side: Users must have the tables/OPSCOM Enforce app installed on their handheld device and be logged in to view the local database tables.

Using this Feature

Enforcement personnel can use this feature to check the health of their connection and manually force data pushes if records are synchronizedfailing withto theupload server.automatically.

    Viewing System Status

    1. Tap on the Replication Status option.option from the main application menu.

    2. This will

      Review bringthe youlist toof database tables on the Record Counts and Data Table Tools. screen.

    3. Tap

    Visual Cues and hold an option to open a pop-up message with additional options. 

Status Report

Status Icons

Indicators

The following icons are used to clearly indicate status:the synchronization status of each individual table:

  • Green Checkmark: Table data is successfully synchronized with the server.

  • Red X: Table data is NOT synchronized with the server.

  • 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

    normal

    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 synced to the server.

    Replication StatusActions area(Table-Specific)

    by

    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 usOPS-COM support containing helpful information for debugging/troubleshooting issues.

          Select if requested to by us, or notify us first before sending if possible.

    Never select the rebuild or delete functions unless explicitly instructed by OPSCOM Support. Doing so can result in the permanent loss of violations or vehicle data that has not yet been synchronized to the server.

    Replication Options

     (System-Wide)

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

    by
      selecting
    1. your

      Tap devicesthe options/Options icon (menu buttonbutton) ( iconlocated 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.

    • 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.

    • Verify synchronization before any rebuilds: If you are instructed to rebuild your database, always ensure you have attempted to push table data to the server first. Verify that all tables marked with a Red X are cleared to prevent catastrophic data loss.

    • Back to top