The Handheld Devices Settings feature allows administrators to manage and configure handheld devices used for field enforcement and data collection. Its primary purpose is to register new devices, push messages, and update device configurations to ensure seamless operation and accurate data synchronization for field personnel. This article is intended for OPS-COM administrators responsible for managing enforcement hardware.
## Setup and Configuration This feature requires both physical software installation on the handheld devices and backend configuration within the administration portal. **Admin Side:** Administrators must have the **Display as Ticket Writer** permission enabled to use a handheld as a ticket writer. This 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 to 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](https://opscom.wiki/books/setup-configuration-for-admins/page/manage-roles-and-permissions "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. Hover over **Tools** and click **Handhelds Devices**. Alternatively, hover over **Violations** and click **Handhelds Devices**. 2. The Handhelds - Common Settings screen will appear, where you can manage various aspects of your handheld fleet. ### Adding a New Device When adding a new handheld device, the process involves actions on both the physical device itself and within the OPS-COM system configuration. 1. Install the OPS-COM enforcement application directly on the handheld device. 2. Tap the login button on the device to attempt a first login. A notice indicating the device is not registered will appear and display a 16-digit alphanumeric UUID (Universally Unique Identifier). 3. Navigate to the Handhelds - Common Settings page in the admin portal and click the **Add New Device** button. 4. Enter the obtained identifier into the **UUID** field, ensuring you include all characters and any dashes. 5. Click the **Server to Sync with** drop-down menu and choose the **Production Server**. 6. Enter a clear, descriptive name into the **Name** field. 7. Enable the **Enabled** checkbox at the top of the entry form. 8. Click the **Add Device** button to complete the registration. ### Pushing Messages You can send messages directly to your configured handheld units in the field. 1. Click the **Push Message** 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. Click on the specific device name you wish to update to expand a drop-down list of editable settings. 2. Enter your desired changes to the device's configuration. 3. Click the **Process Updates** button to save and apply your changes to the device.To successfully edit a ticket footer for your handheld devices, you must possess the system permission level and role of a Primary Admin.
--- ## Best Practices and Considerations - **Always register on the production server first:** **Due to the underlying logic of the tool, you must always register a new handheld unit on the Production admin portal first, even if its ultimate purpose is for testing on a Preview site.** The system initially connects to the production server, then references the assignment table to determine if a unit is registered for Production or Preview. - **Follow specific steps for preview testing:** **To add a handheld unit to a preview environment for testing, you must configure both servers and perform a device reinstallation.** First, refresh your preview site. Then, add the unit to the production portal but choose your Preview Server from the **Server to Sync with** drop-down menu. Next, enter the exact same device information into the preview admin portal. Finally, perform a fresh reinstallation of the OPS-COM enforcement app on the handheld device itself to pick up the newly set path. - **Reinstall software when switching environments:** **Remember that you must perform a reinstallation of the software on the handheld unit each time you change the synchronization path in the system.** This forces the physical handheld device to update and connect with the newly selected path. - **Ensure UUID accuracy:** **Ensure the UUID is entered precisely, including any required dashes.** Any typographical error will actively prevent the device from connecting to the server. - **Use descriptive 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.