Skip to main content

Handhelds Devices Settings (Handheld Commons)

The HandheldsHandheld Devices sectionSettings in OPSCOMfeature allows administrators to manage and configure handheld devices used for field enforcement and data collection. ThisIts includesprimary registeringpurpose is to register new devices, pushingpush messages, and updatingupdate device settings,configurations ensuringto ensure seamless operation for field personnel and accurate data synchronization.synchronization for field personnel. This article is intended for OPS-COM administrators responsible for managing enforcement hardware.

Setup and Configuration

InThis orderfeature torequires useboth physical software installation on the handheld asdevices aand ticketbackend writer,configuration youwithin willthe needadministration toportal.

Admin Side: Administrators must have the following permission set:

  • Display as Ticket Writer: Ability to be a ticket writer on the Handheld Tablets or on the system.

This setting comes with the role Patrol Officer by default. To check if this role is set up in your system:

  • Go to System Configuration, Admin Management, and click Manage Roles.
  • Select the role for Patrol Officer and click on the tab for violations.
  • You should see the box labeled Display as Ticket Writer checked.
    • permission
enabled

Forto moreuse informationa onhandheld managingas roles,a clickticket here!

writer.

BeforeThis setting is enabled by default with the standard patrol officer role. Additionally, before accessing a handheld device for the first time, new admin users are strictly required to log in through the online admin portal andto complete their initial password reset.

  1. Hover over System Configuration, click Admin Management, then Manage Roles.

  2. Select the specific role for the patrol officer and click on the Violations tab.

  3. Enable the Display as Ticket Writer checkbox to grant access. Detailed instructions can be found on the Manage Roles and Permissions page.

Using this Feature

Administrators can navigate the management interface to seamlessly add new devices, push direct messages to active units, and update device data.

  1. Click

    Hover over Tools, thenand click Handhelds Devices. Alternatively, youhover can access this on theover Violations menuand asclick well.Handhelds Devices.

  2. The Handhelds - Common Settings screen appears,will appear, where you can manage various aspects of your handheld fleet.

    From here, you can edit settings such as ticket due dates, customize ticket footers, view device information, and add or manage individual handheld units.

Adding a New Device

When adding a new handheld device, the process involves actions on both the physical device itself and within the OPSCOMOPS-COM system configuration.

  1. Install Software: Start by installing the OPSCOMOPS-COM enforcement appapplication directly on the handheld device.

  2. Obtain UUID: After

    Tap the first login attemptbutton on the device,device you'llto receiveattempt a first login. A notice indicating the device isn'tis registered.not This messageregistered will appear and display a UUID (Universally Unique Identifier) number. This is a 16-digit alphanumeric codeUUID typically(Universally foundUnique underIdentifier).

    your
    3. login
  3. screen

    Navigate onto the device.

  4. Register Device in OPSCOM:
    • Once on the Handhelds - Common Settings page in the admin portal,portal and click the Add New Device. button.

    • A new screen will open. You must add the following information:
      • UUID:

        Enter the UUID obtained fromidentifier into the handheldUUID device.

        • field,
      ensuring

You will need toyou include all characters inand any dashes.

  • Click the UUID, including dashes between the groups of characters. Some UUIDs do not have dashes.

        • Server to Sync with: Alwaysdrop-down startmenu byand selectingchoose the Production Server. This is a critical step for initial device registration, regardless of whether the device will eventually be used for testing on a Preview server (explained further in "Production Server.

          First (Crucial)          " under Best Practices & Considerations).
        • Name:

          Enter a clear, descriptive name into the nameName tofield.

          easily identify this device (e.g., "Patrol Unit 1," "Enforcement Officer John's Device").
        • Ensure

          Enable the Enabled checkbox at the top of the entry form is selected.

        form.

      • Click the Add Device oncebutton allto informationcomplete isthe in place.

      registration.

    Pushing Messages

    You can send messages directly to your configured handheld units:units in the field.

    1. On the Handhelds - Common Settings screen, click

      Click the Push Message button.button on the main settings screen.

    2. Follow the on-screen prompts to compose and send your message to the selected devices.

    Updating Device Data

    To modify settings for an existing handheld device:

    1. On the Handhelds - Common Settings screen, click

      Click on the specific device name you wish to update.update Thisto will openexpand a drop-down list of editable settings.

    2. Make

      Enter your desired changes to the device's configuration.

    3. Once finished,

      Click ensure you clickthe Process Updates button to save and apply your changes to the device.

    To successfully edit thea ticket footer,footer for your handheld devices, you must havepossess the system permission level and role of a Primary Admin.

    Best Practices &and Considerations

    • ProductionAlways Serverregister Firston (Crucial)the production server first::

      • Important Note: Due to the underlying logic of the Handheld Common tool, you must always register a new handheld unit on the Production admin portal first,first, even if its ultimate purpose is for testing on a Preview site.
      • The system initially connects to the production server, then references the PA Common/handheld assignment table (which is written from production) to determine if a unit is registered for Production or Preview. This ensures the correct routing is established in the database.
      • This initial production-side registration is also why you can refresh preview sites without losing the handheld units configured for them.

    • AddingFollow aspecific Handheld Unit to Previewsteps for Testingpreview testing::

      1. Start by refreshing your preview site to ensure it’s using the latest data. For details, see Create or Refresh a Preview Space.
      2. First,To add thea handheld unit to Handheldsa -preview Commonenvironment Settingsfor testing, you must configure both servers and perform a device reinstallation. onFirst, refresh your preview site. Then, add the unit to the production admin portal as described in "Adding a New Device," but selectchoose your Preview Server infrom the Server to Sync with field.drop-down Thismenu. sets the proper database route.
      3. Next, navigate to the preview admin portal and enter the exact same device information into itsthe Handheldspreview -admin Commonportal. Settings section.
      4. Finally, perform a fresh reinstallation of the OPSCOMOPS-COM enforcement applicationapp on the handheld device itself. This reinstallation allows the handhelditself to pick up the newly set path to the preview server.path.

    • SwitchingReinstall Betweensoftware Productionwhen andswitching Previewenvironments::

      • Once a handheld entry exists in both Production (configured for Preview sync) and Preview, you can generally switch between environments by re-pointing the SyncRemember With setting on both the Production and Preview admin portals to your preferred path.t
      • However, remember thathat you must performperform a reinstallation of the software on the handheld unit each time you change the synchronization path in the systemsystem. forThis forces the physical handheld device itself to update and connect with the newly selected path.

    • Ensure UUID Accuracyaccuracy:: Ensure the UUID is entered precisely, asincluding any required dashes. Any typographical error will actively prevent the device from connecting.connecting to the server.

    • DescriptiveUse Namingdescriptive naming conventions:: Use clear, identifiable names for your handheld devices to simplify management and troubleshooting. Standardizing names like "Patrol Unit 1" or "Enforcement Officer John's Device" makes identifying hardware in the system much easier.

    • Back to top