**Edit a Violation**
Administrators can make changes to basic information and deal with appeals for this Violation however once a user pays for the violation the comments are locked and admins must use the **Violation Notes** for further comments. Simply click the **Ticket has not been appealed. Show appeals form** text to get the appeal information.
- **Tomahawk Options → Third Party Simulators**
https://ontariocourtforms.on.ca/en/provincial-offences-act-forms/
The provincial forms are:
Case Court: starts at character 3 - a 4 digit number (Parry Sound is 3060, Perth's is 1860). This is repeated starting at character 57 and again at character 186.
Case Jurisdiction: starts at character 7 - a 3 digit number (Parry Sound is 658, Perth's is 073). This is repeated starting at character 61 and again at character 190.
The Agency Code: 3 alphanumeric characters followed by 3 numbers (Parry Sound is BYL390, Perth's is BYL658).
Disbursement Code: 1 alphanumeric character followed by 3 numbers (Parry Sound is M525, Perth's is M658).
To set these codes up within the site, go to System Settings and select the Collections Component.
Enter the values in the designated fields, and then click on save settings.
For municipalities using the extra-detailed version of the notice letter where one notice is sent out for each violation rather than in bulk, the "Include All Unpaid Violations" setting must be disabled.
- **Case Court:** starts at character 3 - a 4 digit number (Parry Sound is 3060, Perth's is 1860). This is repeated starting at character 57 and again at character 186.
- **Case Jurisdiction:** starts at character 7 - a 3 digit number (Parry Sound is 658, Perth's is 073). This is repeated starting at character 61 and again at character 190.
- **The Agency Code:** 3 alphanumeric characters followed by 3 numbers (Parry Sound is BYL390, Perth's is BYL658).
- **Disbursement Code:** 1 alphanumeric character followed by 3 numbers (Parry Sound is M525, Perth's is M658).
https://ontariocourtforms.on.ca/en/provincial-offences-act-forms/
The provincial forms are:
Case Court: starts at character 3 - a 4 digit number (Parry Sound is 3060, Perth's is 1860). This is repeated starting at character 57 and again at character 186.
Case Jurisdiction: starts at character 7 - a 3 digit number (Parry Sound is 658, Perth's is 073). This is repeated starting at character 61 and again at character 190.
The Agency Code: 3 alphanumeric characters followed by 3 numbers (Parry Sound is BYL390, Perth's is BYL658).
Disbursement Code: 1 alphanumeric character followed by 3 numbers (Parry Sound is M525, Perth's is M658).
To set these codes up within the site, go to System Settings and select the Collections Component.
Enter the values in the designated fields, and then click on save settings.
For municipalities using the extra-detailed version of the notice letter where one notice is sent out for each violation rather than in bulk, the "Include All Unpaid Violations" setting must be disabled.
https://ontariocourtforms.on.ca/en/provincial-offences-act-forms/
The provincial forms are:
Case Court: starts at character 3 - a 4 digit number (Parry Sound is 3060, Perth's is 1860). This is repeated starting at character 57 and again at character 186.
Case Jurisdiction: starts at character 7 - a 3 digit number (Parry Sound is 658, Perth's is 073). This is repeated starting at character 61 and again at character 190.
The Agency Code: 3 alphanumeric characters followed by 3 numbers (Parry Sound is BYL390, Perth's is BYL658).
Disbursement Code: 1 alphanumeric character followed by 3 numbers (Parry Sound is M525, Perth's is M658).
To set these codes up within the site, go to System Settings and select the Collections Component.
Enter the values in the designated fields, and then click on save settings.
For municipalities using the extra-detailed version of the notice letter where one notice is sent out for each violation rather than in bulk, the "Include All Unpaid Violations" setting must be disabled.
# List Overdue Report
## Accessing the Report
From the **Violations** menu hover over **Reports** and click the **List Overdue** menu item to access the **Overdue Violation Payments** report.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Os9image.png)
The **Overdue Violation Payments** screen is displayed.
Enter your search criteria and click **List Overdue Records.** In this case we are looking at violations between **May1st 2020** and **February 8th 2021** The report will appear at the bottom of the screen with the violation number, details, amount, and offender details.
[](https://opscom.wiki/uploads/images/gallery/2024-06/P6Rimage.png)
## Emailing Users
You can click on the user email address to email users directly related to their overdue violations.
You can also select **Email Listed Users** at the bottom of the report to send an email to **all users** on the report.
## Generating an Excel Report
Click **Generate Excel Report** to create an excel document for your records or further manipulation.
# Violations by Pay Type by Month Report
## Running the Report
To begin go to the **Violations** menu and hover over **Reports**. Select **List By Type By Month** Report.
[](https://opscom.wiki/uploads/images/gallery/2024-06/KiCimage.png)
The **Violations by Pay Type by Month** screen opens.
[](https://opscom.wiki/uploads/images/gallery/2024-06/TIfimage.png)
Select the month you wish to report on. In our example we will look at **November of 2020**. Click on **Retrieve** to continue.
[](https://opscom.wiki/uploads/images/gallery/2024-06/lOsimage.png)
The resulting report will display onscreen.
[](https://opscom.wiki/uploads/images/gallery/2024-06/06Ximage.png)
The report may also be exported as an excel file.
[](https://opscom.wiki/uploads/images/gallery/2024-06/jcfimage.png)
# Hiding Zero Dollar Violations
1. Hover over '**System Config**' and click '**System Settings**'
[](https://opscom.wiki/uploads/images/gallery/2024-06/Yg9image.png)
2. Click '**Violations**' to open the Violations settings
[](https://opscom.wiki/uploads/images/gallery/2024-06/zcjimage.png)
3. Enable the '**Hide Zero Dollar Fines**' checkbox to hide zero dollar violations.
[](https://opscom.wiki/uploads/images/gallery/2024-06/B8Fimage.png)
# Cancelling a Violation
## How to cancel a violation
Hover over **Violations**, select **Search**
[](https://opscom.wiki/uploads/images/gallery/2024-06/qyvimage.png)
Enter the violation being cancelled into the **Search Text** field, then select **Search using only text**. In this case the violation being cancelled is **TT-10063.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/ekQimage.png)
Click on the **Ticket Number** of the violation being cancelled
[](https://opscom.wiki/uploads/images/gallery/2024-06/FHpimage.png)
Click on the **Edit** button
[](https://opscom.wiki/uploads/images/gallery/2024-06/dGAimage.png)
Select **Cancelled** in **Fine Action** field and enter the reason for the cancellation into the **Appeal Admin Comment** field
[](https://opscom.wiki/uploads/images/gallery/2024-06/f8Himage.png)
Click on **Update this Violation**
[](https://opscom.wiki/uploads/images/gallery/2024-06/PLoimage.png)
The **Violation Information Updated** page displays, showing the violation has been updated
[](https://opscom.wiki/uploads/images/gallery/2024-06/xmDimage.png)
# Spoiling a Violation
## How to Spoil a Violation
To spoil a violation start by searching for the violation through the **Quick Search** or **Violation Search** tool.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Ajjimage.png)
Drill into the payment details on the **Violation Information** page
[](https://opscom.wiki/uploads/images/gallery/2024-06/uh1image.png)
Select **Edit** at the top right of the violation and change the **Spoiled** status from **Valid - not spoiled** to **Spoiled**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Vi3image.png)
Submit the changed violation details and your ticket will now be marked as **Spoiled** the next time you go to search for it.
# Violations From Static Cameras / Mailout Violations
Violations/Infractions can be created from a report that looks at chalk records. Before this can work, ensure that OPS-COM has set your static cameras up with the necessary settings to report on the lot group and gps location of the camera. Some cameras report on more vehicle information than others. This can be helpful in the report later.
The next setup would be to map your Lot Groups to the appropriate Offence Location:
[](https://opscom.wiki/uploads/images/gallery/2024-07/dgjimage.png)
With this set up, logs will be available as they come in:
[](https://opscom.wiki/uploads/images/gallery/2024-07/jztimage.png)
[](https://opscom.wiki/uploads/images/gallery/2024-07/dbSimage.png)
Report type will contain all available filters that we support at the time.
- No Permit & Over Lot Time - This option will only list vehicles where they have no permits and the duration exceeds the lot group's free parking time.
The following is an explanation of each field.
[](https://opscom.wiki/uploads/images/gallery/2024-07/Pl5image.png)
Vehicles can appear in one of three formats. No existing vehicle record, a single vehicle record, or multiple vehicle records. They will change the violation creation screen as follows:
[](https://opscom.wiki/uploads/images/gallery/2024-07/1xuimage.png)
Clicking a row will display the violation entry form.
The entry and exit cameras will show the chalk image associated to this entry:
[](https://opscom.wiki/uploads/images/gallery/2024-07/doMimage.png)
Once the details are entered, the chalk record will disappear from the list and the violation can be found by searching for it:
[](https://opscom.wiki/uploads/images/gallery/2024-07/4MLimage.png)
# IncidentAdmin
# IncidentAdmin Workflow
Incidents can be reported in several ways:
- Campus Security may observe violations as they occur
- Individuals may contact campus security to report incidents
- Staff may report incidents on behalf of fellow staff or students
- Requests to investigate may come from campus administration
- Incidents may be caught on surveillance cameras etc.
Initiating the entry of incidents into the system can be done in a couple of ways.
- Dispatch Logs
- Incident Entry
These items can be generated in any order.
Once an incident is recorded in the system **Security Administrators** can track the progress of any resulting investigation or follow-up events related to the incident.
Tasks can be created and assigned to officers, primary investigators, case workers and security administration through the incidents tool.
Investigators can track their progress from initial discovery through to resolution.
Steps taken in the process as well as the outcome for individuals involved can be recorded, and in turn reported on through **IncidentAdmin**.
The following subjects are the main highlights in the workflow process in **IncidentAdmin**.
1. Searching, viewing and editing incident records
2. Working with related occurrences and violations
3. Viewing "**My Tasks**" within **IncidentAdmin**
4. Generating reports from records stored in **IncidentAdmin**
## A Word About Reports
There are a number of reports that can be generated in **IncidentAdmin.**
1. **Recent Incidents Summary Report -** Lists the last 30 days of incident records.
2. **Search Repeat Offenders -** Report on individuals involved in multiple incidents
3. **Weekly Stat Report -** Reports on the number of all types of incidents that happened during a specified time span
4. **Calls for Service**
5. **Summary Search -** Allows administrators to get a summary of all incidents that have been recorded within a specified time frame.
6. **Summary Report -** Allows administrators to produce a list in a spreadsheet format of incident summaries based on a date range**.**
7. **Report by Category** - Search for incidents under defined categories within a specific time frame.
8. **Sub Location Report** - Search incidents filtered by sub location.
# Configuring Incidents
Here is the list of items that would have to be set up in the system prior to using the incident module.
[](https://opscom.wiki/uploads/images/gallery/2024-06/cNbimage.png)
1. **Categories**: Incident Categories are a listings of the types of Incidents that occur. Each **Category** can have multiple **sub categories**.
Here's an example of a category and it's sub-category items. In this case the category is **Break and Enter**. The subcategories appear on the right.
[](https://opscom.wiki/uploads/images/gallery/2024-06/pbPimage.png)
2. **Flags**: Incidents may be **flagged** for information, and/or importance.
An example would be: "Was violence involved?" or "Were there weapons involved?"
For more information Refer to this Article.
3. **Ethnicity**: Within incident reporting you have the ability to enter a description of people associated with the incident, whether it be the victim, a related person, the suspect or person who committed the incident.
Ethnicity is one of the descriptors typically used in identifying a person related to an incident.
4. **Relations**: In this area you can define the relationship/involvement the individual has with the particular incident.
Examples could be: Complainant, Witness, Victim etc.
5. **Ext. User Profile Options**: These items are **extended values** used in describing an individual within incident reporting.
Examples could be: Physical descriptors such as hair colour, hair style, Body Build Type, Clothing Style etc.
(**Note:** These descriptions will only be seen in the incidents module and not in the user's profile.)
6. **Missing Property Types**: An incident may include theft or damage to property. This item allows you to create **pick lists** that can describe property involved in an incident.
Examples could be: Vehicles, personal property such as jewelry, computers, electronic devices, money, etc.
7. **Cameras**: In this section admins can configure input from surveillance cameras that may have captured the incident.
# Search Incidents
1\. Hover over the **Incidents** icon and select **Search Incidents**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/RWtimage.png)
2\. This will take you to the **Search Incidents** screen. Here you can do an Incident Search, People Search or a Vehicle Search.
Fill in the information you want to search by and select the "**Search**" button at the bottom of that particular section.
## Search Criteria
**Occurrence #:** When an incident is created in the system a unique ID number is designated to the incident that can be referenced in this search module.
**Police Occurrence #:** If you partner with a police force they may have a reference number that can be assigned and searched.
**Reported by (Officer):** This search filter will narrow your search to incidents reported by specific officers selected from a drop down pick list.
**Reported Dates**: Enter the date on which the incident was reported.
**Status:** Select from a drop down pick list incidents that have a status of **Open, Closed,** or **Close Requested**
**Summary:** Enter a short description of the incident in question.
**Between Dates: **Enter a date range in which the incident occurred.
**Location** and **Sub-Location:** Select areas where the incident occurred.
**Room Number:** If the incident occurred in a specific room on campus, enter the room number here.
**Category:** Select the general type of incident being searched from a drop down pick list.
**Sub Category:** Select the specific type of incident in relation to the general type being searched from a drop down pick list. The list changes based on which general category is chosen.
**PON/Summons Issued:** Select whether or not a PON (Provincial Offence Notice) or Summons has been issued.
**Arrest/Apprehension Made:** Select whether or not an arrest or apprehension of an individual was made.
**Violence Involved:** Select whether or not violence was involved in the incident.
**Weapons Involved:** Select whether or not weapons of any kind were involved in the incident.
**Text:** Use this field to enter related key words, descriptions, locations etc. This search field searches both the narrative, and location description.
**Last Updated Between Dates: **Select a date range of when an update to the incident information might have occurred.
**Has Been Read:** Select yes, no or either. This will select incidents that have been previously reviewed or those that have not.
**Case Manager**: Select from a drop down pick list to filter on specific case managers assigned to the incident in question.
**Primary Investigator:** Select from a drop down pick list to filter on specific primary investigator assigned to the incident in question.
**Task Assignments:** Select from a drop down pick list to filter on a specific assignee who has been tasked with investigating the incident in question.
**Requires a Checklist:** Select whether or not the incident has a related checklist.
**Include Checklist Details: **If the item above it checked as yes or either, check this box if you wish to have the checklist details appear in your search results.
[](https://opscom.wiki/uploads/images/gallery/2024-06/lbUimage.png)
**People Search:** In this section you can enter typical details about a specific person to perform an incident search on.
**Vehicle Search:** In this section you can enter typical details about vehicles that are involved in the incident being searched.
[](https://opscom.wiki/uploads/images/gallery/2024-06/K5Vimage.png)
# Incident Entry
1\. Hover over the **Incidents** icon and select **Incident Entry.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/ab7image.png)
2\. This will take you to the **Opened Incidents** page. Here you can select the link for a particular ***Incident Number*** to view the details of that particular incident or you can select the ***Create a*** ***New** **Incident*** **button**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/QnXimage.png)
3\. When you select the link to **Enter New Incidents**, this will take you to STEP 1: Finding individuals and vehicles related to an incident. Select the appropriate link to search by Users, Vehicles or Missing Property.
If the incident is not associated with a particular user, vehicle or missing property, select the "**Enter Specific Incident Details**" button.
[](https://opscom.wiki/uploads/images/gallery/2024-06/TgAimage.png)
4\. Once you find the user that you are looking for, select the "**Add User to Incident"** button at the bottom right.
If there is no user found with the information you are searching, you can select the "**Add a New Individual to the Database**" button at the very bottom, in the center.
This will take you to the STEP 1: Quick Registration Form where you can enter all the details that you have on the individual.
[](https://opscom.wiki/uploads/images/gallery/2024-06/PdSimage.png)
5\. Once the user is selected or added you will be taken to a page where you can identify specifics about the individuals involved in the incident. Fill in all the details that you have. You must fill in the **Relation** field which identifies person's relationship to the incident (e.g. victim, witness, prime suspect, etc.)
Select the "**Save User Details"** button to save the details. Select the "**Search for Additional Individuals**" button to add other individuals involved in the incident. You can also add vehicle details and property details by selecting the appropriate link.
You can also select the **"Enter Specific Incident Details"** button at the bottom right if there are no other details to add related to people, vehicles, and property.
[](https://opscom.wiki/uploads/images/gallery/2024-06/NgJimage.png)
Sample Vehicle Search
[](https://opscom.wiki/uploads/images/gallery/2024-06/V3Rimage.png)
Sample Missing Property Search
[](https://opscom.wiki/uploads/images/gallery/2024-06/sHyimage.png)
6\. Once you select the **"Enter Specific Incident Details"** button you will be taken to STEP 2: Entering Incident Information.
A summary of the people involved, vehicles involved and/or the missing property involved will appear at the top of the page. Next, you will find the **Incident Information** section where you will fill in all information that you have on the incident. (**OPS Number** is an abbreviation for ***Other Police Services Number*** used for tracking the incident. **PON Summons** is an abbreviation for ***Provincial Offences Notice Summons.***)
To attach images, select the **"Choose File"** button beside the line for Attach Image, find and select the file that you want to attach and select the **"Open"** button. This will upload the file and attach it to the incident.
When all information is submitted in the Incident Information section, select **"Save Incident"** at the bottom of the page.
[](https://opscom.wiki/uploads/images/gallery/2024-06/e1eimage.png)
7\. Once the incident has been saved you will be taken to the **"Incidents - Last 30 Days"** summary screen. If you need to edit any details, select the **"View Incident"** link to the right of the incident that you want to reopen.
[](https://opscom.wiki/uploads/images/gallery/2024-06/P2Vimage.png)
# Editing Incidents
1. From the **Incident Information** page, select the '**Edit Incident**' button
[](https://opscom.wiki/uploads/images/gallery/2024-06/XZuimage.png)
2. Enter or change any new information, then select '**Update Incident Details**'
[](https://opscom.wiki/uploads/images/gallery/2024-06/v4Cimage.png)
3. Select '**View Incident**' to return to the **Incident Information** page
[](https://opscom.wiki/uploads/images/gallery/2024-06/fiqimage.png)
4. There are other options listed down the side bar. An explanation for each button is below:
[](https://opscom.wiki/uploads/images/gallery/2024-06/hOXimage.png)
Close Incident - Select this button to toggle the incident between Closed and Open.
Edit Incident - Select this button to toggle between viewing and editing the incident.
Distribute Incident - Select this button to create a distribution report. This locks the incident from being edited.
Email Incident - Select this button to generate an email about the incident.
Download Incident - Select this button to download a PDF copy of the incident. This locks the incident from being further edited.
Toggle Read Status - Select this button to toggle the read status from '**unread**' to '**read**' or '**read**' to '**unread**'
# Incident Reports
- [Recent Incidents Summary Report (Last 30 Days)](https://opscom.wiki/books/for-administrators-staff/page/recent-incidents-summary-report-last-30-days)
- [Incidents Summary Report](https://opscom.wiki/books/for-administrators-staff/page/incidents-summary-report)
- [Incidents Summary Report by Category](https://opscom.wiki/books/for-administrators-staff/page/incidents-summary-report-by-category)
- [Incident Summary Report by Sub-Location](https://opscom.wiki/books/for-administrators-staff/page/incident-summary-report-by-sub-location)
# Recent Incidents Summary Report (Last 30 Days)
1\. Hover over the **Incidents** icon and select **Recent Incidents**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/GNsimage.png)
2\. This will bring up a table of all incidents that have been recorded in the previous 30 days.
You can get the details of an individual incident by selecting the "**View Incidents**" button to the right of the particular incident that you want to review.
You can also sort the table by selecting the column heading to sort by.
[](https://opscom.wiki/uploads/images/gallery/2024-06/iEKimage.png)
Note: The ability to export this report to excel is now a permission that can be given to admins.
[](https://opscom.wiki/uploads/images/gallery/2024-06/3KCimage.png)
# Incidents Summary Report
Hover over the **Incidents** icon, click **Reports** then select **Summary Report.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/0fTimage.png)
This will take you to the **Incident Summary Report** page. Here you can get a summary of all incidents that have been recorded within a specified time frame.
[](https://opscom.wiki/uploads/images/gallery/2024-06/twIimage.png)
Enter the ***start date*** and ***end date*** for the report that you want to create and select the button at the bottom for **"Search Incidents**".
If you wish to include incidents that do not have a summary in the results, uncheck the **Show only Items with Summaries** checkbox.
This will bring up the **Incident Summary Report** at the bottom of the screen. You can export this information to an Excel file by selecting the **"Export to Excel"** button.
You can also get the details of an individual incident by selecting the **"Details"** button to the right of the particular incident that you want to review.
[](https://opscom.wiki/uploads/images/gallery/2024-06/zhQimage.png)
# Incidents Summary Report by Category
1\. Hover over the **Incidents** icon, click **Reports** and select **Report by Category**
[](https://opscom.wiki/uploads/images/gallery/2024-06/Hocimage.png)
2\. This will take you to the **Incidents Summary by Category** screen. Select the selection boxes beside the categories that you want to include in your report, select the dates that you want the report to include, select location and/or select the sub-location. Select the Search Incidents button at the bottom once you have selected all of the criteria that you want to search by. Note, you do not need to select an option in all sections, only the ones that you specifically want information on.
[](https://opscom.wiki/uploads/images/gallery/2024-06/iPeimage.png)
3.This will bring up a table at the bottom of the page that provides an overview of the incidents that have occurred in each category based off of your search criteria (sample below). From here you can select any of the links listed as a sub-category to get a **Sub-Category Report.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/lE4image.png)
4\. In the **Sub-Category Report,** administrators can sort the table by selecting the column headings. Administrators can select the Details link beside a particular incident to view/edit details within that incident.
[](https://opscom.wiki/uploads/images/gallery/2024-06/R9Himage.png)
# Incident Summary Report by Sub-Location
1\. Hover over the **Incidents icon**, click **Reports** and select **Sub-Location Report**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/vREimage.png)
2\. This will bring up the **Search Incidents** page. Select the specific dates that they want to search as well as the specific sub-location that they want to search. Select the **"Search"** button when all criteria have been entered.
[](https://opscom.wiki/uploads/images/gallery/2024-06/drHimage.png)
3\. This will bring up a table at the top of the page that provides an overview of the incidents that have occurred in each sub-location based on the time frame specified (sample below). Administrators can also select the **Details link** to the right of a particular incident to view/edit that particular incident.
[](https://opscom.wiki/uploads/images/gallery/2024-06/kevimage.png)
# View Open Incidents
1\. Hover over the **Incidents** icon and select **View Open Incidents.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/NDbimage.png)
2\. This will take administrators to the **Open Incidents Report Page**. Administrators can select the specific ***Incident Number link*** to view/edit that particular incident.
[](https://opscom.wiki/uploads/images/gallery/2024-06/SToimage.png)
# Dispatch Logs
## Reviewing Dispatch Logs
Hover over the **Incidents** icon, **Dispatch**, and select **Dispatch Logs**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/zl2image.png)
This will bring up the **View/Edit Dispatch Log Records** page. Here administrators/dispatchers can view all open logs that still need to be followed-up on.
[](https://opscom.wiki/uploads/images/gallery/2024-06/UzYimage.png)
## Printing a Dispatch Log
To print the currently selected dispatch logs, select the appropriate source in the list of current dispatch logs followed by **Print Selected** to get a printed list of these logs.
[](https://opscom.wiki/uploads/images/gallery/2024-06/DwJimage.png)
## Creating new Dispatch Log Records
To create a new log record select one of the options from the **Create New Log Record**
[](https://opscom.wiki/uploads/images/gallery/2024-06/SuDimage.png)
Once the source contact for the new log has been selected, this will bring up the **Add New Log Record** screen.
[](https://opscom.wiki/uploads/images/gallery/2024-06/qg1image.png)
Select the appropriate **Category** from the drop-down menu and type in any details that need to go with the log in the ***Note section.*** Select the **Add New** button at the bottom of the screen to save the information. Once the information has been saved, the log will show at the top of the listing of Dispatch Log Records.
## Adding Additional Log Notes
If dispatchers want to add a separate log that is attached to the first log, select the **Add link** in the **Add column**. This will bring up an **Add Log Note** screen where dispatchers can include the source of the information, the category and any notes that need to be included. To save the log select the **Add** button at the bottom. To save the log and to also close the log, if it is completed, select the **Add & Close** button at the bottom.
[](https://opscom.wiki/uploads/images/gallery/2024-06/8CXimage.png)
If dispatchers want to assign an admin user to act on the log or if they want to attach an incident report, select the **Assign** link at the far right of the log. When an assignment is made, the incident number will appear in the listing of Dispatch Log Records. This link can be selected to gain access to view/edit the incident report.
## Viewing Additional Notes / Rolled-Up Alerts
We can view all of the available log records associated with the dispatch log In the **View/Edit Dispatch Log Records**, by selecting the **+** symbol to the left of the log.
[](https://opscom.wiki/uploads/images/gallery/2024-06/a3Fimage.png)
Dispatchers can add additional information to the initial log by selecting the link for the dispatch number. To close a log once it has been dealt with, select the **"C"** in the Status column to change the status to closed.
## Bulk Closing of Dispatch Logs
It is also possible to close multiple Dispatch Logs in bulk. Select the logs you wish to close by selecting the checkbox associated with the log in question. Once you have selected all the log records you wish to close, click on Close Selected.
[](https://opscom.wiki/uploads/images/gallery/2024-06/RcjxFhimage.png)
# Related Occurrences
1. Click the **'Incidents Menu'** select '**Search Incidents**'.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Rt6image.png)
2. In the Occurrence# field enter the **Incident Number** you wish to relate to another.
[](https://opscom.wiki/uploads/images/gallery/2024-06/PoDimage.png)
3. The **Incident Information** screen displays. *Note: the tabs along the top of the form,* they provide a quick summary of information.
Under the **'Related'** tab we currently see the numeral 0 indicating that there are no incidents related at this time. When you select the **Related** tab, the button to **Track Related Occurrences** will appear.
[](https://opscom.wiki/uploads/images/gallery/2024-06/0QAimage.png)
4. Click the **'Track Related Occurrences**' button to display the **'Track Related Occurrences'** screen. The buttons across the top allow different options to search for. The '**Add Related Occurrences**' form is now available, by selecting **New Related List**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/GOYimage.png)
5. The first step is to **Name** and **Create** the list. In our example, we are naming the list "***Suspicious Activity March 20***". In the notes field, you can add a description of what the purpose of the list is. Click '**Save**' to save the list name and information. The screen will refresh with a **Search** box now showing at the bottom.
[](https://opscom.wiki/uploads/images/gallery/2024-06/foFimage.png)
6. Enter the **Current Incident Number** you are working with. For this example we are using16-0004. Click **'Search.'**
[](https://opscom.wiki/uploads/images/gallery/2024-06/iaaimage.png)
7. Click '**Add**' to add this incident to the list entitled ***'Suspicious Activity March 20th'***.
8. Repeat the search process by entering the *Incident number* you would like to relate to the first incident.
For example, Incident 16-0004 as 16-0006 and click **'Search'**. Add this incident to the list. The resulting screen will look like this: Note both 16-0004 and 16-0005 are listed.
[](https://opscom.wiki/uploads/images/gallery/2024-06/qREimage.png)
9. To see the result of this process, search once again for the original Incident 16-0004 from the **Search Incidents** menu. Note the change in the Related Tab now indicates 1 related occurrence.
[](https://opscom.wiki/uploads/images/gallery/2024-06/ptRimage.png)
10. Click on **Related** to see the **Related Incident Information**. Note: the related incident is now listed. This information will show up on the incident information for both incidents in question.
[](https://opscom.wiki/uploads/images/gallery/2024-06/dEQimage.png)
# View Cameras
1. To view the cameras, go to Incidents icon, and click on View Camera
[](https://opscom.wiki/uploads/images/gallery/2024-06/04timage.png)
2\. Next, you will see a page that has a button that says "**Launch Cameras**". Click on it
[](https://opscom.wiki/uploads/images/gallery/2024-06/as1image.png)
3. A new window will open so you can see the Cameras
[](https://opscom.wiki/uploads/images/gallery/2024-06/HY3image.png)
# My Incident Tasks
## Accessing your Tasks
To access your tasks, click on **Incidents**, then click **My Tasks**
[](https://opscom.wiki/uploads/images/gallery/2024-06/Epbimage.png)
To view tasks, click on the *blue drop-down menu*, select your **name**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/AsKimage.png)
Click on the **Incident Number** to display the **Incident information** page for more information.
[](https://opscom.wiki/uploads/images/gallery/2024-06/lhLimage.png)
# Incident Checklist
### Accessing the Checklist
To access the checklist go into any incident and click on the **Checklist tab**. To access the form click on **Open Checklist**.
The checklist form will open.
[](https://opscom.wiki/uploads/images/gallery/2024-06/xTTimage.png)
#
Checklist Fields Defined
**CCTV Reviewed:**
Indicate if the closed-circuit television cameras were reviewed. (Yes/No/Not Required) State the reason for what was selected or additional details. E.g. What was found in the footage? Why was the footage not reviewed?
**Other Resources Reviewed:**
Indicate if other resources were reviewed as a part of the incident. (Yes/No/Not Required) State all resources used or additional details. E.g. Social media, Canada 411 or OPS-COM.
**Witness(es) Interviewed:**
Indicate if witnesses were interviewed as a part of the incident. (Yes/No/Not Required) State all witnesses, and their contribution to the incident resolution or additional details. E.g. Mike Lawson - Saw the incident.
**Suspect(s) / Person(s) of Interest Interviewed:**
Indicate if the suspects were interviewed as a part of the incident. (Yes/No/Not Required) State all suspects involved, and their involvement with the incident or additional details. E.g. Sandra Morra - Admitted fault after evidence had been found.
**Statements Obtained:**
Indicate if statements were collected as a part of the incident. (Yes/No/Not Required) State all the statements provided in relation to the incident or additional details. E.g. No other people at the scene to make a statement.
**Other Evidence Collected:**
Indicate if other physical or virtual evidence was reviewed as a part of the incident. (Yes/No/Not Required) State all the evidence collected, where it is stored and important information about it, or additional details. E.g. Beer bottle - given to the police - had fingerprints of the suspect.
**Safe Plan and Community Resources Discussed with Complainant:**
Indicate if a safe plan and community resources were discussed with the complainant. (Yes/No/Not Required) State what specifically was discussed, or additional details. E.g. Complainant was informed that the police were updated on the case and that the complainant's information was given to them.
**Other Departments / Agencies Consulted or Notified:**
Indicate if other departments were notified as a part of the incident. (Yes/No/Not Required) State all departments notified and the reason why, or additional details. E.g. Housing - Students need to be moved to separate buildings.
**Community Notified:**
Indicate if the community was notified as a part of the incident. (Yes/No/Not Required) State how and why the community was notified, or additional details. E.g. Flyers put up on west residence building to inform other students of the case, due to its nature and school policy.
**Security / CPTED Audit Conducted:**
Indicate if security and/or CPTED (Crime Prevention Through Environmental Design) audit was conducted as a part of the incident. (Yes/No/Not Required) State what was audited, any problems found, and steps taken to resolve them, or additional details. E.g. Audit of residence building security shows blind spots in lobby cameras by front desks. Additional cameras were added.
**Recommendations Made to Prevent a Re-occurrence:**
Indicate if recommendations to prevent future incidents were made. (Yes/No/Not Required) State all recommendations, or additional details. E.g. An employee will be posted at the front desk of the residence building at all times, to ensure the safety of all in the main lobby.
**Complainant Notified of Outcome:**
Indicate if the complainant was notified of the outcome. (Yes/No/Not Required) State what the complainant was told, or additional details. E.g. Bob Gant was informed that there would be an employee posted at the front desk, who could help prevent future incidents.
**Documentation Updated & Filed:**
Indicate if documentation was updated and filed for the incident. (Yes/No/Not Required) State what documentation was updated, or additional details. E.g Security audit has been saved to the security network drive and camera layout has been updated for all buildings.
**Status at time of Closing:**
Indicate the status of the incident at the time the case is closed. (Solved/Unsolved/Unfounded)
**Reason For Report Being Closed:**
Indicate the reasons for the report being closed. (Drop down box) E.g Reason beyond the control of service
**Closing Comments:**
Indicate any final comments or details of the case. E.g. Case has been closed, recommendations have been implemented for security and staffing. This type of incident should no longer be possible on the lobby floors of all residence buildings across campus.
# Filling out the Incident Form (WIP)
Here is a sample of what the Incident report looks like. Basic information describing what occurred can be registered here in the overview. This includes what one might consider the essential information about the incident.
- Description
- Status
- Time
- Place
- Any related information or events
[](https://opscom.wiki/uploads/images/gallery/2024-06/DQaimage.png)
The incident report also allows the admin to record details:
- Dispatch Logs
- People Involved
- Vehicles Involved
- Missing Property if any
- Tasks to be completed
- Checklist (A Custom form that can be generated)
- Related issues or incidents
- External (Follow-Up Items)
- Related Violations
[](https://opscom.wiki/uploads/images/gallery/2024-06/dslimage.png)
# Viewing an Incident
You can get to the view incident screen from multiple areas. Searches, reports, links from other places.
Once there, you can view something similar to this:
[](https://opscom.wiki/uploads/images/gallery/2024-07/view-image1.png)
### Viewing Permissions
To view the page, you must have one of the following permissions:
- View All Incidents
- View Incidents - Self
- AND you must be one of the following:
- The reporter
- Primary Investigator
- Case Manager
- Be on a task group that’s assigned in the tasks
- Be assigned directly to a task.
The edit option is only available if you have one of the following permissions:
- Custom Permission - Open All
- Edit Incidents
- View Incidents - Self
- AND you are the reporting admin
- AND the incident is Open
[](https://opscom.wiki/uploads/images/gallery/2024-07/view-image2.png)
- If the incident is locked and the admin has the permission "incident\_admin" - Incident Administrator, then they can view the lock reason.
- If the admin has the permission: View/Edit Confidential Information, they can see a Confidential Info section near the bottom above files.
### **Dispatch Logs**
Anyone who can view the incident can view the dispatch logs. To add or drop dispatch logs from this incident, the admin must have the permission: “Add/Drop Dispatch Logs.”
Linking dispatch logs can be done from either the dispatch entry screen or from the link Log button:
[](https://opscom.wiki/uploads/images/gallery/2024-07/view-image3.png)
Dropping a log can be done from the Dispatch Logs tab. It will prompt the admin prior to dropping the log:
[](https://opscom.wiki/uploads/images/gallery/2024-07/view-image4.png)
### **Linking People**
[](https://opscom.wiki/uploads/images/gallery/2024-07/view-image5.png)
The show more section will show all the extended details about a user that isn’t on the screen above:
[](https://opscom.wiki/uploads/images/gallery/2024-07/view-image6.png)
### **Linking Other Items**
Linking other items such as vehicles, missing property and violations can also be done from here. There’s less information to show than with users.
Related incidents can be viewed here.
[](https://opscom.wiki/uploads/images/gallery/2024-07/view-image7.png)
Useful for when several incidents are all related in some way. How these are linked and managed are done elsewhere.
### **Checklists**
Some incidents require a checklist to be filled out prior to closing or requesting the incident be closed. The subcategory is what defines this requirement:
[](https://opscom.wiki/uploads/images/gallery/2024-07/image8.png)
To view the checklist, the admin must have one of the following permissions: View All Incidents or Incident Administrator.
When the issue is still open, a warning will appear:
[](https://opscom.wiki/uploads/images/gallery/2024-07/image9.png)
Then they can fill out the details and depending if they have the right permission, close or request the incident be closed:
[](https://opscom.wiki/uploads/images/gallery/2024-07/image10.png)
### **Tasks and assignment**
[](https://opscom.wiki/uploads/images/gallery/2024-07/image11.png)
#### **Case Manager assignment**
To assign an incident to a case manager, the admin editing the report must have the permission “Assign Incident To Case Manager” or they must already be the case manager.
Further to this, to be able to be the case manager, only the admins with the permission “Is Incident Case Manager” or “Is Incident Shift Manager” will be available.
In the above example, Maximillion Smith is not the case manager, nor do they have the assign permission so they can only view who is assigned the case manager role.
#### **Primary Investigator assignment**
Similarly with Primary Investigator, the admin must meet one of the following criteria:
- Permission: Edit Incident Tasks
- Permission: Is Incident Shift Manager
- Permission: Assign Incident To A Different Investigator
- Role: Is the case manager for this incident
- Scenario: No Primary Investigator is selected and they have the permission Assign Incident to An Investigator
Only admins with the permission “Be Assigned Tasks Directly” will be available.
In the above example, Max has the permission Edit Incident Tasks and therefore can change the primary investigator.
#### **Editing Tasks and Comments**
If the admin is:
- Permission: Edit Incident Tasks
- Permission: Is Incident Shift Manager
- Role: Is the primary investigator or case manager
They can add and edit tasks. They can also edit the text in the task.
[](https://opscom.wiki/uploads/images/gallery/2024-07/image12.png)
If the admin does not have the permission, but is assigned to a task either directly or they are part of the task group, they get the reassign option as indicated above.
### **Use of Force Forms**
The use of force form is available for clients in the province of Ontario as this is a Government of Ontario form as indicated below. It requires the setting for Use of Force to be enabled.
On the view incident page, the use of force forms are read only.
[](https://opscom.wiki/uploads/images/gallery/2024-07/L1Jimage.png)
### **Side Buttons & Permissions**
1\. The first button is available and visible if the admin has the Open Incidents permission. It will either be in a state of open or close depending on the current open/close status.
2\. The second button can either be View, Edit, Edit Summary, or hidden. If the admin meets one of the following requirements:
- Permission: Custom Permission - Open All
- Permission: Edit Incidents
- Permission: Edit Incident Summaries
- Permission: View Incidents - Self
- AND you are the reporting admin
What the button does will depend on other states.
- If the admin also has the Incident Admin permission then:
- AND the incident is open, the admin can edit the incident.
- AND the incident is closed, the link will take the admin to the edit summary screen.
- If the admin has the Edit Incident Summaries permission:
- AND the incident is locked, they can edit the summary.
- AND the incident is unlocked, they can edit the incident
- If the incident is open
- They can edit the incident
- If none of the scenarios above match, the admin is not able to edit this incident, nor the summary.
3\. The Distribute & Email buttons are only available to admins with the Incident Admin permission.
4\. The download incident only requires the admin can view the incident at all.
5\. The toggling of read status will switch the state of the read status back and forth between read and unread.
6\. If the admin has the Delete Incident permission, then they can see the next button.
- If the Incident can be deleted, a delete option will appear. This requires that all details on the incident are over seven years old. Any update to any item will render the delete option disabled.
- The message will appear as "Delete Not Avaialble" if the incident or any detail has been created or updated in the last seven years.
# Payments and Transaction Flow
# Payments and Transaction Flow
The flow is a 3 step process, which includes:
1. User/Admin link item to user
2. User makes payment promise
3. Admin processes payment
## Step #1:
A user or an administrator links a permit to the user. At this point, there is no payment link and the item is "**Awaiting Payment**" since the user has not selected a payment method (*made a promise of payment*). As well, items (permits) are not accessible to any other system user. *There is a midnight clearing list which can automatically release permits linked to users that do not have promises for payment.*
## Step #2:
User or admin links a **payment type** (ie. cheque, cash, etc.) This puts the user on the **Unprocessed Payments** list, and that list needs to be checked regularly. This allows a user to mail in a cheque or to stop by the office to make payment. In these cases, a user has "promised" to pay. We suggest that permits be released (Drop Payment) after 2 weeks since that offers users enough time to make payment.
## Step #3:
Once payment is received (cheque is received in the mail, or the user stops by the office to make a payment) the transaction is marked as **processed** and the user is linked to the item. At this point, the item is marked processed and is actually (completely) linked to the user.
# Payment Processing Models
## Using a Gateway
This is being phased out as the method for handling payments.
## Using Hosted Payments
This is the preferred method for handling payments.
[](https://opscom.wiki/uploads/images/gallery/2024-06/G8Yimage.png)
# Types of Reimbursement
## Cancel Transaction
- To cancel a transaction **before** a payment is processed
**When would you cancel a transaction?**
- User decides not to follow through on a promise to pay
**Note:**
- Items in the transaction are released back to the system
- The promise to pay is removed from the user (user no longer owes money)
## Adjustments
- Alter the cost of an item **before** it has been paid for
- Alter the value of a transaction **after** it has been paid for
**When would you apply an adjustment?**
- User was charged too much or too little for an item
- User is being refunded part of a transaction (ie. not longer using item; pro-rated refund)
- Adjustments can be positive or negative
- Can also be considered refunds, but full transaction refunds are a different option
**Note:**
- Items are not released back to the system
## What does a refund look like in the system?
- Item is (or items are) returned **after** it has been paid for
- Transaction needs to be cancelled **after** it has been paid for
**When would you give a refund?**
- User has decided against the purchase
- Transaction is totally incorrect and it is easier to start over
- A refund can be used to **reverse** the transaction
**Note:**
- Transaction items are released back to the system
- If there is more than one item in the transaction, all items will be reimbursed and all items are released back to the system. If only one item needs to be refunded/reimbursed, do an adjustment and release the item separately.
# Adjusting a violation to zero dollars
## Adjusting the fine amount by editing the ticket:
1. To adjust the fine amount on the ticket go to the user's profile and locate the **violation** you wish to reduce.
[](https://opscom.wiki/uploads/images/gallery/2024-06/d1Simage.png)
2. Click on the **ticket number** to access the **Violation Information** detail screen.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Sa9image.png)
3. Click on the **Edit** button in the upper right corner to access the **Edit Violation Information** page.
Halfway down the page you will see the offence listed as well as the amount of the violation.
Edit the dollar value of the fine to **$0.00.**
Click on **Update this Violation** to save your changes.
[](https://opscom.wiki/uploads/images/gallery/2024-06/qu6image.png)
4. The violation will now appear in the user profile as a zero dollar fine.
[](https://opscom.wiki/uploads/images/gallery/2024-06/YUBimage.png)
## Cancelling a fine by changing the ticket to a warning:
An admin can change a ticket to a warning which will result in cancelling the fine amount.
1. To do so **edit** the ticket as described above.
2. Check the box next to the word **Warning** to change the state of the ticket. Click on **Update this Violation** to save your changes.
[](https://opscom.wiki/uploads/images/gallery/2024-06/C9wimage.png)
3. The ticket will appear as follows in the user history. (Captured here from the admin side.)
[](https://opscom.wiki/uploads/images/gallery/2024-06/i5Himage.png)
4. This is how it would appear on the user side:
[](https://opscom.wiki/uploads/images/gallery/2024-06/l6vimage.png)
## Adjusting the fine amount by processing an adjustment:
This scenario is slightly different as adjustments to fines are done **after** the initial fine has been paid for.
1. To begin, go to the user's history and locate the violation you wish to zero out.
In our example we are using Ticket number **TT-10011.**
Click on the **Adjust** link on the left.
[](https://opscom.wiki/uploads/images/gallery/2024-06/7HRimage.png)
2. The **Create Adjustment Record** window will open.
Enter the amount you wish to reduce the fine by. In this case the current fine is $*40.00* (the violation had a fine of $*50.00,* but was paid within the widow where the discount of *$10.00* applied)
It is advisable to enter a comment as to why the fine is being reduced.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Jw2image.png)
3. This method will place an adjustment on the user's account. This is what it will look like in the payments tab.
This adjustment can be applied to a future payment or be processed as a refund.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Uj5image.png)
## Adjusting the fine through the appeals process
A fine can be adjusted or reduced to zero through the appeals process.
# Adjustments
## Making an Adjustment as an Admin
1\. Note that the top right-hand corner will always identify the name of the user file that is being worked in.
[](https://opscom.wiki/uploads/images/gallery/2024-06/ncfimage.png)
2\. For this example, when finished going through the payment process, on the **Transaction Details** screen, select the **Adjust** link.
(Note the process is the same if you select the adjustment link before a transaction is completed.)
This will bring up the **Create Adjustment Record** pop-up screen. Enter in the internal organization **Requisition Code**, change the amount sign to positive if you are charging the user more or change the amount sign to a negative if you are reimbursing the user, enter the dollar amount of the adjustment, enter any comments to be associated with the adjustment and select the **Add Adjustment** button at the bottom of the screen. This will bring you back to the **Payment Details** screen with the adjustment listed below the original transaction. Note, at this point, the adjustment is not processed.
[](https://opscom.wiki/uploads/images/gallery/2024-06/FtFimage.png)
3\. Select the **Not processed** link. This will bring up the **Adjustment Information** pop-up screen where you verify the adjustment details are correct.
[](https://opscom.wiki/uploads/images/gallery/2024-06/QgFimage.png)
4\. If the adjustment details are correct, select the **Process this Adjustment** button at the bottom of the screen. You will notice the **Payment Status** line will change from **Not Processed** to **Submitted** and the date. This completes the adjustment process, altering the dollar amount associated with the item. Note, no items are released back into the inventory system using the adjustment process. If an item needs to be released back into the inventory, this will need to be done separately.
## **Adjusting a Violation Before Payment**
# Cancel Transaction
### Cancelling
On the **Transaction Details** screen you can see the different options available. You can choose to **Cancel & Keep** or **Cancel & Release**.
- **Cancel & Keep** will cancel the transaction but keep the transaction details and reserve the permit so that you can process the payment at another time.
- **Cancel and Release** will cancel the payment and release the permit back into the system
[](https://opscom.wiki/uploads/images/gallery/2024-06/Qtjimage.png)
A pop-up message will ask that you confirm. Click OK to confirm the cancellation of the transaction.
# What does a refund look like in the system?
Locate the user profile for the user you want to refund for. Note: The top right-hand corner will always identify the name of the user that is being worked on. In our example we will refund **Permit #1** at **$395.50** but keep in mind the process is identical for and refund such as Standard Permits, Temporary Permits, Locker rentals, violations etc.
[](https://opscom.wiki/uploads/images/gallery/2024-06/fItimage.png)
From the **History Tab** select **All Records.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/nfQimage.png)
**For Standard permits and Temporary permits:**
Find the permit you want to refund and click on the Processed **date** link.
[](https://opscom.wiki/uploads/images/gallery/2024-06/HLoimage.png)
**For Violations:**
Click on the word **Processed** to access the transaction details.
[](https://opscom.wiki/uploads/images/gallery/2024-06/0QUimage.png)
**For Lockers:**
Click on the Processed **date** link.
[](https://opscom.wiki/uploads/images/gallery/2024-06/5T2image.png)
The **Transaction Details** screen appears. Click on the **Refund** button to begin the refund process.
[](https://opscom.wiki/uploads/images/gallery/2024-06/81qimage.png)
The **Refund Payment Record** window will pop up. Enter the internal organization **Requisition Code** (optional) and the **Refund Amount** (including taxes).
You are required to enter a **comment** in order to proceed.
[](https://opscom.wiki/uploads/images/gallery/2024-06/S4Ximage.png)
Click the **Refund Payment Record** button to continue. A confirmation pop-up will appear. Click **OK** to continue.
**IMPORTANT**: As noted on this screen,
**By using refund for permits and lockers you will be releasing all items associated with this Confirmation Number. Violations however will simply go back to awaiting payment status.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/bjkimage.png)
The **Adjustment Information** pop-up will display showing the refund details. You have the ability to select the type of refund in this window. In our example this will be a **Cash Refund.** Click on **Process This Adjustment** to proceed.
[](https://opscom.wiki/uploads/images/gallery/2024-06/XIhimage.png)
You will return to the **Transaction Detail** window showing the details of the refund. Notice the refund amount of **$-395.50** is listed as an **adjustment**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/4cNimage.png)
To see how this appears in the user's profile on the admin side, go back into the history tab and select **All Records**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/YPaimage.png)
In the user history we see the record of the original purchase as well as; (1) **Released** date and a note indicating the permit is **"Released back to system by refund process"** and (2) **w**e can also see the refund under **Adjustment Records.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/7fsimage.png)
## Refunding to Deal with a NSF Payment
When a payment is made and processed the item is considered paid for. If the payment fails to pass at the bank (NSF) you would need to perform a refund in order to remove the payment from the system.
Why do we refund a NSF Payment?
Refunding for a NSF payment is essentially a bookkeeping issue. For example, if a cheque is returned NSF, the admin must remove the payment from the system in a manner that shows the incoming cheque as a payment and the refund as the removal of the payment that in reality never happened due to the NSF payment.
After you process the refund, the Processed Payment Report for this transaction should show the payment on the report as well as the refund. This is normal as with any refund you will see the incoming payment and then the refund (outgoing) payment. These both need to be there to record the attempt to pay (for lack of a better term) which would show as income. Since the cheque bounced that income has to be removed from the OPS-COM system (system of record).
By doing the refund and processing it you essentially remove that payment from the system and you do so in accordance with typical book keeping entries. Be sure to process the refund with the same payment type (cheque) as the original payment attempt. This will make more sense to anyone doing you accounting. It is also very important to leave good clear notes to document the failed payment and the reason for the refund.
# Collections Module
## Accessing the Collections Module
[](https://opscom.wiki/uploads/images/gallery/2024-06/Serimage.png)
There are several steps leading up to a collection since often notification of a user is all that may be needed to collect on overdue funds.
The collections module is currently tied to the Violations menu, but may in the future work with all modules in the system. Originally the implementation worked around the idea that people parking on campus may be unknown users. By having a collection module (and the MTO lookup functionality) unknown user details can be determined from a vehicle tag (plate, province, etc.). Students and staff users can be dealt with in a different manner but can also be sent to collections. In the case of a student, they can be denied graduation if their account is not paid in full.
## Collection Module Operation
In this particular case, the items related to MTO lookup are based on a data format for the Ministry or Transportation Ontario, but could be adjusted to match requirement in any area.
- ### **Vehicle Lookup Export**
- allows an administrator to export data in a MTO friendly format. This export can be imported to the MTO terminals by MTO staff (or automation) and the result is an MTO Lookup Report.
[](https://opscom.wiki/uploads/images/gallery/2024-06/w3oimage.png)
- ### **Import from Lookup (MTO)**
- allows an administrator to import the unknown user details back into the system and populate address and contact fields.
- ### **Known Report**
- allows an administrator to query and package accounts (as an Excel export) that should be sent to a collection service provider
- Internally it sets the "SentToCollections" flag on the associated violations so that future queries will not duplicate listings
logic around this report is defined as follows:
- **If** (the user has an email and an **overdue notice** *(details below)* that was sent more than 30 days ago)
**OR** (the user does not have an email and the violation is past due date)**Then** include them on the report based on the supplied parameters (user type and days overdue)
[](https://opscom.wiki/uploads/images/gallery/2024-06/g2nimage.png)
- ### **Send to Known & Unknown Report**
- generates a report of the accounts "SentToCollections" based on the date and user type
- the report includes details related to payment where applicable
[](https://opscom.wiki/uploads/images/gallery/2024-06/R95image.png)
## Overdue Notices
See also: Technical Schematic - Step #1
*This document highlights the first steps leading to a collection.*
As part of system automation, overdue notices on violations can be sent out each night. If this is not enabled on your system, please contact Tomahawk Support to have this feature enabled.
Each night the system will create an email list and send overdue notices to any known users that have emails on the system. Essentially the system looks up overdue violations, then looks up vehicles and users associated with those vehicles. From that information it may be able to obtain an email address and formulates a message for delivery to the user.
When the message is sent, the violation field "AutoNotice" is flagged in the database.
In the event a user does not have an email address, or the users are unknown, a report is compiled containing that information and is sent to the system administrator.
An overdue sample message follows:
[](https://opscom.wiki/uploads/images/gallery/2024-06/dEbimage.png)
# Automatic Violation Notice
The Automatic Violation Notice Script sends New and Past Due violation notice emails to ParkAdmin users.
For a Lucid Chart Diagram See: Technical Schematic - Step #1
## OPS-COM Settings to be Confirmed:
There are additional settings that will affect whether or not all unpaid violations will be added to the letter or if the selected violations will only be included when it comes time to create the letter report. These settings are found under **System Settings →** **Collections** → **Include All Unpaid Violations.** As mentioned this will allow you to select a single violation in the list and generate a report for all violations associated with that user. Keep in mind that means it will also remove the associated violations from the pick-list on the Printable Violation Notice Report page even if you only have one of the violations selected.
[](https://opscom.wiki/uploads/images/gallery/2024-06/TT9image.png)
## Notice/Email Summary:
In total there are 4 different types of emails that will be sent once the above is setup:
- **User overdue account notice** (lets normal users know they have a violation(s) past due in OPS-COM).
[](https://opscom.wiki/uploads/images/gallery/2024-06/GF3image.png)
- **User new violation notice** (lets normal users know they have a new violation issued to them the day of, \*note: it seems this will NOT notify older violations once enabled, e.g. violation that is 3 days old vs 1 day old, would only notify the 1 day old user since it's "new").
[](https://opscom.wiki/uploads/images/gallery/2024-06/iwTimage.png)
- **Admin new violation report notice** (emails the OPS-COM administrator telling them how many new violation emails were sent).
[](https://opscom.wiki/uploads/images/gallery/2024-06/IO1image.png)
- **Admin past due violation report notice** (emails the OPS-COM administrator telling them how many users were emailed past due violation emails AND also how many users couldn't be emailed because they didn't have an email address in the system. These users are added to the "letter report", more info below).
[](https://opscom.wiki/uploads/images/gallery/2024-06/vvDimage.png)
| Setting | Details |
|---|---|
| merchant | The merchant code we will be submitting items against. This is the Merchant Code on the clients system. |
| item code | They need to set up an item and give us the code. The item will need to be allowed to change the value. See below for the screen. These codes need to match exactly what the client has configured or the transactions will fail. |
| Setting | Value |
|---|---|
| Sign-out & Complete payment | [https://hostedpayments.parkadmin.com/hook/cashnet/CLIENTS-UNIQUE-HOSTED-ID/?a=r](https://hostedpayments.parkadmin.com/hook/cashnet/CLIENTS-UNIQUE-HOSTED-ID/?a=r) |
| Sign-out & Incomplete | [https://hostedpayments.parkadmin.com/hook/cashnet/CLIENTS-UNIQUE-HOSTED-ID/?a=f](https://hostedpayments.parkadmin.com/hook/cashnet/CLIENTS-UNIQUE-HOSTED-ID/?a=f) |
| Pass information to calling system | Append Data using GET |
| Setting | Value |
|---|---|
| Successful & Failed Transactions | [https://hostedpayments.parkadmin.com/hook/cashnet/CLIENTS-UNIQUE-HOSTED-ID/?cb=TO-BE-DETERMINED](https://hostedpayments.parkadmin.com/hook/cashnet/CLIENTS-UNIQUE-HOSTED-ID/?cb=TO-BE-DETERMINED) |
| Select format for HTTP content | Name Value Format (POST) |
| ## User Management Permissions | |
|---|---|
| Permission Names | Description |
| View Users | Allows the admin user to view, but not change, the users in the system. User Search functionality is enabled. |
| Edit Users | Allows the admin user to edit users in the system including new User Registration. This should be used with the 'View Users' permission. - If 'View Users' is enabled, Admins can see the user history including Permits and Violations issued (but not the details) and any payments outstanding for this user. - If 'View Users' is not enabled, Admins can only use the User Registration portion and cannot search for existing users. |
| Delete User Aliases | This permission allows users to Update User Aliases. It cannot be used without 'View Users' and 'Edit Users' turned on. |
| Edit Vehicle Information | Allows Admin to update vehicles and view the vehicle's history. Admins can also do a Plate Search from the User Management menu. In addition, Admins can see the DNTT reports. |
| Edit Forms | Allows Admins to create, update and view forms. |
| View Forms | Allows Admins to view all forms and see the user-submitted entries of forms. Users cannot create or edit forms without the 'Edit Forms' permission. |
| Clear Alarms on User Profile | Allows Admins the ability to update and clear alarms on the user's profile. This must be used with 'View Users' and 'Edit Users' permissions enabled. |
| Send Bulk Email | Allows Admins to send email messages to various groups of Users. |
| ## Locker Permissions | |
|---|---|
| Permission Names | Description |
| Building Areas | Allows the Admin user to view buildings and building areas and add buildings and building areas. You must use this with the 'View Lockers' permission. |
| View Lockers | Allows the Admin to view lockers and look at locker history. As well the Admin can see lockers awaiting payment. |
| Edit Locker Information | Allows users to edit the locker information. |
| Allocate Lockers | Ability to allocate locker numbers to a building area. |
| Edit Locker Allocations | Allows creation and editing of locker sales windows, allows Admin users to view active locker sales window |
| Allocation Locker - Single | Admins are able to add new buildings and building areas, able to create and update certain lockers. You must have 'View Lockers' enabled to use this permission effectively. |
| ## Parking Permissions | |
|---|---|
| Permission Names | Description |
| Pricing & Lot Administration | Allows Admins to create and edit lots. This permission will not work by itself. The Admin must also have the following permissions: - View Permits - Edit Permits - Allocate Permits - Edit Permit Allocations |
| View Permits | This allows the Admin to view Permit records, do Permit Switches and to view waiting lists. |
| Edit Permits | This allows the Admin to edit Permit details. This permission allows access to most functions that relate to permits. |
| Allocate Permits | Grants the ability to allocate permits to different lots. This permission will also grant all privileges of the 'View Permits' permission. |
| Edit Permit Allocations | Allows access to edit the Permit Allocation Sales Window and the Active Permit Sales Window. |
| View Access Cards | Allows the Admin to view Access cards. This will not work without the 'View Permits' permission enabled as well. |
| Edit Access Cards | Allows the Admin to edit Access cards. This will not work without the 'View Permits' permission enabled as well. |
| Add Access Cards | Allows the Admin to add Access cards. This will not work without the 'View Permits' permission enabled as well. |
| Prorate Permit Purchases | Allows the Admin to prorate permit purchases for the end user. This cannot be used without 'User Management' permissions and 'Edit Permits' enabled. |
| Create Temp Permit Entries | Allows Admins to use the Parking Validation utility. Please note, |
| ## Violations Permissions | |
|---|---|
| Permission Names | Description |
| View Violations | Allows the Admin to see information about violations including, basic user details and details of any payments. |
| Edit Violations | Allows the Admin to search for violations. This permission requires 'View Violations' to see the details. |
| Edit Violation ticket number | Grants the ability to edit a violation number if you also have the 'View Violations' permission. |
| Display as Ticket Writer | Grants the ability to be a ticket writer on the Handheld or the Web if the Admin also has the 'Add New Violations'. |
| Add New Violations | Allows the Admin to issue a violation. The Admin must have the 'Edit Vehicle Information' permission found in the User Management section. |
| Grant Violation Appeals | Gives the ability to manage Appeals and grant them. The Admin must have the 'View Appeal Reports' permission as well. |
| View Appeal Reports | Allows the Admin to view Appeal reports for different officers. Admins must also have the 'View Violations' and 'Edit Violations' permissions. |
| Issue / View Violation Notices | Allows the Admin the ability to issue and View Violation Notices. |
| Manage Collections | Grants the ability to manage the collections process for violations. |
| View Violation Reports | Allows the Admin to view financial and statistical reports regarding violations. Admins must have the 'View Violations' permission as well. |
| ## Incident Permissions | |
|---|---|
| Permission Names | Description |
| Add/Edit Contact History User Notes | Grants the Admin the ability to add / edit notes in contact history. You must have User Management permissions to use this since it is accessed through the user profile. |
| Delete User Contact History Notes | Grants the Admin the ability to delete User notes in contact history. You must have User Management permissions to use this since it is accessed through the user profile. You must also have the 'Add/Edit Contact History User Notes' permission. |
| View All Incidents | This is a master permission that grants the ability to view all Incidents. This permission is normally used for high-level Admins as it grants access to all information. |
| Add Incidents | Allows the Admin to add incidents and have an incident reported on their behalf. |
| Delete Incident | USE WITH CAUTION - This permission should only be added to a Primary Admin. If this is enabled the Admin can remove the incident and all related records and files where they are not used in other reports. There is a button on the incident to "Delete Incident". |
| Open Incidents | Allows the Admin to open incidents that are closed. This requires the 'View all Incidents' permission. This permission is normally used for high-level Admins. |
| Edit Incidents | Grants the ability to edit Incidents. This requires the 'View all Incidents' permission. This permission is normally used for high-level Admins. |
| View Incidents - Self | Allows the Admin to view Incidents if they are listed as the reporter. |
| Edit Task Notes on Incidents | Grants the ability to edit comments on Incident tasks. Requires the 'View all Incidents' permission. |
| Edit Incident summaries | Allows the Admin to edit Incident Summaries. Requires the 'View all Incidents' permission. |
| Incident Administrator | Grants the ability to view and edit incidents. This permission is normally used for high-level Admins. |
| View/Edit Confidential Information | Allows the Admin to View/Edit Confidential Information on reported incidents. Requires the 'View all Incidents' permission. |
| Be assigned Tasks Directly | Allows the Admin to be assigned as an investigator for an Incident. |
| Edit Incident Tasks | Grants the ability to edit Incident Tasks. Requires the 'View all Incidents' permission. |
| Close Incidents / Checklists | Grants the ability to close Incidents and Checklists. Requires the following permissions: - View all Incidents - Incident Administrator |
| Assign Incident to Case Manager | Allows the Admin to Ability to assign a Case Manager to an Incident. Requires the 'View all Incidents' permission. |
| Assign Incident To An Investigator | Allows the Admin to assign an Investigator to an Incident. Requires the 'View all Incidents' permission. This permission is normally used for high-level Admins. |
| Assign Incident To A Different Investigator | Allows the Admin to assign a different Investigator to an Incident. Requires the 'View all Incidents' permission. This permission is normally used for high-level Admins. |
| Is Incident Case Manager | Allows the Admin to be listed as a Case Manager that can be assigned to an Incident. |
| Is Incident Shift Manager | Allows the Admin to be listed as an Incident Shift Manager. This will require some other high-level permissions as required for the job. |
| View Incidents Distribution Reports | Grants the ability to view the Incident Distribution Reports. |
| View Incident Reports | Grants the ability to view all Incident Reports in OPS-COM. |
| View Incident In-House Report | Grants the ability to view the Unpaid In-House Incident report. |
| Export Incident Reports | Grants the ability to export the Recent Incidents Report and the Sub-location Report to Excel. |
| ## Dispatch Permissions | |
|---|---|
| Permission Names | Description |
| View License Plate Alarms | Allows Admins to view License Plate alarms. |
| Receive License Plate Alarms via email | Allows Admins to receive Plate Alarms via email if they also have subscribed to the Alarms list. |
| View People Alarms | Allows Admins to view People alarms. |
| Receive People Alarms via email | Allows Admins to receive People Alarms via email if they also have subscribed to the Alarms list. |
| Add New Dispatch Logs | Grants the ability to add dispatch logs. |
| Edit Dispatch Logs | Grants the ability to edit the Admin's own dispatch logs. |
| Edit All Dispatch Logs | Grants the ability to edit the dispatch logs of other Admins. |
| Open Dispatch Logs | Allows Admins to Open dispatch logs. |
| View Dispatch Logs | Allows Admins to View dispatch logs and close log records. |
| Add/Drop Dispatch Logs | Grants the ability to remove the association of a Dispatch Log with an incident. |
| View Cameras | Allows the Admins to view Cameras, if this is configured with OPS-COM. |
| ## Payment Permissions | |
|---|---|
| Permission Names | Description |
| Manage User Credit Cards | Grants the ability to add, remove and update credit cards from Users. |
| View Payments | Grants the ability to view payments. Limited access to user information is also granted. |
| Edit Payments | Allows the Admin to process payments. Admin must have the 'View Payments' permission. |
| Change Payment Type | Allows the Admin to change the Payment Type of a payment. |
| Drop Payments | Allows the Admin to drop payments. |
| Mark Bulk Payments | Grants the ability to mark Bulk payments for bulk processing. |
| Refund Payments | Grants the ability to refund payments, but not process. |
| Process Refunds/Adjustments | Allows the Admin to process refunds and adjustments. |
| ## System Content Permissions | |
|---|---|
| Permission Names | Description |
| View and Select Files | Grants the ability to view and select files for use in editors. Admins must have the 'Manage System Messages' permission as well. |
| Manage Files | Allows the Admin to add and remove files for use with content editors. Admins must have the 'Manage System Messages' permission as well. |
| Manage System Messages | Grants the ability to edit the email templates, home page messages, system messages, Temp Permit Text and Notice Literature. |
| View History Search | Allows the Admin to view history searches if they also have the corresponding User Management permissions. |
| Purge Old Data | Allows the Admin to purge Data older than 7 years. |
| ## System Configuration Permissions | |
|---|---|
| Permission Names | Description |
| Manage Roles | Grants the ability to manage roles and permissions. This is typically the job of a Primary Admin only. |
| Edit Administrators | Allows the Admin to edit other Admin user accounts and assign roles based on their job description. This requires 'Manage Roles' to function. This is typically the job of a Primary Admin only. |
| Manage System Configuration | Grants the ability to edit the System Settings. This is typically the job of a Primary Admin only. |
| Manage User Types and Departments | Allows the Admin to manage User Types and Departments. |
| Manage Vehicle Configuration | Allows the Admin to setup the different Vehicles descriptions that are used in OPS-COM. |
| Manage Permit Types and States | Allows Admins to manage the Zones, Groups, Common Lots and Permit States. This must be used the 'Edit Permits' permission. |
| Manage Access Cards | Grants the ability to setup Access card options. |
| Manage Barcodes | Allows the Admin to setup Barcode options. |
| Manage Locations | Grants the ability to setup Locations options for use in OPS-COM. |
| Manage Handhelds | Allows the Admin to manage settings stored in the Handheld Commons area |
| Manage Violation Offence Types | Allows the Admin to manage ticket types and ticket offence items. |
| Manage Alert Lists | Allows the Admin to setup alert and alarm email lists. |
| Manage Distribution Configuration | Allows the Admin access the Distribution setup options. |
| Manage Dispatch Configuration | Grants the ability to the Dispatch setup options. |
| Manage Incident Configuration | Allows the Admin to configure the IncidentAdmin options. |
| Manage Cameras | Grants the ability to Admin to access the Camera options. |
| Reset Database | Allows the Admin to the reset their preview database for testing. |
| Manage Duplicates | Grants the ability to resolve duplicates in the system. |
- User Name
- Address Information
- Phone Information
- License Information
- Student Information
- Employee Information
| ### General System Component | ||
|---|---|---|
| Setting Name | Definition | Notes |
| Default Notification Email | The address you wish all notifications from OPS-COM be sent to | |
| Organization Name: Website | Set the name of the Organization | |
| Organization Name: Handheld | Set the name of the Organization that appears on the handheld | |
| Country | Set the country where the system is located | |
| Company Address | Set your primary street address here | |
| Time zone | Set the time zone based on your closest major city | |
| System Timeout | Set how long the system can be idle before timeout (can be up to 6 hours) | |
| From Email | This address will be the return address that appears in emails sent from OPS-COM | |
| Time offset (mins) | This represents your time offset from Greenwich mean time | |
| Using daylight savings | Used to toggle whether or not you are subject to daylight savings time | |
| System Timeout | Set length of time before the admin user is automatically logged out of OPS-COM | |
| Run the Task Scheduler | Used to toggle whether or not your system uses the Task Scheduler | |
| Template Editor | Choose between RAW HTML Editor and a WYSIWYG Visual Editor | |
| Select how to show dates | Used to set the date format | |
| ### Alarms Component | ||
| **Setting Name** | **Definition** | Notes |
| Use Alarms System | Controls if the Client can use Alarms module | Admins can see, only OPS-COM Team can change. |
| Alarm Duration | ||
| Generic Alarm Append Threshold | Picklist that allows you to determine the type of alarm you want to issue, and what Action you want taken. In addition you choose the Dispatch Sub Category that should be associated with this Alarm. For example, People Alarms should generate a System Alert with a Sub-Category of Personal Safety Reports. | |
| People Alarm Append Threshold | Same as above | |
| Vehicle Alarm Append Threshold | ||
| Stolen Device Append Threshold | ||
| Email Address | Email Address that an alert is sent to | |
| Generic Alarm | Same as above | |
| People Alarm | ||
| Plate Alarm | ||
| ### Collections Component | ||
| **Setting Name** | **Definition** | Notes |
| Days before CRC is eligible | Set the length of time before a ticket is sent to court | |
| MTO Lookups on all records | Perform an MTO Lookup on all records even if a user profile exists | |
| Include All Unpaid Violations | When Toggled on: Includes all unpaid Violations when sending violation notices When Toggled off: Only the violation in question will be included in the letter | |
| Prevent Violation Payment | Prevents violations from being paid through OPS-COM if they have been sent to collections | |
| Prevent Purchases | Prevents Users from making any permit purchases if this is enabled and a violation has been sent to collections | |
| Send Letter To All | When Toggled on: Send collections letter to all users even if they have been emailed a copy | |
| **Deposits Component** | ||
| **Setting Name** | **Definition** | Notes |
| Use Deposits | Toggle the use of deposits on or off | |
| Enable Deposits For Permits | ||
| ### Forms Component | ||
| **Setting Name** | **Definition** | Notes |
| Default email for sending form entries | These settings are used to control the Forms Module | |
| ### Global Component | ||
| Setting Name | Definition | Notes |
| Email Image Header | Select an image to appear in the header of all emails | |
| Default Site Logo | Select a logo that appears on the mobile app, Text2ParkMe and the QR code interface | |
| Default Site Header | Select a background image that appears in the header of the mobile app, Text2ParkMe and the QR code interface | |
| Disable nightly email notifications | Disable auto-emails during system maintenance | |
| Symbol before the dollar value | Which currency symbol to use before a dollar value | Accommodates the English format of the dollar value $100.00 |
| Symbol after currency value | Which currency symbol to use after a dollar value | Accommodates the French format of the dollar value 100,00$ |
| ### Handheld Device | ||
| **Setting Name** | **Definition** | Notes |
| **Network Communication Model** | Select Standard or Volley | |
| **Setting Name** | **Definition** | Notes |
| Usage Limit | ||
| Enable Megdgate nightly script. | ||
| ### Lightweight Directory Access Protocol Component | ||
| Setting Name | Definition | Notes |
| Log Failed Attempts | ||
| Use SSL | ||
| Servers | ||
| BaseDN | ||
| Account Suffix | ||
| LDAP username | ||
| LDAP password | ||
| Student Group Name | ||
| Staff Group Name | ||
| ### Licensing Component | ||
| Setting Name | Definition | Notes |
| Permits per year | Indicate the number of permits eligible to be used yearly (Usage Limit) | |
| Violations per year | Indicate the number of violations eligible to be written yearly (Usage Limit) | |
| Temp Permits per year | Indicate the number of temp permits eligible to be used yearly (Usage Limit) | |
| Number of Handhelds | Indicate the number of OPS-COM for Android Licenses to be used (Usage Limit) | |
| Mobile PL8RDR Cameras | Indicate the number of Mobile Cameras in use by client | |
| Static LPR Cameras | Indicate the number of Static Cameras in use by client | |
| Lockers per year | Indicate the number of lockers eligible to be used yearly (Usage Limit) | |
| Validation Records per year | Indicate the number of validation records eligible to be used yearly (Usage Limit) | |
| Dispatch Logs per year | Indicate the number of dispatch logs eligible to be used yearly (Usage Limit) | |
| Incidents per year | Indicate the number of incidents records eligible to be used yearly (Usage Limit) | |
| ### Lockers Component | ||
| Setting Name | Definition | Notes |
| Enable Lockers Module | Toggles the use of the Lockers Module | Admins can see, only OPS-COM Team can change. |
| Tax % | Percentage of tax to charge for lockers | |
| Map of Lockers | Used to enter a path to a diagram or map image | |
| Receipt Reply To Address | Reply to address on receipts if only a locker was purchased | |
| ### **License Plate Recognition Component** | ||
| **Setting Name** | **Definition** | **Notes** |
| Possible plate prefixes | Indicates the prefix of what typical plate reads in your region start with. (ie: 123 for Numbers, ABC for Alpha Characters) | |
| Using Mobile LPR | This checkbox will toggle on or off the use of the LPR functionality on handheld devices | |
| ### **Parking Component** | ||
| **Setting Name** | **Definition** | **Notes** |
| Validation deletion cutoff minutes | Indicate how long a validation record is editable by an admin before it is locked into the system | |
| ### Payments Component | ||
| Setting Name | Definition | Notes |
| Gateway Online | Toggle to set the status of your payment gateway (Online or Offline) | |
| Invoice Number | An incremental number for invoices. This can be set the first time you want to issue them | |
| EFT Settings | This is used if you are set up to accept EFT payments through OPS-COM. You must be set up by OPS-COM Team first, before you can change anything | Admins can see, only OPS-COM Team can change. |
| ### Permits Component | ||
| Setting Name | Definition | Notes |
| Receipt Reply To Address | Reply to address for receipts that contain permits | |
| Multiple Plate Validator | Allow multiple plates in parking validator | |
| Require Payment for Rollovers | If enabled, only permits that are paid for and processed can be rolled over | |
| Show remaining permits | If enabled, the number of remaining permits in a lot will be shown to site users. e.g. "32 Remaining" If disabled, the number of remaining permits will be replaced with "On Sale" (which hides how many permits are left from users) | Screenshot: [](https://opscom.wiki/uploads/images/gallery/2024-06/F48image.png) |
| Enable User Permit Printing | ||
| Show Total Spots Taken | ||
| Show Waiting List Rank | ||
| Show Only Visible Lots | ||
| Waitlist Email Managers | Enter the email address of the admin who will be managing the waitlists | |
| Waitlist Reservation Duration | Enter a timeframe for how long a waitlist reservation will be held before being released | |
| Receipt Reply To Address | ||
| Allow Credit Card Processing | Allows credit card payments for rollovers | Admins can see, only OPS-COM Team can change. |
| Personal Information on Permit Print | Include personal information on hang tag printing | |
| Require Mailing Address | Require a mailing address to be completed fully to purchase permits | |
| Show Permit Lots on Landing Page | Show parking permit lots on the landing page | |
| Show Only Visible Lots | Only show lots with an active visibility flag to the end user | |
| Show Waiting List Rank | Allow users to see their rank on the waiting list | |
| Show Total Spots Taken | When being added to a waiting list, show the number of spots that exist within the lot | |
| Enable User Permit Printing | Allow users to print their own permits, this requires you to have a permit PDF message under System Messaging to work | |
| Map of Permit Areas | This is the image of your parking map | |
| ### Security Component | ||
| Setting Name | Definition | Notes |
| Hash and Salt | Enable the hashing of passwords. Once set, it should not be turned off | Admins can see, only OPS-COM Team can change. |
| Require Password Update | Require password resets after an admin changes the password | Admins can see, only OPS-COM Team can change. |
| Toggle Password Expiry | Enable the use of password expiry | Admins can see, only OPS-COM Team can change. |
| Password Expiry in days | Number of days before administrator must change their password | |
| Enable Password History | Prevent passwords from being reused up to X days | Admins can see, only OPS-COM Team can change. |
| How long to remember old passwords | The number of days the system will remember old passwords to prevent re-use | |
| Minimum password length | The minimum password length for administrator passwords | |
| Enable password strength requirements | Used to set standards in password creation based on password security strength | Admins can see, only OPS-COM Team can change. |
| Numerical Characters | The minimum number of numbers required | |
| Lower Case Characters | The minimum number of lower cases needed | |
| Upper Case Characters | The minimum number of upper cases needed | |
| Non-Alpha Numeric | The minimum of a Non-Alpha required | |
| Enable Admin Lockouts | Enable admin lockouts after X invalid attempts within Y minutes | Admins can see, only OPS-COM Team can change. |
| Lockout after X Attempts | Sets the number of retries with a wrong password before the system will lock you out | |
| Login attempt timeframe | Sets the timeframe for wrong entries. For example, if you fail 3 times within 5 minutes the system will lock out this admin | |
| Lock the admin out for X minutes | Sets the length of time in minutes that the admin will be locked out. Set at 120 minutes would mean the admin would be locked out for 2 hours before another attempt at logging in would be allowed | |
| ### Third Party Component | ||
| Setting Name | Definition | Notes |
| Twilio Account Number | Admins can see, only OPS-COM Team can change. | |
| Twilio Auth Token | Admins can see, only OPS-COM Team can change. | |
| T2 API Last Successful Fetch | Admins can see, only OPS-COM Team can change. | |
| ### User Profile Component | ||
| Setting Name | Definition | Notes |
| Enable Public Registration | If disabled, the Admins control the new account registration. Existing users can log in, but no one can create a profile | |
| Profile Field Visibility | This controls the fields for the User Profile page | |
| Max Student Number Digits | The maximum number of digits allowed in a student number. This can be useful if your organization requires student numbers that follow a specific min and max count. | |
| Min Student Number Digits | The minimum number of digits allowed in a student numbers. This can be useful if your organization requires student numbers that follow a specific min and max count. | |
| Max Employee Number Digits | The maximum number of digits in an employee number. This can be useful if your organization requires employee numbers that follow a specific maximum digit count. | |
| ### Vehicles Component | ||
| Enable VIN | Toggles the use of VIN on and off | Only seen and edited by OPS-COM Team |
| Require Vehicle Year | If enabled will require the vehicle year when users are adding a new vehicle. | |
| ### Violations Component | ||
| Setting Name | Definition | Notes |
| Enable Violations Module | Toggles the Violations Module on or off, this effects the web application and handhelds If this is toggled off, clients can chalk vehicles but cannot issue violations | |
| Hide Zero Dollar Fines | When enabled, this prevents $0.00 violations, that are not warnings, from being displayed on the user side. These violations will still show up on the Admin side and will show on the Report by Officer and the Violation Summary by Officer report | |
| Days until due | Indicates the number of days from the issue date that a user has to pay a ticket before it becomes overdue | |
| Include Random Pin on Handheld Tickets | Select this item if you wish your users to have the ability to pay violations OPS-COM Quick Pay/Guest Payments. The PIN number is required in order to pay OPS-COM Quick Pay/Guest Payments | Admins can see, only OPS-COM Team can change. |
| Handheld Footer | This is the message that will be applied to the end of each ticket that gets printed from the handheld | This footer is for violations only. Admins have the ability to change these settings on their own. |
| Clear Violation Payments | ||
| Appeal days | Indicates the number of days a user has to launch an appeal | |
| Enable OPS-COM Quick Pay/Guest Payments Payments for Violations | ||
| Link Violations to users | When enabled allows violations to be the user instead of a vehicle | Admins can see, only OPS-COM Team can change. |
| The prefix to go in front of the ticket number | These characters will appear before the ticket number on the printed ticket | Admins can see, only OPS-COM Team can change. |
| The next number for printing tickets from the web | Sets the next sequential number to be on tickets printed from the web tool | Admins can see, only OPS-COM Team can change. |
| Show Driver's License on Tickets | When selected, shows License number and Province of issuance on ticket | |
| Show Ticket # as barcode on ticket | When selected, will print a bar code representing the ticket number on the ticket | |
Go into System Messaging and update the following System Messaging:
(These are the actual pages that occupy the content area between the header and footer that you configured above)
## The Pages Tab
- User Dashboard - Currently the generic page. You will want to customize this content.
- Login Screen - You will want to customize this content.
- Payments Page - Optional. This content will appear on the Payments page above the functional part of the page.
- Permits - Most clients customize this message. A good place to put a Campus Map and Messaging about permits.
- User Registration- Optional.
- My Vehicles - Optional.
## The Messages Tab
- Dashboard Message - Admin Dashboard.
- noPaymentOptions - Currently a standard generic message. Edits Optional.
- permitPDF - Set for printing a standard permit.
- permitTempPDF - Set for printing a temporary permit.
- tempPermitText - Optional.
## Popup Disclaimers
You may opt to place popup disclaimers throughout the system. These popup windows can be triggered to appear based on navigation to a page or associated with a button on a page.
- Appeals Disclaimer
- Locker Disclaimer
- Permit Disclaimer
- Vehicle Disclaimer
Email Headers and Footers Configuration
These are the common elements that will be used for all outgoing emails.
You will probably want to customize the messages as well as add your logo to the header, although there are no rules here you can decide, for example, to put the logo in the footer.
Click on toggle templates and have a look at:
- Header - You will want to customize this content.
- Footer - You will want to customize this content.
## Email Templates
These are the ones I believe you will be using at this point.
- Appeal Decision
- Appeal Submitted - Standard. Edits Optional.
- Lost Password - Standard. Edits Optional.
- Create Password registration email. - Standard. Edits Optional.
- User Receipt - Standard. Edits Optional.
- Waitlist Selected - Standard. Edits Optional.
##
Disclaimers & Messaging
There are only 2 that would be of concern.
- Payment Footer
- Receipt Header
## Notice Literature
These are notices that get sent out to end users as an email. They would use the Headers and Footers you configured above.
- Overdue Notice Literature - sent to a user when they have an overdue violation. You will want to customize this message.
- New Notice Literature - sent to a user when they have received a violation. You will want to customize this message.
# Email Server Communication Errors
## Finding Communication Errors
It is possible, that if some of the system settings and classic system settings are not setup correctly to use a **From** address, that you will receive a communication error as a response. One example would be when trying to submit the **Forgot Password** form found on the user side login page. An error message of this nature would look something like this:
[](https://opscom.wiki/uploads/images/gallery/2024-06/preimage.png)
As mentioned, this is because there is no **From** address setup in the system.
## Fixing Communication Errors
To fix this issue you would just need to update the **Reply-to Admin Email Address** found under **Classic System Settings.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/Uwhimage.png)
Once you have updated the email address this issue should be resolved. If the issue is still not resolved after completing these fields, please contact support for further assistance.
# Default Header and Footer for Mobile Readiness and SwiftDeploy
## Accessing System Settings
First we must go into **System Settings** from the **System Configuration** menu.
[](https://opscom.wiki/uploads/images/gallery/2024-06/yBQimage.png)
We are looking for the **Global** component in the list of system setting components.
[](https://opscom.wiki/uploads/images/gallery/2024-06/WPoimage.png)
In Global Setting we will see two areas where we can configure images to be used.
- Default Site Logo
- Default Site Header
[](https://opscom.wiki/uploads/images/gallery/2024-06/33simage.png)
By clicking on **Select Image** we will be taken to the **Manage Files** section where images and files are stored.
## Setting the Default Logo
Here we will select an image to be used as the default site logo.
[](https://opscom.wiki/uploads/images/gallery/2024-06/1qyimage.png)
## Setting the Default Header Image
We can now set the Default Site Header image.
[](https://opscom.wiki/uploads/images/gallery/2024-06/X2ximage.png)
Once the images are selected they will appear in the configuration settings.
[](https://opscom.wiki/uploads/images/gallery/2024-06/zSDimage.png)
## Where The Changes Appear
These images will appear in various places in the system. If no header or logo is set in the Templates and Designs section of the system, these default images will be used.
In our example we are using the default header and logo on the user portal...
[](https://opscom.wiki/uploads/images/gallery/2024-06/0Pzimage.png)
As well as the phone interface utilized in **Real-Time Parking**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/w1fimage.png)
# Email Templates
## Navigate to Email Templates
In order to find your current default email templates, you will have to login as an admin and navigate to the system config cog. From this drop-down menu, you should see **Email Content**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/USXimage.png)
Editing Default Email Templates
To edit the default email templates, you can click the **Edit** button next to the template you wish to adjust. After you click this, you will be taken to another area where you can make your changes to the current email template.
[](https://opscom.wiki/uploads/images/gallery/2024-06/79Nimage.png)
Using Shortcodes
Each email template will have available shortcodes that you can use to craft your message to your liking. The shortcode tokens are displayed on the left of the template editor. As you can see in the image below, the email template for **Appeal Submitted by User** offers the ability to craft messages without knowing when the ticket was appealed, as well as the ticket being appealed. This offers you a very quick and seamless way to make your email templates more engaging and informative.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Uo4image.png)
You should be able to use these codes in the smart editor to the right and it will display the appropriate information to the desired user. The smart editor also gives you the ability to add images and format your messages.
Email Template Fields - What do they do?
| Label | ##### The label field is how you will identify your email templates. |
|---|---|
| Type | ##### The type is an nonadjustable value that lets you know the type of the email template. |
| Language | ##### This field contains two options that allow you to select between French or English. |
| Layout | ##### Select the layout that surrounds your messaging, this allows you to have multiple different layouts for different email templates. These layouts include your email header, footer, and its styling. You can create or adjust email template layouts under **System Config → Email Headers & Footers.** |
| Subject | ##### This is the subject of the message you wish to send under the current email template. |
| HTML Content | ##### Here you will write the message your users will receive. You can insert images, shortcodes, and use the smart editor, to format your messages just like other word processors. |
| Text Content | ##### This section is a simple text editor that does not offer the use of shortcodes or any formatting. This is simply for the message itself and not necessarily the |
- To create a **Page** click the **Create Page/Message** button at the top right of the **Manage System Messaging** screen. It doesn't matter what tab you're on when you do this as you will specify the **Page Type** when you go to create the page.
- Once you click this button OPS-COM will take you to a different section where you can set the properties and content of the page. Below is a detailed description of the options available to you when creating new **Pages**.
| Page Attributes | Short Description |
|---|---|
| **Title** | The **Title** of the page you wish to create, which will be the name displayed on the user navigation bar. |
| **Path** | The path after the domain. i.e. **login*****/** → This is the home page* Changing this to **lockers/area/1** will display **login/lockers/area/1** as the URL for that page. |
| **Visibility** | You can toggle the visibility of your pages which will make it so your users can't see the page anymore, but you can still edit it. |
| **Language** | Use this to select between two language options for a specific page. Tomahawk currently supports **English** and **French**. |
| **Layout** | You can select the layout of your page here. Usually, you will have the **Default Layout** selected. |
| **Content** | Your content will be the text on the page you are currently editing. You can also use **Shortcodes** here to display a body of material or feature. For example, a user login form could be displayed on your homepage. |
- Adjust the visibility of your page by toggling the **Visible** button on/off. The **Page** will still be editable in the **System Messaging** section but it will not be visible to your users who are on your **Page** or **System Message**.
| Toggle On(Visible Page) | Toggled Off(Invisible Page) |
|---|---|
- Toggling the **Page** as invisible will show it under the **Messages** tab like seen in the image below to signify it cannot be seen by your users.
- Select the default **Language** and **Layout** of your page. If you are not sure which template to use you can leave it as the **Default Layout.**
- Provide the content of your page in the editor found under the page settings. This content will be the main content of your **Pages**; you can use **Templates & Design** to edit the other sections of your pages such as the **Header-Content** and **Footer-Content.**
- OPS-COM uses **Shortcodes** to display a section of interactive or static content like a user login, permits, etc.
1. To **Edit** a page, simply click on the **Edit** button next to the page **Title** you want to edit. As seen in the image below we are going to select and edit the **Appeals Message** page.
[](https://opscom.wiki/uploads/images/gallery/2024-06/u9Kimage.png)
2. You can now make any changes to the **Pages** content or attributes that you like.
See **Creating Pages** near the top of the page if you are not sure what a specific field does. From here we can edit the format of the text such as the colour, background color, etc..
[](https://opscom.wiki/uploads/images/gallery/2024-06/Alnimage.png)
3. If you have not made any changes to the page you are **Editing**, you may go back to the **Page List** by clicking **Return to Page List** at the top of the screen. Clicking this button will discard **all** changes recently made.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Q6Cimage.png)
4. Once you have finished editing the page, click **Save Messaging** for your changes to take effect.
[](https://opscom.wiki/uploads/images/gallery/2024-06/xIaimage.png)
| Message Attributes | Description |
|---|---|
| **Title** | The title that will be displayed across the top of the **System Message** when users navigate to that page. |
| **Identifier** | The identifier is used to know which page you want to display the message by using **Shortcodes**. |
| **Visibility** | This section toggles the visibility of your page which will make it so your users may not see the page, but you can still edit it. |
| **Language** | Select between two language options for a specific page. Tomahawk current supports **English** and **French**. |
| **Content** | Content is what will display on the actual page. You may use **Shortcodes** here to view predefined static or interactive content. For example, a user login form could be displayed on your homepage. |
| Toggle On(Visible) | Toggled Off(Invisible) |
|---|---|
| [](https://opscom.wiki/uploads/images/gallery/2024-06/XY6image.png) | [](https://opscom.wiki/uploads/images/gallery/2024-06/L2Himage.png) |
1. To **Edit** your **System Messages** click the **Messages** tab under the **Manage System Messaging** page.
2. Select the **Edit** button next to the **System Message** you wish to edit. For this example, we will be editing the **Admin Dashboard.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/elXimage.png)
3. You will now be able to adjust the message your users will see using the **System Messaging** editor. Below are the fields in which you can use to edit the **System Message**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/TZlimage.png)
4. You may use the **Title** field to change the **Title** of the **System Message**.
5. You may use the **Identifier** field to change text used to display a **System Message** to a **Page,** but this will require you to modify all **Disclaimer Shortcodes** using the old unique **Identifier** for the message you are replacing.
6. You may click **Save Messaging** when you are finished making your changes.
| Message Attributes | Description |
|---|---|
| **Title** | The title that will be displayed across the top of the **System Message** when users navigate to that page. |
| **Identifier** | The identifier is used to know which page you want to display the message by using **Shortcodes**. |
| **Visibility** | This section toggles the visibility of your page which will make it so your users may not see the page, but you can still edit it. |
| **Language** | Select between two language options for a specific page. OPS-COM currently supports **English** and **French**. |
| **Content** | Content is what will display on the actual page. You may use **Shortcodes** here to view predefined static or interactive content. For example, a user login form could be displayed on your homepage. |
## Understanding Templates & Design
**Templates & Designs** are the visual functionality of your web page structured around your **Page** content. OPS-COM provides you with default templates which allow you to get started easily without having to know any code.
- Once you are on the landing page for **Templates & Design,** you can view a list of your current templates, or create a new one. **Templates** contain all of the sections found on your **User Portal** except for the **Page** content found in the middle of the page. To adjust this you will have to leave Templates & Design and navigate to **System Messaging**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/p7wimage.png)
- OPS-COM gives you a total of 12 section templates, 6 in English and 6 in French. (Of course, you will have to create the French content yourself as we do not provide a translator).
[](https://opscom.wiki/uploads/images/gallery/2024-06/ZWOimage.png)
1. Clicking on **Toggle Templates** will display all of the sections attached to that template. Templates can be created in English and French.
2. The contents of our pages are split into four separate sections. Header(1)**,** Content Header(2), Content Footer(4), and Footer(5). See **Template Layout** right below this guide to get a better understanding of the OPS-COM layout.
3. To edit a template **Section,** simply click **Edit** next to the section name.
### Template Layout
Below is a visual example of how your **Pages** are split into **Sections** using **Templates**. All of the Content (3) of our Pages are added through the **System Messages** under **Pages**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/gJrimage.png)
1. **Header** - The header of your page, where you can find your header image and user navigation.
2. **Content\_Header** - Another header section for you to place content into, such as alerts or user information. Everything placed here will appear before the Content and Content Footer.
3. **Content** - The content of your pages. Content may not be added from Templates & Design and will require you to navigate to **System Messaging**.
4. **Content\_Footer** - The footer of your Content. Everything placed here will appear after the Content Header and Content. Again, you can use this to display alerts, messages, or additional content to your Template.
5. **Footer** - The footer of your page is where you can find useful information. You can use this area to advertise important information your users might need while using your system.
## Page Layouts and Templates
### Creating Layouts
To create a layout simply click the **Create Layout** button found at the top right of the **Layouts** page.
[](https://opscom.wiki/uploads/images/gallery/2024-06/mvtimage.png)
You will be presented with the **Add Layout** system message.
[](https://opscom.wiki/uploads/images/gallery/2024-06/ebMimage.png)
1. Provide the name of your layout. In this example, we are going to create our own Summer Layout to be used, instead of the default layout.
2. Click **Save Changes** when you are happy with the name of your layout. Once the **Layout** has been created, you can see it under the Layouts list.
3. If you wish to cancel the creation of your layout simply click **Close**.
4. You can see that our **Summer Layout** was added to the end of our Layouts List with no sections yet.
5. You can choose whether or not your template is the **Default** template at any time by clicking the **Non-Default** drop-down and selecting **Default**.
6. Anytime you add sections to your Templates it will display how many are attached next to **Toggle Templates**. As you can see, we don't have any **Sections** created yet so there are no numbers to be displayed, otherwise, clicking on **Toggle Templates** would show you a list of all the templates currently attached to that **Layout**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/lNwimage.png)
7. You can edit the layout name by clicking on the **Edit** button next to archive.
8. If you would like to archive a layout that you are no longer using, you can click the **Archive** button next to edit.
### Creating Templates
Now that you have a better understanding of how **Templates** work with **Layouts** we can start creating our own.
[](https://opscom.wiki/uploads/images/gallery/2024-06/o02image.png)
1. Click on Toggle Templates.
2. Clicking this will display the available Templates attached to the **Summer Layout**.
3. You can now **Create** a variety of templates for your page, including bilingual support.
4. If you are non-technical, it is advised not to change the code for **Scripts, Styles, Header,** and **Footer Templates**. You can use the default Style, Script, Header, and Footer Templates from All Default Templates. These can still be edited according to your company and their style guides. See **Edit the Page Style** and **Edit the Page Behaviour** below for more information.
## Edit the Page Style (CSS)
Important
This guide is used if you intend to adjust the **Templates** provided to you by OPS-COM. If you choose to rewrite your own Templates you can choose to ignore this.
**Content**
`/* Style properties of our page body, this affects the entire page. */` `body {` ` ``background``: ``black` `url``(/uploads/FILES/OC_TOMA/parking-deck.jpg) ``center` `center``;` ` ``background-``size``: cover;` ` ``background-attachment``: ``fixed``;` ` ``color``: ``#FFF``;` `}` `/* This changes the color property of --Find where these classes are used ` `.card, .modal, .list-group-item {` ` ``color``: ``#333``;` `}` |
**Slide Show**
`/* Below are all of the styles for our header slideshow at the top of each page. */` `/*--------------WORD BANK---------------` ` ``* ELEMENTS: Elements are the tags with '<>' around them such as and ` ``* We access them here by giving them a Class name or ID. ` ` ``* PROPERTIES: Properties are used to define certain styles to a class or ID.` ` ``* CLASS: Generally used to assign a style to a group of HTML elements but can be used on single elements as well.` ` ``* They are assigned within HTML elements like this: where MyClass would be your class name.` ` ``* ID's: Generally used to assign styles to a single element but can be used on multiple elements as well.` ` ``*` ` ``*--------------CLASSES-----------------` ` ``*` ` ``* To learn more about the CSS Position Property see: https://www.w3schools.com/cssref/pr_class_position.asp` ` ``* For more information on CSS Syntax and Selectors see: https://www.w3schools.com/css/css_syntax.asp` ` ``* It is not recommended to adjust with the position of elements unless you are sure about the changes being made. This can dramatically change how content is positioned. ` ` ``*/` `/* Class Names and Elements` ` ``* [.slideshow-header]: Container that contains our slides and overlay.` ` ``*` ` ``* Properties` ` ``* @position: Adjust the position of the slideshow-header. For more information see: https://www.w3schools.com/css/css_positioning.asp` ` ``*/` `.slideshow-header {` ` ``position``:``relative``;` `}` `/* Class Names and Elements ` ` ``* [.slideshow-header]: Container that contains our slides and overlay.` ` ``* [.slides]: Controls the style properties of the individual slides.` ` ``* ` ` ``* Properties ` ` ``* @z-index: Adjust the stack placement of the [.slideshow-header] and [.slides] along the Z axis.` ` ``* @position: Define the position of the page. ` ` ``* @top:Change in the position from the top of an element.` ` ``* @left: Change in the position from the left of an element.` ` ``* @right: Change in the position from the right of an element.` ` ``* @bottom: Change in the position from the bottom of an element.` ` ``* @display: Adjusts how the content is displayed on the page. See: https://developer.mozilla.org/en-US/docs/Web/CSS/display and https://www.w3schools.com/css/css_display_visibility.asp` ` ``* @align-items: Aligns the child elements of this PARENT element to be centered. For a visual example see: https://developer.mozilla.org/en-US/docs/Web/CSS/align-items` ` ``* @justify-content: Defines how the space disturbed around the child elements. For a visual example see: https://developer.mozilla.org/en-US/docs/Web/CSS/justify-content` ` ``*` ` ``* These are the style properties and values of the slideshow header and its individual slides.` ` ``*/` `.slideshow-header .slides {` ` ``z-index``: ``0``;` ` ``position``:``absolute``;` ` ``top``:``0px``;` ` ``left``:``0px``;` ` ``right``:``0px``;` ` ``bottom``:``0px``;` ` ``display``:flex;` ` ``align-items: ``center``;` ` ``justify-``content``: ``center``;` `}` `/* Class Names and Elements` ` ``* [.slideshow-header]: A container that contains our slides and overlay.` ` ``* [.overlay]:` ` ``*` ` ``* Properties` ` ``* @z-index: Used to layer elements. Elements with a higher z-index number will appear before elements that are lower.` ` ``* @position: Set the position property for the element. We recommend you do not adjust this property unless you have knowledge on how the changes will affect your page.` ` ``*` ` ``* These are the styles for the overlay, as well as additional properties for the slideshow-header.` ` ``*/` `.slideshow-header .overlay {` ` ``z-index``: ``1``;` ` ``position``:``relative``;` `}` `/*--------------ID'S---------------*/` `/* ID Names and Elements` ` ``* [#slideshow-header] is the container used to contain the images you have chosen for your header` ` ``*` ` ``* Properties` ` ``* @overflow:` ` ``* @opacity:` ` ``* @box-shadow: Create a box shadow for this element.` ` ``* EX: box-shadow: a, b, c, d(e, f, g, h); ` ` ``*/` `#slideshow-header {` ` ``overflow``: https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/overflow` ` ``box-shadow: https://developer.mozilla.org/en-US/docs/Web/CSS/box-shadow` `}` ` ` `/* ID Names and Elements` ` ``* [#slideshow-header] is the container used to contain the images you have chosen for your header` ` ``*` ` ``* Properties` ` ``* @width: 100% width will take of 100% of that element.` ` ``* @position:` ` ``*/` `#slideshow-header > div {` ` ``width``:``100%``;` ` ``position``: ``absolute``;` `}` ` ` `/* ID Names and Elements` ` ``* [#slideshow-header]: is the container used to contain the images you have chosen for your header.` ` ``* [div]: Refers to our HTML elements. ` ` ``* [img]: Refers to our images in the slideshow. ` ` ``* ` ` ``* Properties` ` ``* @width: Defines the width of the images, divs and slideshow-header. A value of 100% will display the image across the entire page. ` ` ``*/` `#slideshow-header div img {` ` ``width``: ``100%``;` `}` |
1. Translations that are in red, are translations on the adminside which are not yet supported. Since they are not supported you will see them come up in English only until the adminside is supported.
2. Translation that are in **black,** are translations that are on the userside that can currently be changed.
| **Shortcode** | **Description** |
| \[user show="firstname"\] | The first name of the user account receiving the email or messaging. |
| \[user show="lastname"\] | The last name of the user account receiving the email or messaging. |
| \[user show="email"\] | The email address of the user account receiving the email or messaging. |
| \[user show="username"\] | The username of the user account receiving the email or messaging. |
| \[user show="salutation"\] | The salutation of the user account receiving the email or messaging. |
| **Option** | **Type** | **Default** | **Purpose** |
| price | boolean | true | Shows the price. Set to false/off/0 etc. to turn off |
| sold\_out | boolean | false | If true, it will include the lots that are sold out. They will have the warning background to highlight they are sold out |
| remaining | boolean | false | If true, it will show a column for how many remaining permits are in this lot |
| type | string | If a value is set, it will filter the list to only show this lot type. Blank, or not set, will show all |
`[permitlots remaining=true sold_out=true price=true]` |
| **Example Shortcode** | **Description** |
| \[values show=violation.Ticket\] | Returns the violation ticket number. |
| \[values show=violation.user\_info.username\] | Returns the username of the user the violation belongs to. |
| \[values show=violation.writer.DisplayName\] | Returns the display name of the admin who assigned the violation to the user. |
| \[values show=violation.vehicle.Plate\] | Returns the plate of the vehicle the violation was assigned to, if applicable. |
| \[values show=violation.vehicle.province.ProvName\] | Returns the province or state of the vehicle plate. |
| \[values show=violation.vehicle.colour.ColourName\] | Returns the colour of the vehicle. |
| \[values show=violation.vehicle.plate\_type.TypeName\] | Returns the plate type of the vehicle. |
| \[values show=violation.vehicle.vehicle\_type.TypeName\] | Returns the type of the vehicle. |
| \[values show=violation.vehicle.make.MakeName\] | Returns the make of the vehicle. |
| \[values show=violation.location.LocationName\] | Returns the name of the location the infraction happened. |
| \[values show=violation.details.0.Ticket\] | Returns the violation ticket number. Alternate value location. |
| \[values show=violation.details.0.type.ViolationDescr\] | Returns the violation type description. |
- If the vehicle being added is already in the system but not currently associated with the user, the user will be prompted by asking if they wish to add this existing vehicle to the profile. In this case the same rules described here will still apply.
- It is also important to note that if you reduce the number of allowed active vehicles, users who currently have more active vehicles than the newly reduced setting will not be affected and are essentially grandfathered in. The new rule will only come into effect when the user attempts to add vehicles in the future.
1. Red fields are required to click save.
2. Yellow fields are required to work but still allow empty or invalid values to be saved.
3. Yellow fields can also indicate that a change has been made.
1. Red fields are required to click save.
2. Yellow fields are required to work, but still allow empty or invalid values to be saved.
3. Yellow fields can also indicate that a change has been made.
`` ` ``<``samlp:Response` `xmlns:samlp``=``"urn:oasis:names:tc:SAML:2.0:protocol"` `xmlns:saml``=``"urn:oasis:names:tc:SAML:2.0:assertion"` `ID``=``"_aa1963115aa6490e728c7376f4c8849813bbb..."``>` ` ``...` ` ``<``saml:Assertion` `xmlns:xsi``=``"http://www.w3.org/2001/XMLSchema-instance"` `xmlns:xs``=``"http://www.w3.org/2001/XMLSchema"` `ID``=``"_9efd79bf6425983ee9176f3d33a99d1a9176180..."``>` ` ``...` ` ``<``saml:Subject``>` ` ``<``saml:NameID` `SPNameQualifier``=``"MinionOpsComStaff"` `Format``=``"urn:oasis:names:tc:SAML:2.0:nameid-format:transient"``>_7a426e0be71f14c1f349db00d7d543b6f7dcb52baa` ` ``<``saml:SubjectConfirmation` `Method``=``"urn:oasis:names:tc:SAML:2.0:cm:bearer"``>` ` ``<``saml:SubjectConfirmationData` `NotOnOrAfter``=``"2021-08-24T16:00:41Z"` `Recipient``=``"https://minion-3.dev.parkadmin.com/auth/saml2/MinionOpsComStaff/acs"` `InResponseTo``=``"ONELOGIN_bb8a09203c888cf59af4c621a71cfa8f7559c016"``/>` ` ``` ` ``` ` ``<``saml:Conditions` `NotBefore``=``"2021-08-24T15:55:11Z"` `NotOnOrAfter``=``"2021-08-24T16:00:41Z"``>` ` ``<``saml:AudienceRestriction``>` ` ``<``saml:Audience``>MinionOpsComStaff` ` ``` ` ``` ` ``<``saml:AuthnStatement` `AuthnInstant``=``"2021-08-24T15:34:46Z"` `SessionNotOnOrAfter``=``"2021-08-24T23:34:46Z"` `SessionIndex``=``"_a7a68666092117d24aab8adecf1b0830622855b85..."``>` ` ``<``saml:AuthnContext``>` ` ``<``saml:AuthnContextClassRef``>urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport` ` ``` ` ``` ` ``<``saml:AttributeStatement``>` ` ``<``saml:Attribute` `Name``=``"uid"` `NameFormat``=``"urn:oasis:names:tc:SAML:2.0:attrname-format:basic"``>` ` ``<``saml:AttributeValue` `xsi:type``=``"xs:string"``>6ddf4027-3397-4e45-8628-0189f60fe91e` ` ``` ` ``<``saml:Attribute` `Name``=``"full name"` `NameFormat``=``"urn:oasis:names:tc:SAML:2.0:attrname-format:basic"``>` ` ``<``saml:AttributeValue` `xsi:type``=``"xs:string"``>Sarah Knowles` ` ``` ` ``<``saml:Attribute` `Name``=``"email"` `NameFormat``=``"urn:oasis:names:tc:SAML:2.0:attrname-format:basic"``>` ` ``<``saml:AttributeValue` `xsi:type``=``"xs:string"``>sknowles@tomahawk.ca` ` ``` ` ``` ` ``` ` ``` |
1. Click **Admin Options**, **Access Cards**, and **Add Bulk.**
1. Click **Admin Options, Access Cards**, and **Edit Bulk.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/Rxuimage.png)
1. Click **Admin Options**, **Barcodes** and click **Add Bulk.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/RxSimage.png)
2\. The **Barcodes Administration** page will display. To create a bulk set of Barcodes, fill out the required information fields and click "**Add Barcodes and Associations**".
[](https://opscom.wiki/uploads/images/gallery/2024-06/XWgimage.png)
# Barcodes - Edit Bulk
1. Click **Admin options**, **Barcodes** and **Edit Bulk.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/yKQimage.png)
2\. The **Barcodes Administration** page displays. To change/edit information associated with bulk barcodes, fill out the required information fields then click "**Update Barcodes and Associations"**
[](https://opscom.wiki/uploads/images/gallery/2024-06/TxOimage.png)
# Barcodes - Edit Gates
1. Click **Admin Options**, **Barcodes**, and **Edit Gates.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/Gphimage.png)
2. You will be redirected to the **Gates Administration** page. To register a ***New Gate***, click "**New**" under "**IP Address**".
[](https://opscom.wiki/uploads/images/gallery/2024-06/oB7image.png)
3\. The **Gates Administration** page will refresh, to display information fields. Fill out the required information, and click "**Update Gate**".
[](https://opscom.wiki/uploads/images/gallery/2024-06/24Oimage.png)
# Barcodes - Edit Barcodes
1. Select **Admin Options**, hover over **Barcodes** and click on **Edit Barcodes**
[](https://opscom.wiki/uploads/images/gallery/2024-06/Yhkimage.png)
2\. You will be redirected to the **Barcodes Administration** page.
[](https://opscom.wiki/uploads/images/gallery/2024-06/ux2image.png)
To **edit a barcode**, fill in the required information fields, then select **Search.** This will bring up any barcodes related to the information you supplied.
# Location Setup
- [Locations](https://opscom.wiki/books/for-administrators-staff/page/locations)
- [Locations - Sub Locations](https://opscom.wiki/books/for-administrators-staff/page/locations-sub-locations)
# Locations
Click **Admin Options**, **Manage** **Locations** and **Locations.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/9Cyimage.png)
The **Manage Locations** page displays.
[](https://opscom.wiki/uploads/images/gallery/2024-06/cQaimage.png)
|
## Adding a Location
Click the **Add Location** button to begin.
[](https://opscom.wiki/uploads/images/gallery/2024-06/freimage.png)
- Enter the name of your new location. In our example the name is **Mulloy Library**.
- Select the Sub-Location(s) you would like associated with this location. Sub-Locations are used in incident reporting and do not apply to vehicle violations.
- To have the location be **Writer Visible**, click on the **"Writer Visible"** checkbox beside the location.
- The GIS **Number** is optional and is used by clients who use a geographic location code.
- Click on **Save Changes** to continue.
The list on the left now shows 'Parked in No Parking Area' in first position and 'Parked Blocking Fire Hydrant' in second position.
Click **Admin Options**, **Incidents**, and **Categories.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/7fYimage.png)
The **Edit Categories and Sub Categories** main page will display. To ***edit** a* Category, select the desired category from the listed items and click the pencil icon to edit.
[](https://opscom.wiki/uploads/images/gallery/2024-06/zMmimage.png)
The page will refresh and you will be able to ***edit*** your **Incident Category**. Change the category name and/or details as desired and click **"Save Incident Category".**
[](https://opscom.wiki/uploads/images/gallery/2024-06/m7gimage.png)
To **add** a new **Incident Category**, return to the **Edit Categories and Sub Categories** main page, and click **"Add New Category"** located at the bottom of the page.
[](https://opscom.wiki/uploads/images/gallery/2024-06/e5Himage.png)
The page will refresh. Fill out the details for your new ***Category Name***, select whether it's "***In-House***", enter the GIS number, and select if you'd like this category included in Reports. Click **"Save Incident Category".**
[](https://opscom.wiki/uploads/images/gallery/2024-06/Y0Simage.png)
To check a category for **Sub-Categories**, return to the **Edit Categories and Sub Categories** main page. Select one of the categories by clicking on **Sub**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Ipsimage.png)
The page will refresh, and you will have the option to ***add a sub-category***.
[](https://opscom.wiki/uploads/images/gallery/2024-06/poYimage.png)
To ***add*** a new sub-category, enter the name you want for your sub-category. Enable the functions you wish to have in this subcategory.
- If a ***Checklist*** is required, click **"Required".**
- If it's to be ***Included in*** **Reports**, click **"Include"**.
- Once you have finished, click **"Save SubCategory"**.
# Ethnic Types
## Navigation to Ethnicity Administration
To get to **Ethnicity Administration** click **Admin Options**, **Incidents,** followed by **Ethnicity.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/TF9image.png)
The **Ethnicity Administration** page will be displayed. This page will list all Ethnicity labels currently used in OPS-COM.
## Managing Ethnic Types
### Adding Types
To add a new ethnicity, click **Add Ethnic Type**. A modal window will display allowing you to add your type. When you are finished adding your type click **Save Changes.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/Bfrimage.png)
### Editing Types
To edit/update an Ethnicity, click the **Edit** button next to the ethnicity you want to update. This will display a similar modal window as seen when adding an ethnic type and allow you to make your changes. When you are finished updating your type click **Save Changes**.
When you make changes to records that are already used in the system then you will be changing this for all records in the system using that ethnic type.
[](https://opscom.wiki/uploads/images/gallery/2024-06/r1gimage.png)
### Delete Types
To delete an ethnic type, click the **Delete** button next to the type you wish to remove. Keep in mind that if ethnic types are in use then they cannot be deleted.
[](https://opscom.wiki/uploads/images/gallery/2024-06/YFOimage.png)
# Extended User Profile Options
Under the **Admin Options**, hover over **Incidents**, then click on **Ext. Profile Options.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/HwUimage.png)
You will be redirected to the **User Extended Values Administration** page.
[](https://opscom.wiki/uploads/images/gallery/2024-06/WWRimage.png)
Notice the various **types** you can choose form to narrow your description.
[](https://opscom.wiki/uploads/images/gallery/2024-06/l3Nimage.png)
This is where you can **add** and **update** Extended Values.
To **add** an extended value:
Scroll to the bottom of the values list to the blank textbox line.
Select **value type** from the drop-down menu. Type the **value description** in the textbox provided.
Click **Insert New** to add and save user value.
[](https://opscom.wiki/uploads/images/gallery/2024-06/4Wuimage.png)
Note: A **Value Type** is a category you select to distinguish what your value description will be about. Example: If your **value type** is Hair Type, then your **value description** would be what the users' hair is like.
**Value Description** can include a range of physical features/identifiers of a user. Some examples could include; the location of a tattoo on a users' body, the colour of clothing they're wearing, or the style of hair they have.
Value descriptions allow officers to save unique identifiers of a user involved in an incident.
## Editing an Extended Value
Click on **Update** to edit the value.
[](https://opscom.wiki/uploads/images/gallery/2024-06/7zmimage.png)
Adjust the **category, and name by selecting the textbox and making the desired changes. In this case we are changing Bald to Balding.
[](https://opscom.wiki/uploads/images/gallery/2024-06/m9Mimage.png)
When you are finished updating, click **Save Changes** to save and continue.
# Flags
## Adding or Editing an Incident Flag
From the **Admin Options** menu, hover over **Incidents**, then click on **Flags.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/AYHimage.png)
You will be redirected to the **Edit Flags** page.
[](https://opscom.wiki/uploads/images/gallery/2024-06/kAsimage.png)
To ***add*** a flag: Click on the empty text box, and fill in the name you want for this flag. You can then choose to toggle whether this item appears on reports. The **Include In Reports** checkmark is on by default.
Click **"Add"** to complete the item entry.
[](https://opscom.wiki/uploads/images/gallery/2024-06/W4Iimage.png)
The new Flag entry will now appear in the list and is ready to use in incident reporting.
[](https://opscom.wiki/uploads/images/gallery/2024-06/wBvimage.png)
# Missing Property Types
1. Click **Admin Options**, I**ncidents** and **Missing Property Types.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/DrDimage.png)
2. The **Edit Missing Property Types and Fields** page will display. You can edit, retrieve and/or add a new Property Type.
[](https://opscom.wiki/uploads/images/gallery/2024-06/X32image.png)
3. To **add** a new missing property type:
- Click the **Add Type** button, and the page will refresh.
- Type the type of missing property in the textbox provided.
- When finished, click **Save Type**. It will now say **SAVED** across the bottom.
[](https://opscom.wiki/uploads/images/gallery/2024-06/qYPimage.png)
[](https://opscom.wiki/uploads/images/gallery/2024-06/mDIimage.png)
[](https://opscom.wiki/uploads/images/gallery/2024-06/oKbimage.png)
4\. To ***edit*** a missing property type:
- Select the missing property type you wish to edit from the drop-down menu, then click **"Retrieve"**
- The page will refresh to show the property type, and fields associated with it. To add a field to this property, click on **"Add New Field".**
- Type in the **Field Name** in the textbox, select the **Field Type** from the dropdown menu (i.e checkbox, textbox etc.) and select whether or not it is ***a required field*** by clicking on the **Required** box.
- Once you have finished, click **Save Field** to save.
[](https://opscom.wiki/uploads/images/gallery/2024-06/pc8image.png)
[](https://opscom.wiki/uploads/images/gallery/2024-06/i73image.png)
5\. To **delete** a missing property type:
- Select the property type you wish to delete from the drop down menu, and click **Retrieve**.
- If there are **no** fields found associated with that property, you can immediately click **Delete**.
[](https://opscom.wiki/uploads/images/gallery/2024-06/evTimage.png)
- If there **are** fields found associated with that property, select the **Delete** checkbox attached to that field, then click **Save All**.
- The field attached to that property will be deleted. You may then follow the above instructions to **Delete** the property type.
[](https://opscom.wiki/uploads/images/gallery/2024-06/dx6image.png)
# Relations
## Adding a Relation to the List
Click **Admin Options**, **Incidents** then **Relations.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/HbOimage.png)
You will be redirected to the **Relation Administration** page.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Hazimage.png)
You can **add** or **edit** your Relation Options.
- To **edit: Select the relation you wish to edit, change the textbox as desired, and click **update**.
- To **add: Select the empty textbox at the bottom, type in what you want as the relation, and click **Insert New.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/Df7image.png)
# Alarms Setup
## Setting up Alarms in OPS-COM
please refer to the following article Guide to System Settings to see how we can set up **Generic, People,** and **Plate** **Alarms**. We can get to the alarm settings by going to **System Settings** → **Alarms**
[](https://opscom.wiki/uploads/images/gallery/2024-06/Qjfimage.png)
## Additional OPS-COM Triggers
### Warning Email Trigger List
See the child page
### Email Alert List
See the child page
# Email Alert List
## Getting to Alerts & Alarms
To get to the alerts and alarms go to **Admin Options**, **Alerts & Alarms** followed by **Email Alert List.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/CA8image.png)
The **Alert Email Trigger List** page will display.
[](https://opscom.wiki/uploads/images/gallery/2024-06/Vq3image.png)
## Adding and Adjusting Emails
### Adding Emails
To add an email to receive alerts via E-Mail, click the **Add Alert Email** button at the top. A new modal window will appear allowing you to add a new email address as well as the option to make the alert inactive.|
[](https://opscom.wiki/uploads/images/gallery/2024-06/N9gimage.png)
### Editing Emails
To update an email that currently exists under the alert email list, click on the **Edit** button on the same row as the email you wish to change. This will bring up a modal window similar to the one you see when adding an email. This window allows you to update the email address as well as toggle the email as either active or inactive. If the button is darkened this indicated the email is active. If the button is white then it indicates the user is inactive.
[](https://opscom.wiki/uploads/images/gallery/2024-06/mRrimage.png)
## Deleting Emails
To delete an email from the list, click the **Delete** button on the same row as the email you wish to delete. This will bring up a modal window asking if you are sure you want to delete the email alert. Simply click the **Delete** button from the modal window to remove the email.
[](https://opscom.wiki/uploads/images/gallery/2024-06/LVEimage.png)
Keep in mind that deleting an email is not the same as archiving/deactivating an email. Once the email has been deleted it is removed from both the archived and active lists.
## Archiving Alert Emails
You can also choose to archive a particular email if you would like to make it temporarily unavailable to receive email alerts. By default you will not see the archived users as this requires you to click the **Toggle Archived** button.
[](https://opscom.wiki/uploads/images/gallery/2024-06/sAZimage.png)
This will display the highlighted users in red and allow you to edit or delete the email if you wish. To activate emails again make sure that you toggle the **Active** field on.
# Warning Email Trigger List
## Getting to Warning Email Trigger List
Under the **Admin Options**, hover over **Alerts & Alarms**, then click **Warning Email Trigger List.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/w5jimage.png)
You will be redirected to the **Warning Email Trigger List** page. From here, you can add, edit, or delete your **Warning Email.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/tfUimage.png)
## Adding and Adjusting Email
To **add** an email: Select Add Warning Email, then enter the email address in the text box and click **Save Changes.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/5pzimage.png)
To **edit** an email: Select Edit then make the desired changes, then click **Save Changes.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/Ddsimage.png)
To **delete** an email: Click on the **Delete** button to the right side of the email you want to delete. A pop-up confirmation window will appear. Click **Delete to delete, or click **Cancel** to return to previous page.
[](https://opscom.wiki/uploads/images/gallery/2024-06/hwCimage.png)
# Dispatch Setup
- [Dispatch Categories](https://opscom.wiki/books/for-administrators-staff/page/dispatch-categories)
- [Sources - Dispatch](https://opscom.wiki/books/for-administrators-staff/page/sources-dispatch)
# Dispatch Categories
## Navigating to Dispatch Categories
To get to this page, click on **Admin Options**, hover over **Dispatch**, then click **Categories.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/Cylimage.png)
You will be redirected to the **Dispatch Categories Administration** page. It will display a list of all categories currently in your system. From this page, you may add/edit/remove a **Category**.
## Managing Dispatch Categories
### Adding Categories
To add a new dispatch category click on **Add Dispatch Category.** A new modal window will appear allowing you to type your category name. Click **Save Changes** when you are finished.
[](https://opscom.wiki/uploads/images/gallery/2024-06/4k7image.png)
Edit Categories
To edit dispatch categories click the **Edit** button next to the category name. This will bring up a modal window similar to the one seen when adding categories. Click **Save Changes** when you are finished editing the category.
[](https://opscom.wiki/uploads/images/gallery/2024-06/mQKimage.png)
Editing dispatch categories that are being used will update them across the entire system.
Delete Categories
To delete a dispatch category simply click the **Delete** button next to the category name. Keep in mind you will not be able to delete categories that are being used.
[](https://opscom.wiki/uploads/images/gallery/2024-06/1Gqimage.png)
# Sources - Dispatch
1. Click **Admin Options**, **Dispatch** and **Sources.**
[](https://opscom.wiki/uploads/images/gallery/2024-06/Gsbimage.png)
2. The **Dispatch Category Link Administration** page will display. From here, you can add, edit, and/or delete **Source Names**, and **Categories** as needed.
[](https://opscom.wiki/uploads/images/gallery/2024-06/8B9image.png)
3. To ***add*** a new source:
- Scroll to the bottom of the **Dispatch Category Link Administration** page. Select the blank text box and type in the name of your new source.
- Select the categories that should be linked to this source from the connected drop-down menu.
- *Note: If you want to select all categories when you create this new source, you may left-click on the first category in the list (which will show up highlighted in blue once selected) and scroll down to select all.*
- Click on Insert Newto add your new source, and the selected category links.
[](https://opscom.wiki/uploads/images/gallery/2024-06/SkUimage.png)
4\. To ***edit*** a source:
- Choose the source you wish to edit from the list of sources (found on the **Dispatch Category Link Administration** page).
- Make the desired changes to the textbox (source name) and categories selected, then click **Update** to save.
[](https://opscom.wiki/uploads/images/gallery/2024-06/fIdimage.png)
5\. To ***delete*** a source:
- Find the source you wish to delete in the list of sources, then click the **Delete** button, found on the right-hand side of the page.
- A confirmation pop-up will appear. Click **OK** to confirm the delete, or click **Cancel** to return to previous page.
[](https://opscom.wiki/uploads/images/gallery/2024-06/ITkimage.png)
[](https://opscom.wiki/uploads/images/gallery/2024-06/Yr0image.png)
# Distribution Setup
- [Users - Distribution Admin Options](https://opscom.wiki/books/for-administrators-staff/page/users-distribution-admin-options)
- [Search for a User](https://opscom.wiki/books/for-administrators-staff/page/search-for-a-user)
- [Departments](https://opscom.wiki/books/for-administrators-staff/page/departments)
- [Alerts - Distribution](https://opscom.wiki/books/for-administrators-staff/page/alerts-distribution)
- [Actions - Distribution](https://opscom.wiki/books/for-administrators-staff/page/actions-distribution)
- [Status - Distribution](https://opscom.wiki/books/for-administrators-staff/page/status-distribution)
- [Warnings - Distribution](https://opscom.wiki/books/for-administrators-staff/page/warnings-distribution)
# Users - Distribution Admin Options
1. Under **Admin Options**, hover over **Distribution**, then click **Users**.
1. To get to this page, click on **Admin Options**, hover over **Distribution**, then click **Search by a User.**
| Report Title | When do we use this? |
|---|---|
| **Parking Reports** | |
| Permit Sales by Lot By Month | The 'Permit Sales by Lot by Month' report displays the lots, payment types, amount of sales processed and the number of permits sold based on a particular month. This report also provides the total sales for the month and the total number of permits sold that month. |
| Permit Sales Report | The Permit Sales Report provides a breakdown of sales for a selected allocation type and time period. |
| Active Permit Report | The Active Permits Report provides a breakdown of who owns permits for a selected allocation type and time period. |
| Temp Permit Sales Report | The Temp Permit Sales Report provides a breakdown of who has purchased temp permits within a selected time period. |
| Athletic Permit Sales | The Athletic Permit Sales report provides purchase details based on user types that include 'Athletics' or has the athletic user type included in their lot. |
| Lot Value Report | The Lot Value report will summarize your Lot utilization and total value of the permits sold in each lot. |
| Active Parker Report | |
| Midnight List | This is a list of permits that will be cleared at midnight. The permits will automatically be released from users that do not have promises for payment (e.g. the permit was reserved but the user did not specify how they were going to pay). These permits will be available for purchase again the next day. |
| **Violation Reports** | |
| Violations by Location/Officer Report | The Summary Report by Officer report allows administrators to search for Violations issued by an officer and see a summary of how many violations were : issued of each type, How many were appealed, how many were upheld, reduced or canceled, how many spoils and warnings, how many paid or unpaid |
| Paid Violations Summary by Type Report | The Paid Violations Summary by Type report allows administrators to search for Violations issued by Date and Type. The report will display the number of violations issued by type and the Total amounts for each type including Warnings. |
| Violations by Officer Report | The Violations by Officer report allows administrators to search for Violations issued by the officer. You can filter on Date, Ticket Writer, Spoil Type, and Ticket Type. The report will display the number of violations each officer has issued, the plates they were issued to, the date of the violation and the fine amounts. |
| Summary Report by Officer | The Summary Report by Officer report allows administrators to search for Violations issued by the officer and see a summary of how many violations were : issued of each type, How many were appealed, how many were upheld, reduced or canceled, how many spoils and warnings, how many paid or unpaid |
| List Overdue Report | The List Overdue report allows administrators to report on violations that have not been paid before the due date. Once the violation is paid it would drop off of this report. You can filter on User Type, Ticket Type, and Date. |
| Violations by Pay Type by Month Report | The Violations by Pay Type by Month report allows administrators to search for Violations issued by Month and Payment Type. |
| **Incident Reports** | |
| Recent Incidents Summary Report (Last 30 Days) | The Recent Incidents option provides administrators with a table of all incidents that have been recorded in the previous 30 days. |
| Search Repeat Offenders Report | The Search Repeat Offenders report allows administrators to search for users with Multiple Violations issued. You can filter on Date, Ticket Type, Number of Violations and User Types. |
| Weekly Stat Report | The Weekly Stat Report is a listing of the number of Incidents listed by category and sub category filtered by date. |
| Calls For Service | |
| Incidents Summary Report | The Incidents Summary Report allows administrators to get a summary of all incidents that have been recorded within a specified time frame. From here, administrators can also get the details of a particular incident and make updates. |
| Incidents Summary Report by Category | The Incidents Summary Report by Category allows administrators to get a summary of all incidents that have been recorded based on specified incident categories for a specified time frame. From here, administrators can also get the details of a particular incident and make updates. |
| Incident Summary Report by Sub-Location | The Incidents Summary Report by Location allows administrators to get a summary of all incidents that have been recorded based on a specified location for a specified time frame. From here, administrators can also get the details of a particular incident and make updates. |
| Incidents GIS Report (Carleton Only) | |
| Unpaid In-house Report | |
| **Payments Reports** | |
| Daily Payments | The Daily Payments report shows all of the submitted or processed payments in a certain time frame. It can be reduced to only show certain payment types during that time frame. |
| Unprocessed Payments | The Unprocessed Payment report will show all promises to pay that have been submitted but not yet marked as payments you have received. This report can be exported to Excel. |
| Processed Payroll Deduction | The Processed Payroll Deduction Report allows the admin user to report on payments processed as payroll deductions through the system grouped by day for a user defined time frame. |
| More...: Payment Reports | By clicking on "More..." the admin user will be taken to a page that offers several additional preset reports such as: List Cheque Refunds List unprocessed Cash, Cheque, and Money Order payments List unprocessed Credit Card payments List unprocessed Payroll Deduction payments List unprocessed Internal payments List ALL unprocessed payments List ALL unprocessed adjustments List ALL Processed Payroll Deductions List Daily Processed Payments (by date range) List Daily Submitted Payments (by date range) |
| Tax Exemption Report | This report will output an excel file listing all individuals that have a tax exemption number providing first name. last name and their respective tax exemption code. |
| Failed Payments | This report will show any automatic credit card payments that have failed at a certain point in time. If the payment is redone and successful after appearing in this report once it will still show up as a failed payment from during the original time frame unless it is cleared. |
| Billing Account Setup Report | This report shows a list of users who do not have their subscription settings set, meaning they will not be able to pay for automatic payments, such as rollovers. It also lists any company that is not setup with a billing account. |
| **Shortcode** | **Description** | **Additional Options** |
|---|
| **Shortcode** | **Description** | **Additional Options** |
|---|---|---|
| \[lots\_list\] | Displays a list of the currently available lots. Can be placed on any page. | \[lots\_list include\_hidden=1\] - By default, lots set as not visible will not appear in the list. This option will include those lots in the list. \[lots\_list only\_text2parkme=1\] - This will restrict the list to only show lots that have Text2ParkMe enabled. |
| **Shortcode** | **Description** |
|---|
| **Shortcode** | **Description** |
|---|---|
| \[values show=lotname\] | Displays the name of the lot. |
| \[values show=lottype\] | Displays the initial of the lot's type. |
| \[values show=lotnameid\] | Displays the lot's id. |
| \[values show=defaultcost format=currency\] | Displays how much renting a permit for the lot costs. |
| \[values show=location\] | Displays the location set for the lot. It is an address or a short description. |
| \[values show=textcode\] | The Text2ParkMe code for the lot. |
| \[values show=ratePer10Min format=currency\] | The Text2ParkMe rate for the lot. |
| \[lot show=buy\_now\] | Displays a button that will take the user to the page to purchase a permit for the lot. Will take the user to the login screen if they are not logged in or do not have an account. |
| \[lot show=map\] | Displays a small map with the lot's location according to the latitude and longitude values that are stored for it. |
| \[lot show=photo\] | Displays the photo that has been selected for the lot. A photo can be assigned from the Lot Administration page /admin/config/permits/lot/{id}/edit. |
### Select Menu
Presents a drop-down list the user can select an option from.
This is similar in function to radio-groups and checkbox groups, ideally used when there are many options to choose from to save screen space.
[](https://opscom.wiki/uploads/images/gallery/2024-07/19.png)
- **Allow Multiple Selections:** To allow the user to select more than one option (similar functionality to a checkbox group).
- **Options:** The list of options for the user to choose from. options can be added by clicking on the Add Option button.
- Note: options can be pre-selected for the user by checking the corresponding radio button
[](https://opscom.wiki/uploads/images/gallery/2024-07/222.png)
### Text Field
Used to allow the user to input text.
[](https://opscom.wiki/uploads/images/gallery/2024-07/20.png)
- **Type:** Select what type of input is needed:
- **Text Field:** is used for regular text.
- **Password:** is used for sensitive information.
- **Email:** is used to only accept email addresses.
- **Tel:** is used to only accept phone number, will display a number pad keyboard instead of the regular keyboard.
- **Max Length:** maximum number of characters allowed.
[](https://opscom.wiki/uploads/images/gallery/2024-07/21.png)
[](https://opscom.wiki/uploads/images/gallery/2024-07/22.png)
Click on the entries button for the form in question.
[](https://opscom.wiki/uploads/images/gallery/2024-07/kfE2.png)
Any fields marked searchable will appear here, providing a text box a search query can be placed in.
This can be used to narrow the search to specific values on each field.
[](https://opscom.wiki/uploads/images/gallery/2024-07/ZkA5.png)
| **Table Import** | **Requires** | **Notes** |
|---|---|---|
| UserProfile | Should be the first thing imported. | |
| Vehicles | - UserProfile | Having the user record created before the vehicle is what allows the user to be associated to the vehicle by a vehicleJoin record created during the post-import processing. |
| OffenceLocations | Doesn’t require any data beforehand, but should be included when creating a violation. | |
| Permits | - Vehicles - UserProfile | Having a vehicle record created before the permit is what allows the permit to be associated to the vehicle by a permitJoin created during the post-import processing. If there is also an associated user record, the permit is able to be marked as paid by joining the user and permit through a payment record. |
| Violations | - Vehicles - UserProfile - OffenceLocations | A violation requires the existence of a vehicle record beforehand to have the violation be created at all. Offence locations should be imported before violations in order for the violation to have its location properly marked. |
| **Inserting Into** | **Sourced From Table** |
|---|---|
| prov | Provinces |
| UserTypeID | UserTypes |
| **Inserting Into** | **Sourced From Table** |
|---|---|
| ProvID | Provinces |
| ColourID | VehicleColours |
| MakeID | VehicleMake |
| TypeID | VehicleType |
| PlateTypeID | VehiclePlateType |
| **Inserting Into** | **Sourced From Table** |
|---|---|
| LotNameID | LotName |
| StateID | PermitState |
| **Inserting Into** | **Sourced From Table** |
|---|---|
| VehicleID | Vehicle |
| TicketType | TicketCategory |
| LocationID | OffenceLocations |
- [https://opscom.wiki/books/for-administrators-staff/page/importer-field-descriptions](https://opscom.wiki/books/for-administrators-staff/page/importer-field-descriptions)
# Importer Field Descriptions
| **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 | 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 OPSCOM by default. |
| **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/](https://www.gismaps.org/)). |
| **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. |
| **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. |
| **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. |
A list of options related to flex permits.
[](https://opscom.wiki/uploads/images/gallery/2024-08/v9Eimage.png)
There is only one option for flex permits.
- **Enable flex permits** - this will enable the use of flex permits for this lot.
- If not enabled, users will not have the option to selected flex permits for this lot, even if the hourly grid is filled out.
### Time Slots
Flex permits are controlled by a grid of customizable timeslots, which are configured for each lot from the lot edit page.
The time slot section is located below the options section.
[](https://opscom.wiki/uploads/images/gallery/2024-08/o2Pimage.png)
Time slots created by the admin are located here.
- **Name** - a user-friendly name to identify what the slot should be used for
- **Price** - the price of booking a permit for the selected hour
- **Colour** - the colour that the time cells in the week grid will be marked with when they are assigned this price
### Time-slot Creation
Click the add new button to bring up the add time slot modal.
Fill in the required fields and press save changes to save the new time slot.
[](https://opscom.wiki/uploads/images/gallery/2024-07/5gK3.png)
Flex permit options will now be available as a separate option to the page.
[](https://opscom.wiki/uploads/images/gallery/2024-08/YMAimage.png)
Selecting the flex option will show the input requirements to book a permit.
[](https://opscom.wiki/uploads/images/gallery/2024-08/WFtimage.png)
Flex permit inputs:
- **Date** - the day the permit is being booked for.
- **Start Time** - The time the booking will start at.
- Flex permits are limited to booking on the hour. They do not currently support proration, meaning if a user arrives during the middle of an hour, they must pay for the entire price of the hour.
- **Duration** - the number of hours to book the permit for.
- A permit can be booked for a limit of 12 hours. If the booking would go beyond the bounds of the day, the user will be required to pick a shorter duration.
- **Vehicle** - like normal for temp permits, the user can either select a vehicle on their account or enter a new plate as a guest vehicle.
Selecting an option in the date input will cause the prices for that day of the week to appear in a box to the left side of the page.
- If the user selects one of the other options after selecting flex, the flex prices box should disappear again.
- Selecting flex again should make it reappear.
[](https://opscom.wiki/uploads/images/gallery/2024-08/X8yimage.png)
Selecting a different day will cause the flex prices box to reload with the new day's prices.
[](https://opscom.wiki/uploads/images/gallery/2024-08/2024-08-08-16-29-39.gif)
The cost of the permit will be calculated using the prices of each hour in the selected range added together.
[](https://opscom.wiki/uploads/images/gallery/2024-08/AUqimage.png)
Pressing to reserve the permit, the permit will be added to the user's cart.
[](https://opscom.wiki/uploads/images/gallery/2024-08/22Nimage.png)
### Real-Time Map
On the real-time map, the flex permits range of cost will be listed under rental costs.
[](https://opscom.wiki/uploads/images/gallery/2024-08/0YDimage.png)
Clicking here to book a permit will take the user to the guest checkout page, the same place as if they had scanned a QR code to access the lot.
If enabled, the user does not need to be logged in to access this page.
In the case where a lot group is used as an icon in place of a single lot, it will also show the range on the lot groups page.
[](https://opscom.wiki/uploads/images/gallery/2024-08/8P2image.png)
### QR Code / Guest Checkout
Similar to the standard temp permit checkout, the flex permit prices for the day will be displayed to the left side of the page.
As guest checkout permits are intended for immediate bookings, the day and time will be limited to the current date.
[](https://opscom.wiki/uploads/images/gallery/2024-08/fVcimage.png)
Upon filling in the information, the permit cost will be calculated and the user will be able to checkout immediately.
[](https://opscom.wiki/uploads/images/gallery/2024-08/gN4image.png)
Clicking on make payment, the user will be redirected to their selected payment gateway to make a payment.
# Tracking Electrical Vehicles
## Introduction
A flag has been added to vehicles that can be used to mark them as electrical.
This makes it possible to track the number of electric vehicles present on the website.
## Admin Side
Vehicles can be viewed and edited from the user vehicle list, accessible from any user's profile.
Viewing the user vehicle list page, a column is present listing if each vehicle is electrical or not.
[](https://opscom.wiki/uploads/images/gallery/2024-07/OxYimage.png)
The vehicles can be edited from this page by clicking on the plate buttons in the plate column.
On the popup that appears containing the vehicle information, the electric vehicle flag can be enabled for the vehicle using the checkbox:
[](https://opscom.wiki/uploads/images/gallery/2024-07/b4rimage.png)
Once saved, the vehicle will be counted as an electric vehicle in the system.
On the user profile, electric vehicles are marked by a blue thunderbolt icon next to the plate name.
[](https://opscom.wiki/uploads/images/gallery/2024-07/Fn4image.png)
The thunderbolt icon will show a tool tip when moused over.
[](https://opscom.wiki/uploads/images/gallery/2024-07/VABimage.png)
###
Vehicle Report
To quickly see all electric vehicles in the system, the option to search electric vehicles is available on the vehicle search page:
[](https://opscom.wiki/uploads/images/gallery/2024-07/ihaimage.png)
The records returned will contain a column called 'EV' showing if the vehicle is an electric vehicle.
Clicking on the plate buttons on this page will open a modal showing vehicle information.
Electric vehicle status will be shown at the bottom of the modal:
[](https://opscom.wiki/uploads/images/gallery/2024-07/knBimage.png)
## User Side
A user can tell if their vehicle is marked as electric by the presence of a blue thunderbolt icon displayed next to their plate number on the user vehicle list.
[](https://opscom.wiki/uploads/images/gallery/2024-07/cXAimage.png)
On the user vehicle page, electric vehicles are also marked by a blue thunderbolt icon.
[](https://opscom.wiki/uploads/images/gallery/2024-07/p3vimage.png)
A user is able to mark their vehicle as electric from this page by clicking on the vehicle edit button.
In the modal that appears, a check box is present to mark the vehicle as an electric vehicle.
[](https://opscom.wiki/uploads/images/gallery/2024-07/bOximage.png)
# Auto Email Notifications for Warnings
## Introduction
There is now the option to have a warning letter sent to those who have received a violation marked as a warning. Violations marked as a warning have had their fine amount waived.
## Setup
There is a new setting used to enable the sending of warning notices.
It can be found on the **System Settings** page.
[](https://opscom.wiki/uploads/images/gallery/2024-07/2YYimage.png)
The setting can be found under the **Violations** sub-menu.
[](https://opscom.wiki/uploads/images/gallery/2024-07/cHtimage.png)
The setting is named **Send Notices For Warnings**.
[](https://opscom.wiki/uploads/images/gallery/2024-07/SDlimage.png)
Once enabled, warning notices will be sent when the system task is run.
## Template
The layout of the warning letter can be edited on the **Email Templates** page, found under the menu tree:
- **System Configuration -> Content & Designs -> Email Templates**
[](https://opscom.wiki/uploads/images/gallery/2024-07/FMqimage.png)
The template is called **New Warning Notice**.
[](https://opscom.wiki/uploads/images/gallery/2024-07/jYUimage.png)
Here the content of the notice is setup for the email to be sent out to users with warning violations.
[](https://opscom.wiki/uploads/images/gallery/2024-07/45mimage.png)
## System Task
To have the warning notices be sent out, the system task must be run.
Tasks can be accessed from the **View System Task Logs** page, located under the **Tools** menu.
[](https://opscom.wiki/uploads/images/gallery/2024-07/c0Eimage.png)
The system task used to send violation notices is called **New Violation Notices**.
[](https://opscom.wiki/uploads/images/gallery/2024-07/d32image.png)
Like other system tasks, **New Violation Notices** is set to run at a scheduled time while it is enabled.
It can also be run immediately by pressing the run button.
While the setting **Send Notices for Warnings** is enabled, this task will include warning violations in its output. When disabled, the task will only send notices out for violations issued with a fine.
# Daily Payments - Itemized
The Daily Payments - Itemized page can be found under Payments -> Daily Payments - Itemized.
[](https://opscom.wiki/uploads/images/gallery/2024-08/2024-08-08-15-15-19.png)
On this page your can filter for submitted or processed payments based on a date range and payment type:
[](https://opscom.wiki/uploads/images/gallery/2024-08/2024-08-08-15-18-09.png)
Two options for excel export exist:
[](https://opscom.wiki/uploads/images/gallery/2024-08/yZximage.png)
- **Export to Excel (Group)**: payment items such as permits, deposits, violations, lockers, etc that are part of the same payment are grouped together.
Example:
[](https://opscom.wiki/uploads/images/gallery/2024-08/lJIimage.png)
- **Export to Excel (Line)**: payment items such as permits, deposits, violations, lockers, etc that are part of the same payment are listed on separate lines/rows.
Example:
[](https://opscom.wiki/uploads/images/gallery/2024-08/MPeimage.png)
After clicking "List Payments" results will then be displayed below the search criteria, grouped by day:
[](https://opscom.wiki/uploads/images/gallery/2024-08/nYrimage.png)
Additionally along the bottom of the page a table breakdown of daily processed orders is shown:[](https://opscom.wiki/uploads/images/gallery/2024-08/Nucimage.png)
# Review Emails Sent to Users
### Overview
All internal communications, including mass and automatic messages sent by the system, are now able to be viewed from user profiles.
The history page now lists each message sent, making it easy to track that emails have been received by their intended recipients and are being sent as expected.
Internal and automatic messaging are generated in these situations:
- New violation notices are sent
- Overdue violation notices are sent
- A receipt is sent
- An invoice is sent
These emails will now appear in the user history page.
### Viewing Emails
Emails a user has received can be viewed by going to the history section of a user's profile and selecting the sent mail page.
[](https://opscom.wiki/uploads/images/gallery/2024-08/ewaimage.png)
On the view emails page, the emails sent will be listed.
The email sent can be viewed by clicking on the subject button of the email.
[](https://opscom.wiki/uploads/images/gallery/2024-08/RIwimage.png)
This will open a popup displaying the email sent.
[](https://opscom.wiki/uploads/images/gallery/2024-08/qlAimage.png)
#### New Violation Notices
When the System Task "Send New Violation Notices" is run, it will send out notice letters to the owners of the violations by email.
The link presented on the history page will show the notice letter that was sent. This is the same view shown as when viewing the notice letter from the violation info page.
#### Overdue Violation Notices
When the System Task "Overdue Violation Notices" is run, it will send out notice letters to the owners of the violations by email.
The link presented on the history page will show the notice letter that was sent. This is the same view shown as when viewing the notice letter from the violation info page.
#### Receipts
When a user makes a payment on the website, an email will be sent to them containing the payment details.
The link presented on the history page will show a popup of the email of the receipt that was sent. Since the content of the receipt in the email that was sent can be different than is what is on an OPS-COM receipt, it will show the actual email that was sent.
#### Invoices
When an invoice is generated, it will be sent by email to the user set to receive it.
The link presented on the history page will show the invoice itself.