System Settings

• Reset Settings for OPSCOM Parking Enforcement
• OPSCOM Parking Enforcement Admin System Settings

Reset Settings for OPSCOM Parking Enforcement

The Reset Settings feature within the legacy Android application allows users to clear local device configurations and force the handheld to pull fresh data from the server. Its primary purpose is to troubleshoot and resolve synchronization or configuration issues on the mobile device. This article is intended for OPSCOM administrators and field enforcement personnel acting under the guidance of support staff.

Setup and Configuration

This troubleshooting feature is natively built into the application and does not require any backend configuration to activate.

Admin Side: Before initiating a reset, ensure the handheld device is connected to a stable Wi-Fi or cellular network, as the application will need to download a fresh batch of data upon the next login.

Using this Feature

Enforcement personnel should only use this feature when experiencing specific device issues and only under direction from the support team.

Resetting the Application Settings

1. Log in to the OPSCOM Parking Enforcement app.

2. Tap System Settings from the main menu.

3. Scroll down to the bottom of the settings list and tap the Reset Settings checkbox to select it.

4. Tap the device's back button and log out of the application completely.

5. Fully close the application from the Android recent apps menu.

6. Restart the tablet or handheld device.

7. Log in to the OPSCOM Parking Enforcement app. The system will automatically re-download all system settings and related data during this initial login.

---

Best Practices and Considerations

• Ensure a stable network connection: Always verify your device has a strong cellular or Wi-Fi signal before logging back in. Because the reset clears local data, a stable connection is required to successfully pull the fresh settings from the database and resume normal operations.

Authorized Use Only Do not perform a settings reset as a standard troubleshooting step. The reset settings function should only be performed if you have been explicitly told to do so by an OPS-COM Support representative.

OPSCOM Parking Enforcement Admin System Settings

The OPSCOM Parking Enforcement Admin System Settings feature allows administrators to configure core global variables that synchronize directly to the mobile enforcement handhelds. Its primary purpose is to ensure all printed tickets and app interfaces consistently display the correct organizational details, locations, and legal footers. This article is intended for OPS-COM administrators.

Setup and Configuration

These foundational settings must be configured within the core administrative portal before the handheld units can be properly deployed to the field.

Admin Side: Hover over System Configuration and click System Settings to access the main configuration portal.

User Side (Enforcement Staff): No configuration is required on the handheld device to receive these settings. The mobile enforcement units will automatically download these core variables during their next routine synchronization with the server.

Using this Feature

Administrators can use this interface to update the organization's core identity details and customize the legal text that prints at the bottom of physical citations.

Setting the Organization Name and Country

1. Click General System Settings from the list of components on the left side of the screen.

2. Type your organization's official title into the Organization Name field.

3. Type your location into the Country field.

4. Click Save Settings to apply the changes to the database.

Editing the Handheld Footer

1. Click Violations from the list of components on the left side of the screen.

2. Locate the Handheld Footer field in the top portion of the configuration form.

3. Type the exact legal or instructional text you want printed at the bottom of all physical parking tickets.

4. Toggle the appearance of the pin numbers on the violation in this same area, depending on your organization's payment portal requirements.

5. Click to save your configuration changes.

Example Footer Message A standard and effective ticket footer message should look something like this: This parking ticket is due within 14 days. Failure to settle this parking ticket will result in the account becoming delinquent and subject your vehicle to collections and/or towing.

---

Best Practices and Considerations

• Configure across proper environments: Administrators must be aware that settings pushed to a specific site environment (preview or production) do not automatically sync to the other. If you configure a handheld device while connected to the production site, it will not be configured for the preview site, and vice versa.

• Follow the recommended device setup sequence: Always add and configure the handheld device through the preview environment first, and then set it up on the production environment. This specific deployment sequence ensures that the device settings are properly written to the PA_Common tables for both environments simultaneously, preventing future synchronization conflicts.