Admin Tools & Data Maintenance

Items on the tools menu control rarely accessed but important setup and configuration tools for OPS-COM.  Data Maintenance options are also here.

Resolve Duplicate Options

The Resolve Duplicates feature in OPS-COM allows administrators to identify and merge duplicates by email, student number, staff number and vehicle (plate) in the system. This is crucial for maintaining data accuracy, preventing operational errors, and ensuring that enforcement and permit management processes are based on clean, unique vehicle data. This article focuses on resolving duplicates by vehicle, however, the concept is the same for other data types.

  1. Click on Tools, hover over Resolve Duplicates, then click By Vehicle.

Using this Feature

On the Resolve Duplicates By Vehicle page, you will be presented with options to define the criteria for identifying potential duplicate vehicle records.

Duplicate Identification Options

There are two choices to generate a list of potential duplicates:

Strict Duplicate

Purpose: This option generates a list of vehicles where all three primary unique identifiers are identical. This is for finding exact, unambiguous duplicates. Unique identifiers are:

Include Different Plate Types

Purpose: This option generates a list of vehicles where the Plate and State/Province are identical, but the Plate Type may differ. This is particularly useful for identifying potential input errors where a vehicle might have been entered twice with the correct plate and province, but an incorrect or unspecified plate type was initially used.

Example: If a vehicle is a beige BMW sports car with plate ABC123, province Ontario, and an unspecified Plate Type, but there's another record for a beige BMW sports car with plate ABC123, province Ontario, and Plate Type Passenger, it is highly probable that these are the same vehicle entered as a duplicate. Comparing the vehicle description (make, model, color) can help confirm such cases.

Resolving Duplicates

Once a list of potential duplicates is generated based on your chosen criteria:

  1. Review the list carefully, paying close attention to vehicle descriptions and other details to confirm actual duplicates.
  2. For each pair of duplicate records you wish to merge, click the Merge button provided next to the entries.
  3. Clicking Merge will take you to the merge function window, where you can select which information to retain from the duplicate records and then finalize the merge.

2024-08-13_14-41-29.png


Best Practices & Considerations

History Search

The History Search feature in OPS-COM allows administrators to quickly locate and review historical system activities and events. This tool is invaluable for auditing, troubleshooting, and investigating specific actions related to users, vehicles, or violations, providing a comprehensive log of system interactions.

Using this Feature

1. Click Tools, then History Search. The History Dump page will be displayed.

You can search using a single identifier or a combination of them to narrow down your results.

Available Search Criteria
Steps to Perform a History Search
  1. On the History Dump page, enter your desired search criteria into one or more of the available fields (e.g., enter a specific Violation Ticket number, as shown in the example) and click Submit.
  2. All OPS-COM history records that match your entered search criteria will be displayed. 

Best Practices & Considerations

Purge Old - Explained

The Purge Old Data feature in OPS-COM allows administrators to remove inactive historical records from the system. This process is essential for maintaining database efficiency, improving system performance, and ensuring that your data remains relevant and manageable by automatically archiving or deleting old, unused information. The only records that will be purged are ones that have not had any activity associated with them for more than 7 years.


Using this Feature

1. Click Tools, then Purge Old Data.

When you click Purge Old Data, the system initiates a process to identify records that meet the purging criteria.

  1. Upon activation, a progress bar will appear, indicating the number of records being identified for potential purging. The system compiles a list of any user activity and associated record updates that have occurred within the last seven years.
  2. The compiled "activity list" determines which data to exclude from the purge. The script then proceeds to purge any data that is not on this active list.
  3. To complete the process and execute the purge, click Purge these records.

An important business rule is that any small update or activity on a record will "restart" its 7-year clock, meaning the record will then be excluded from purging for another seven years from that last activity date.

What Gets Purged?

The following record types will be purged if they have had no activity in the last 7 years:

What Does NOT Get Purged?

The following record types will NOT be purged, regardless of their last updated date, ensuring the retention of critical historical and incident-related information:


Best Practices & Considerations

Purging Incidents

The ability to purge incidents from OPS-COM allows administrators to permanently remove outdated incident records from the system. This process is critical for maintaining data relevance, complying with data retention policies, and optimizing database performance. This article outlines the two methods for incident purging: individual deletion via incident search and bulk deletion using the Purge Incidents tool.

Setup & Configuration

To enable incident purging capabilities for an administrator, specific permissions must be granted.


Using this Feature

There are two primary methods for purging incidents in OPS-COM: individually through the Incident Search, or in bulk using the Purge Incidents tool.

Method 1: Using the Delete Incident Button (Individual Purge)

This method allows for the deletion of a specific incident after searching for it.

  1. Search for the incident you wish to purge using the standard Incident Search functionality.
  2. Once the incident details are displayed, observe the Delete Incident button.
    • The Delete Incident button will be available (active) only if the incident record is older than 7 years.
    • If the incident is less than 7 years old, the button will appear as "Delete Not Available" and will be greyed out, preventing deletion.
  3. If the button is active, click the Delete Incident button.
  4. Follow any subsequent prompts or confirmation messages to finalize the deletion of the incident.
Method 2: Using the Purge Incidents Tool (Bulk Purge)

This tool allows for searching and purging multiple incidents simultaneously based on specified criteria.

  1. Click Tools, then Purge Incidents.
  2. The Search for Incidents to Purge screen will be displayed.
  3. Enter your search criteria into the available fields (e.g., date ranges, incident types, specific IDs).
    • The results displayed will be limited to the oldest 300 records that match your criteria.

      Note: When entering a value for "Number of Instances," the search field functions as "greater than or equal to." Therefore, supplying "1" might still display incidents with more than one instance.

  4. Review the displayed list of incidents.
  5. Enable the Delete checkbox next to each incident you wish to purge.
  6. Click the Purge Records button.
  7. A confirmation prompt will display. Click the Delete button within this prompt to confirm the action.

Best Practices & Considerations

      Handheld Devices and Commons

      The Handhelds Devices section in OPS-COM allows administrators to manage and configure handheld devices used for enforcement and data collection. This includes registering new devices, pushing messages, and updating device settings, ensuring seamless operation for field personnel and accurate data synchronization.

      Refer to this wiki article for more information.

      Managing Recurring and Onetime System Tasks

      OPS-COM utilizes both recurring and onetime system tasks to automate various back-end processes, such as data synchronization, report generation, or system clean-up. This article guides OPS-COM administrators on how to access, monitor, enable, and disable these critical system tasks, ensuring efficient operation and maintenance of the OPS-COM environment.

      Accessing System Tasks

      1. Click Tools (the Toolbox), then click View System Task Logs.
      2. On the Scheduled Tasks page, there are two sections, Recurring tasks and Onetime tasks. From this screen we can see stats on when the task has run and how long it took to run. We can also enable or disable tasks from running.

      The Scheduled Tasks page is divided into two main sections: Recurring tasks and Onetime tasks. For each task listed, administrators can view its status, statistics, and manage its execution.

      Key Information Displayed 
      Available Actions & Buttons

      Please be aware, there are other settings that may be important to set correctly before enabling any system task.

      image.png


      Best Practices & Considerations


      Using the Database Importer (Beta)

      The Database Importer in OPS-COM provides administrators with a powerful tool to import existing data into the system using CSV files. This functionality is essential for initial data migration, mass updates, or integrating data from external systems, ensuring that your OPS-COM database is populated and maintained efficiently. This tool is currently in BETA.

      Setup & Configuration

      1. Click Tools, then Database Importer to access the tool.
      Permissions Requirements

      If the Database Importer page is not visible, the user's account does not have the necessary permissions enabled. To allow a user to import or manage data, the following permissions must be configured:

      These permissions can be found under the Systems tab of the permissions management page. Enable them to grant a user access to the Database Importer functionality. For more information on configuring permissions, please refer to the User Roles and Permissions wiki article.


      Using this Feature

      The Database Importer allows data to be imported into a select number of tables within OPS-COM.

      Currently Supported Tables for Import
      Importing Data into a Table

      To begin a new import:

      1. Click the Upload button next to the desired destination table that you wish to import information into.
      2. A modal window will open, prompting you to select the CSV file. Your imported CSV file can be comma-differentiated or semi-colon-differentiated.
      3. Once a file has been selected, click Submit to begin the upload process.
      4. After the CSV file has been successfully uploaded, the Table Import screen will appear.

      Converting Fields to Text to Avoid Truncating Leading Zeros - When converting data from Excel to CSV, issues can arise, such as the truncation of leading zeros in numbers (e.g., student IDs, staff numbers). To prevent this, you can force Excel to treat cells as text before converting to CSV as below:

      1. Open a new sheet in your Excel workbook.
      2. In cell A1 of the new sheet, type the formula: ="'"& then click on cell A1 of your original spreadsheet. (This formula is: equals sign, double quote, apostrophe, double quote, ampersand, then the cell reference.)
      3. Drag this formula down and across through the same number of rows and columns as your original data. This will replicate your data on the new page, but an apostrophe (') will be placed in front of all values, forcing Excel to treat them as text.
      4. Save the new sheet as a .CSV file. Ensure you only save the new page. This method effectively preserves leading zeros during the CSV conversion.

      Column Matching

      On the Table Import screen, you will match the columns from your imported CSV file to the corresponding columns in the destination table within OPS-COM.

      Once the columns have been properly matched and you click the Process button, you will be redirected back to the main page while the import is completed in the background.

      Post-Import Processing and Settings

      After the initial import of data into the base table, some tables run additional processing on the information to establish relationships and apply default settings. These processes run separately from the initial import and are not affected by the duplicate settings chosen for the import.

      Status Emails

      Over the course of the import process, a total of two emails will be sent to the user who initiated the import:

      Table-Specific Post-Processing Details
      Order of Operations for Related Imports

      Imports that contain related information should generally be done in a specific order, as some tables contain information that references another table. While imports can be done out of order, records may not be associated correctly if their dependencies aren't met. In general, the tables a record requires should be imported before that record's table.

      Table to Import Requires (Imported Before) Notes
      UserProfile (None) This should generally be the first table imported.
      Vehicles UserProfile Having the user record created before the vehicle allows the user to be associated with the vehicle by a VehicleJoin record created during post-import processing.
      OffenceLocations (None) Does not require any data beforehand but should be imported before Violations to ensure proper location marking.
      Permits Vehicles, UserProfile Having a vehicle record created before the permit allows the permit to be associated with the vehicle by a PermitJoin record created during post-import processing. If there is also an associated user record, the permit can be marked as paid by joining the user and permit through a payment record (if the option was selected).
      Violations Vehicles, UserProfile, OffenceLocations A violation requires the existence of a vehicle record beforehand for the violation to be created at all. Offence locations should be imported before violations for the violation to have its location properly marked.
      User-Association Settings

      Some tables include additional post-processing to associate newly-created records with existing users. For this to work, the unique identifier for the user (UserUUID or Email) must be selected consistently for both the user's primary record and any associated records (Vehicles, Permits). Ensure the same value is selected for both sections during the import setup.

      The tables that currently have this user-association option are:

      Unique Identifiers & Duplicate Settings

      The Unique Identifiers are the columns used to determine if a record's information is unique. If the information in these columns is duplicated in the file or already exists in the system, it will be handled based on your selected Duplicate Settings:

      The number of columns that mark a record as unique varies by table:

      Foreign Lookup Columns

      Some data in one table originates from another table and is stored as an ID in the destination table (known as a foreign key).

      Below is a list of common foreign lookup columns and their source tables:

      Inserting Into Table Column Inserting Into Sourced From Table
      UserProfile prov Provinces
        UserTypeID UserTypes
      Vehicle ProvID Provinces
        ColourID VehicleColours
        MakeID VehicleMake
        TypeID VehicleType
        PlateTypeID VehiclePlateType
      Permits LotNameID LotName
        StateID PermitState
      Violations VehicleID Vehicle
        TicketType TicketCategory
        LocationID OffenceLocations
      Table Reset

      In addition to importing data, the Database Importer page also allows for the purging of an entire table's contents.

      1. Click the Reset button next to the table you wish to empty.
      2. A new modal window will open, prompting you to confirm that you wish to delete the contents of the table. 

        • Irreversible Action: This action is permanent. Once the data is deleted, it cannot be recovered. Ensure you are absolutely certain before proceeding.

      3. If you are certain the data should be deleted, type DELETE (in all caps) into the confirmation text field and press the Delete button.

      4. The selected table will then be purged of all records.

      Some tables are closely connected to the records of a related table. Removing the data they contain will also purge the contents of the related table:

      Note: Only the table contents are deleted; the table structure itself remains intact.


      Best Practices & Considerations

      Importer Field Descriptions

      This article provides a comprehensive guide to the fields used within the OPS-COM Database Importer. For each supported table, you'll find a list of column names, their internal system names, their requirement level (Unique ID, Recommended, Optional), data type, and a detailed description, ensuring you can prepare your CSV files accurately for successful data imports.

      Understanding Field Requirements

      When preparing your CSV files for import, it's essential to understand the different levels of field requirements:


      Importer Columns

      Below is a detailed breakdown of the columns available for each supported import table, including their internal names, requirement levels, types, and descriptions.

      UserProfile Table

      Column Name

      Internal Name

      Requirement

      Type

      Description

      User Unique ID (UUID)

      UserUUID

      Unique ID

      • This or Email is Required

      Standard

      The primary identifier. If UUID is not supplied, email will be used as the key identifier instead.

       

      This value identifies the user as a unique record and it or the email is required to import a record.

      Email Address

      email

      Unique ID

      • This or UUID is Required

      Standard

      The secondary identifier. If UUID is not supplied, email will be used as the key identifier instead.

       

      This value identifies the user as a unique record and it or the UUID is required to import a record.

      Username

      username

      Recommended

      Standard

      The username of the user.

      First Name

      firstName

      Recommended

      Standard

      The first name of the user.

      Middle Name

      middleName

      Optional

      Standard

      The middle name of the user.

      Last Name

      lastName

      Recommended

      Standard

      The last name of the user.

      Password

      password

      Optional

      Standard

      The password of the user.

      User Type

      UserTypeID

      Recommended

      Foreign Key

      • UserTypes Table

      The user type of the user. Attaches to the UserTypes table.

       

      The values supplied by the user in the uploaded file are expected to be values from the TypeName column of the UserTypes table, as these are the values that will be matched against.

       

      The values in the uploaded file must be an exact match to the values in the TypeName column, matching the capitalization, spelling, and spacing exactly, or else it won’t be counted as a match.

       

      The UserTypeID from the UserTypes table matching the name will inserted into the record in the base table. The value will be left blank in the imported record if no matches are found.

      Street Address

      street

      Optional

      Standard

      The street address of the user.

      City

      city

      Optional

      Standard

      The city of the user.

      Province/

      State

      prov

      Optional

      Foreign Key

      • Provinces Table

      The province or state of the user. Attaches to the Provinces table.

       

      The values supplied by the user in the uploaded file are expected to be values from the ProvName column of the Provinces table, as these are the values that will be matched against. These are the long names of the province and not the abbreviation; as in, Ontario and not ON.

       

      The values in the uploaded file must be an exact match to the values in the ProvName column, matching the capitalization, spelling, and spacing exactly, or else it won’t be counted as a match.

       

      The ProvID from the Provinces table matching the name will inserted into the record in the base table. The value will be left blank in the imported record if no matches are found.

      Postal Code

      postal

      Optional

      Standard

      The postal or ZIP code of the user.

      Cellphone Number

      phonecell

      Optional

      Standard

      The cellphone number of the user.

      Employee Number

      employNo

      Optional

      Standard

      The employee number of the user.

      Student Number

      studentNo

      Optional

      Standard

      The student number of the user.

      Secondary Phone Number

      sPhone

      Optional

      Standard

      The secondary phone number of the user.

      Date of Birth

      DOB

      Optional

      Standard

      The date of birth of the user.

      Preferred Name

      preferredname

      Optional

      Standard

      The preferred name of the user.

      Public Comment

      publicComment

      Optional

      Standard

      The public comment for the user. Visible to the user.

      Private Comment

      privateComment

      Optional

      Standard

      The private comment for the user. Not visible to the user.

      Login Source

      loginSource

      Optional

      Standard

      The method by which the user logs into the system.

      If a login source is not supplied for a user, it will be set to OPS-COM by default.

      OffenseLocations Table

      For additional information on this table, refer to this wiki article.

      Column Name

      Internal Name

      Requirement

      Type

      Description

      Location Name

      LocationName

      Unique ID

      • Required

      Standard

      The name of the location being imported. This value identifies the location as a unique record and is required to import a record.

      Writer Visible

      WriterVisible

      Optional

      Standard

      Whether the writer of a violation of a ticket made in the location is visible to the user.

      GIS Number

      GisNo

      Optional

      Standard

      The GIS number is a geographic location code and is only used by certain clients. Associated with GIS maps (https://www.gismaps.org/).

      Vehicle Table

      Column Name

      Internal Name

      Requirement

      Type

      Description

      Licence Plate

      Plate

      Unique ID

      • Required

      Standard

      The license plate number of the vehicle.

      This value identifies the vehicle as a unique record and is required to import a record.

      Vehicle Year

      Year

      Optional

      Standard

      The year of the vehicle.

      Active Vehicle

      active

      Optional

      Standard

      Indicates whether the vehicle is active or not.

      If not supplied, vehicles will be set to active by default.

      Plate Type Name

      PlateTypeID

      Optional

      Foreign Key

      • VehiclePlateType Table

      The plate type of the vehicle. Attaches to the VehiclePlateType table.

       

      The values supplied by the user in the uploaded file are expected to be values from the TypeName column of the VehiclePlateType table, as these are the values that will be matched against.

       

      The values in the uploaded file must be an exact match to the values in the TypeName column, matching the capitalization, spelling, and spacing exactly, or else it won’t be counted as a match.

       

      The TypeID from the VehiclePlateType table matching the name will inserted into the record in the base table. The value will be left blank in the imported record if no matches are found.

      Province/

      State

      ProvID

      Optional

      Foreign Key

      • Provinces Table

      The province or state of the user. Attaches to the Provinces table.

       

      The values supplied by the user in the uploaded file are expected to be values from the ProvName column of the Provinces table, as these are the values that will be matched against. These are the long names of the province and not the abbreviation; as in, Ontario and not ON.

       

      The values in the uploaded file must be an exact match to the values in the ProvName column, matching the capitalization, spelling, and spacing exactly, or else it won’t be counted as a match.

       

      The ProvID from the Provinces table matching the name will inserted into the record in the base table. The value will be left blank in the imported record if no matches are found.

      Vehicle Make Name

      MakeID

      Optional

      Foreign Key

      • VehicleMake Table

      The make of the vehicle. Attaches to the VehicleMake table.

       

      The values supplied by the user in the uploaded file are expected to be values from the MakeName column of the VehicleMake table, as these are the values that will be matched against.

       

      The values in the uploaded file must be an exact match to the values in the MakeName column, matching the capitalization, spelling, and spacing exactly, or else it won’t be counted as a match.

       

      The MakeID from the VehicleMake table matching the name will inserted into the record in the base table. The value will be left blank in the imported record if no matches are found.

      Vehicle Type Name

      TypeID

      Optional

      Foreign Key

      • VehicleType Table

      The type of the vehicle. Attaches to the VehicleType table.

       

      The values supplied by the user in the uploaded file are expected to be values from the TypeName column of the VehicleType table, as these are the values that will be matched against.

       

      The values in the uploaded file must be an exact match to the values in the TypeName column, matching the capitalization, spelling, and spacing exactly, or else it won’t be counted as a match.

       

      The TypeID from the VehicleType table matching the name will inserted into the record in the base table.

       

      The value will be left blank in the imported record if no matches are found.

      Vehicle Colour Name

      ColourID

      Optional

      Foreign Key

      • VehicleColours Table

      The colour of the vehicle. Attaches to the VehicleColours table.

       

      The values supplied by the user in the uploaded file are expected to be values from the ColourName column of the VehicleColours table, as these are the values that will be matched against.

       

      The values in the uploaded file must be an exact match to the values in the ColourName column, matching the capitalization, spelling, and spacing exactly, or else it won’t be counted as a match.

       

      The ColourID from the VehicleColours table matching the name will inserted into the record in the base table. The value will be left blank in the imported record if no matches are found.

      VIN Number

      vin

      Optional

      Standard

      The Vehicle Identification Number (VIN) of the vehicle.

      Permits Table

      Column Name

      Internal Name

      Requirement

      Type

      Description

      Permit Number

      PermitNo

      Unique ID

      • Required

      Standard

      This field is the first primary identifier. Both it and LotNameID must be provided to create a new permit

      This value identifies the permit as a unique record and is required to import a record.

      Lot Name (Long)

      LotNameID

      Unique ID

      • Required

      Foreign Key

      • LotNames Table

      The long name of the lot associated with the permit. Attaches to the LotNames table.

       

      This field is the second primary identifier. Both it and PermitNo must be provided to create a new permit.

      This value identifies the permit as a unique record and is required to import a record.

       

      The values supplied by the user in the uploaded file are expected to be values from the LotName column of the LotNames table, as these are the values that will be matched against. These are the long form version of the lot name, and not the lot short name.

       

      The values in the uploaded file must be an exact match to the values in the LotName column, matching the capitalization, spelling, and spacing exactly, or else it won’t be counted as a match.

       

      The LotNameID from the LotNames table matching the name will inserted into the record in the base table. The value will be left blank in the imported record if no matches are found.

      Visible

      visible

      Optional

      Standard

      Indicates whether the permit is visible or not.

      Permit Status

      status

      Optional

      Standard

      The status of the permit.

      Permit State

      StateID

      Optional

      Foreign Key

      • PermitState Table

      The state of the permit.

      Violations Table

      Column Name

      Internal Name

      Requirement

      Type

      Description

      Ticket Number

      Ticket

      Unique ID

      • Required

      Standard

      The unique identifier for the violation.

       

      This value identifies the violation as a unique record and is required to import a record.

      Licence Plate

      VehicleID

      Recommended

      Foreign Key

      • Vehicle Table

      The license plate number of the associated vehicle. Attaches to the Vehicle table.

       

      The values supplied by the user in the uploaded file are expected to be values from the Plate column of the Vehicle table, as these are the values that will be matched against.

       

      The values in the uploaded file must be an exact match to the values in the Plate column, matching the capitalization, spelling, and spacing exactly, or else it won’t be counted as a match.

       

      The VehicleID from the Vehicle table matching the name will inserted into the record in the base table. The value will be left blank in the imported record if no matches are found.

      Ticket Type Name

      TicketType

      Recommended

      Foreign Key

      • TicketCategory Table

      The type of the ticket. Attaches to the TicketCategory table.

       

      The values supplied by the user in the uploaded file are expected to be values from the TicketTypeName column of the TicketCategory table, as these are the values that will be matched against.

       

      The values in the uploaded file must be an exact match to the values in the TicketTypeName column, matching the capitalization, spelling, and spacing exactly, or else it won’t be counted as a match.

       

      The TicketTypeID from the TicketCategory table matching the name will inserted into the record in the base table. The value will be left blank in the imported record if no matches are found.

      Fine Amount

      Fine

      Recommended

      Standard

      The amount of fine associated with the ticket.

      Towing Amount

      Towing

      Optional

      Standard

      The amount of towing charges associated with the ticket.

      Tax Amount

      taxAmount

      Optional

      Standard

      The amount of tax associated with the ticket.

      Issued Date

      Issued

      Recommended

      Standard

      The date the ticket was issued.

      Due Date

      Due

      Recommended

      Standard

      The due date for payment of the ticket.

      Ticket Writer

      Writer

      Optional

      Standard

      The admin who wrote the ticket.

      Violation Location Name

      LocationID

      Recommended

      Foreign Key

      • OffenceLocations Table

      The name of the location where the violation occurred. Attaches to the OffenceLocations table.

       

      The values supplied by the user in the uploaded file are expected to be values from the LocationName column of the OffenceLocations table, as these are the values that will be matched against.

       

      The values in the uploaded file must be an exact match to the values in the LocationName column, matching the capitalization, spelling, and spacing exactly, or else it won’t be counted as a match.

       

      The LocationID from the OffenceLocations table matching the name will inserted into the record in the base table. The value will be left blank in the imported record if no matches are found.


      Best Practices & Considerations

      Create or Refresh a Preview Space

      Preview Spaces in OPS-COM provide clients and support staff with a secure, isolated testing environment that mirrors your live production system's data. These spaces are invaluable for testing new features, staging changes, or conducting training without impacting your operational system, ensuring a safe sandbox for development and learning.

      Setup & Configuration

      Preview spaces are typically created on demand. Your production/live OPS-COM system is used to either create a new preview space or refresh an existing one with current or historical data.

      Creating or Refreshing a Preview Space
      1. Click Tools, then Database to Preview.

      From this page, you have two options for refreshing your preview database:

      It may take a few minutes to refresh the database. Generally, a database is refreshed in 1-2 minutes, but it can take up to 15 minutes depending on the size of your database. A message will be displayed along the top of the screen notifying you when the database refresh is complete.

      Once the preview database has been refreshed, your preview system will automatically be created or updated. You can access the preview system by adding ".preview" before "ops-com.com" in your browser's address bar. For example, if your production space is https://tomahawku.ops-com.com, your preview space will be https://tomahawku.preview.ops-com.com.


      Using this Feature

      Accessing Your Preview Space

      As an OPS-COM client, you can access your preview space directly by simply adding the ".preview." suffix to your subdomain name. For instance, if your production site is located at https://yourorganization.ops-com.com, your preview space can be found at https://yourorganization.preview.ops-com.com.

      Preview Space Banner

      To clearly distinguish a preview space from a live production system, all preview spaces are denoted with an amber warning banner displayed prominently at the top of the page.

      Locking and Unlocking Database Reset Option

      You can now lock and unlock preview and development OPS-COM databases to prevent them from being reset or refreshed accidentally.

      1. On your preview site, click Tools, then Reset Database.
      2. Toggle the lock/unlock setting as needed.
        • You will be prompted to provide a reason for locking or unlocking the database.
        • A history of the previous 10 lock/unlock actions will be displayed below for your reference.

      This feature allows you to ensure that if you are actively working on a preview/development system and do NOT wish for your changes to be reset or lost, you can place a lock. This lock notifies others attempting to refresh the database that a reset is not desired.


      Best Practices & Considerations

      Data Maintenance Articles

      Data maintenance is crucial for ensuring the accuracy, reliability, and optimal performance of any system.

      Regular data maintenance helps to:

      The following articles all pertain to Data Maintenance Activities: