OperationsCommander - https://opscom.wiki

Content & Design

Email Headers and Footers

The Email Headers and Footers feature allows administrators to define and manage reusable layout components for system-generated emails. Its primary purpose is to ensure consistent organizational branding, provide essential contact information, and apply uniform styling across all automated email communications. This article is intended for OPS-COM administrators responsible for managing system configuration and visual design.

Setup and Configuration

This feature is a core administrative tool used to design the visual wrapper for outbound system emails.

Admin Side: Administrators must have the appropriate system role permissions enabled to access the contents and design configuration menus.

Using this Feature

Administrators can use the following instructions to navigate the layout list and edit individual email components.

Editing Email Layout Templates

  1. Hover over System Configuration, then Contents & Design, and click Email Headers & Footers.

  2. Click the Toggle Templates button to display the various sections of your email layouts.

  3. Locate the specific section you wish to modify (e.g., Header, Footer, or Style) and click the Edit button next to it.

  4. Add or modify text, insert images such as your organization's logo, or include inline styles directly within the HTML editor.

  5. Click the Save Changes button to finalize your updates.

  6. Click the Back button to return to the template list and edit other sections as needed.

Available Actions and Buttons

The Email Template Layout List page acts as a central repository for the individual components that wrap your messages. Remember that changes made to these foundational layout templates will globally and immediately affect all system email templates that are configured to use them.

Best Practices and Considerations

Email Templates

The Email Templates feature allows administrators to customize the content and appearance of automated emails sent by the system. Its primary purpose is to enable the creation of dynamic, informative messages using shortcodes and a smart editor, ensuring clear and consistent communication with portal users. This article is intended for OPS-COM administrators responsible for managing system communications and visual design.

Setup and Configuration

This feature is a core administrative tool used to manage outbound email content.

Admin Side: Administrators must have the appropriate system role permissions enabled to access the contents and design configuration menus. If your organization has multiple languages installed, you can click the Create button from the main template list to build localized versions of your messages.

User Side: This feature is strictly a backend administrative tool. End-users interact with the results of this configuration when they receive automated emails (e.g., password resets, appeal updates) in their personal inboxes.

Using this Feature

Administrators can use the following instructions to navigate the template list, edit default automated messages, and create custom templates for manual communications.

Editing Default Email Templates

  1. Hover over System Configuration, then Contents & Design, and click Email Templates to view the active list.

  2. Locate the specific template you wish to edit in the list.

  3. Click the Edit button next to the template to open the dedicated editor interface.

  4. Make the desired changes to the available fields and content areas.

  5. Click the Save button to apply the changes.

Available Configuration Fields

When editing an email template, administrators must configure the following fields:

Using Shortcodes

Each email template has a specific set of available shortcodes that allow you to dynamically insert user or event information into your message.

Uo4image.png

The shortcode tokens are typically displayed on the left side of the template editor. You can insert these directly into the HTML Content editor on the right side. For example, the template for an appeal might offer [ticket_appealed_date] or [ticket_number]. The system automatically replaces these shortcodes with the appropriate information when the email is generated and sent.

Creating and Using Custom Email Templates

Administrators can create and store frequently used emails that are not tied to specific system triggers. These templates automatically populate the email body when manually drafting a message to a user.

  1. Click the Create button on the main templates page.

  2. Enter a descriptive name into the Label field.

  3. Compose the message using the HTML Content and Text Content fields.

  4. Click the Save button.

  5. Navigate to the compose email page to draft a manual email to a user.

  6. Select your new template from the Load Template drop-down menu to automatically populate the email contents.

  7. Complete any highlighted required fields in the interface before clicking the Send Email button.

Unlike system-defined default templates, custom templates include a Delete button on their configuration page, allowing you to quickly remove them from the system when they are no longer needed.

Best Practices and Considerations

Translations

The Language Translations feature allows administrators to manage multi-language support and customize specific terminology displayed across the user portal. Its primary purpose is to ensure that all user-facing text, labels, and system messages are accessible and align perfectly with your organization's local terminology (e.g., changing the word "ticket" to "citation"). This article is intended for OPS-COM administrators responsible for managing portal content and localization.

Setup and Configuration

This feature is a core administrative tool used to dictate the text displayed on the user-side portal.

Admin Side: Administrators must have the appropriate system role permissions enabled to manage language settings and edit translations.

  1. Hover over System Configuration, click Content & Designs, then Translations to access the Installed Languages page.

User Side: The translation configurations directly control the language options and specific wording available to end-users navigating the parking portal.

When reviewing the translation list in the backend, translations displayed in black text are active on the user side and can be freely changed. Translations displayed in red text are located on the admin side and are not currently supported for localization; they will remain in English until admin-side translations are fully supported.

Using this Feature

Administrators can use the following instructions to add new languages, create localized sub-languages, and manually edit specific terminology across the system.

Installing and Adding Languages

Adding Sub-Languages

Sub-languages allow you to support regional variations (e.g., American English vs. British English).

  1. Ensure the primary "main" language is already created and installed.

  2. Click the Add Language button.

  3. Enter the existing main locale, followed by an underscore _, and the sub-language identifier (e.g., entering en_us for American English).

  4. Click Save Changes. The sub-language will automatically inherit the translations set up on the main language.

Editing Translations and Terminology

The translator is not just for foreign languages; it is essentially a list of code terms and their corresponding display text, allowing you to easily replace local terminology (e.g., changing "ticket" to "citation" everywhere on the portal).

  1. Click Edit Translations next to a language.

  2. Enter a specific word or component (e.g., "permit" or "ticket") into the search bar at the top right to filter the list.

  3. Click the specific text box for the term you wish to modify and type in your preferred localized text.

  4. Click away from the input field. The translation will highlight in yellow to indicate an unsaved change, and the number of affected records will display at the bottom of the page.

  5. Click the Save Changes button to apply the text updates across the system.

Creating Templates and Messaging for New Languages

When you create a brand new custom language, it will not automatically rely on the default templates and system messaging set up for previous languages. They will appear blank until configured.

  1. Hover over System Configuration, click Content & Designs, then Templates & Design.

  2. Click Toggle Templates for the templates currently being used.

  3. Click the Create button to add the new template for your language, or click Edit on an existing language to copy its text over to the new one.

  4. Hover over System Configuration, click Content & Designs, then System Messages.

  5. Click the Edit button next to an individual message, select your new language, and type out the localized translation.

Best Practices and Considerations

User Portal Branding and Setup

The User Portal Branding and Setup feature allows administrators to define the global default branding for the public-facing portal. Its primary purpose is to ensure a consistent visual presentation across the user environment by establishing a default site logo and header. This article is intended for OPS-COM administrators responsible for managing system configuration and visual design.

Setup and Configuration

This feature requires administrative access to the global system settings.

Admin Side: Administrators must have the appropriate system role permissions enabled to access the global system settings and the file management repository.

Using this Feature

Administrators can use the following instructions to configure the default logo and header images for their environment.

Configuring Default Images

  1. Hover over System Configuration and click System Settings.

  2. Click the Global tab to view the global settings section.

  3. Click the Select Image button next to either the Default Site Logo or Default Site Header setting to open your file repository.

  4. Browse or search for the specific image you wish to use within the Manage Files interface and click to select it.

  5. Click Save Settings to apply your branding selections.

Once an image is selected, its file name or a preview will appear in the respective configuration settings field. For best practices on uploading and organizing your visual assets, please refer to the Uploading and Managing Files article.

Key Information Displayed

These default images serve as global fallbacks and will appear in various places throughout the system if no specific visual assets are set in other areas (such as the Contents and Designs section). Common locations where these default images are utilized include:

Available Actions and Buttons

Best Practices and Considerations

Pages and Content Blocks

The Pages and Content Blocks feature allows administrators to create and manage the visual content and system messages displayed throughout the user portal. Its primary purpose is to enable organizations to customize their public-facing pages, embed interactive features using shortcodes, and enforce user agreements via popup disclaimers. This article is intended for OPS-COM administrators responsible for managing portal content and user communications.

Setup and Configuration

This feature is a core administrative tool used to build and maintain the user-facing portal environment.

Admin Side: Administrators must have the appropriate system role permissions enabled to access the content and design menus.

User Side: The configurations applied here directly dictate the layouts, text, interactive forms, and popup agreements that end-users interact with while navigating the parking portal.

Using this Feature

Administrators can use the following instructions to create custom pages, embed interactive shortcodes, and generate targeted system messages.

Accessing the Management Interface

  1. Hover over the gears icon (System Configuration) and click Content & Designs then Pages and Content Blocks.

Creating Pages

  1. Click the Create Page/Message button at the top right of the management screen.

  2. Select Page from the Page Type drop-down menu.

  3. Configure the following page attributes:

    • Title: Enter the name that will be displayed on the user navigation bar.

    • Path: Define the URL path after the domain (e.g., entering login/ establishes the page as the home page).

    • Visibility: Toggle the Visible button to make the page accessible or hidden to end-users.

    • Language: Select the appropriate language for the page (e.g., English or French).

    • Layout: Select the visual structure for the page. Typically, this is left as the Default Layout.

    • Content: Enter the main body text or embed shortcodes to display interactive features.

  4. Click the Save Messaging button to finalize the page creation.

Toggling a page to invisible hides it from your end-users, but it will still remain fully editable to administrators on the backend under the Messages tab. This is highly useful for drafting content.

Content Placement and Shortcodes

The smart editor reads content from top to bottom, left to right. Where you place a shortcode heavily dictates the final visual layout.

For example, placing a lot information shortcode before your text content in the editor will render the interactive lot table visually above your text on the live page. Placing the shortcode after the text will render the table below it.

Editing Pages

  1. Review the URL / System Location column in the page list to identify the specific area of the portal you are updating (e.g., updating /permits modifies the main permit screen).

  2. Click the Edit button next to the specific page title.

  3. Make the desired changes to the attributes or text formatting.

  4. Click the Return to Page List button at the top of the screen to discard all recent changes, or click the Save Messaging button to apply them.

Creating System Messages

System messages are used to offer agreements and disclaimers before users make purchases. If a user does not agree to a required system message, they are automatically redirected away from the action.

  1. Click the Create Page/Message button.

  2. Select Message from the Page Type drop-down menu.

  3. Enter a Title for the message.

  4. Create a unique Identifier. This code is strictly used to link the message to a page via a shortcode.

  5. Toggle the Visible setting, select the Language, and input your Content.

  6. Click the Save Messaging button.

Do not click the Return to Template List button before saving. Doing so will immediately discard all changes, and your system message will not be created.

Editing System Messages

  1. Click the Messages tab on the main management screen.

  2. Click the Edit button next to the system message you wish to modify.

  3. Adjust the title, identifier, visibility, language, or content as needed.

  4. Click the Save Messaging button.

Linking Messages to Pages

System messages and pages work together using disclaimer shortcodes. To display a popup message on a specific page:

  1. Copy the unique Identifier of the system message you created.

  2. Open the target page in the editor.

  3. Insert a disclaimer shortcode into the content area using the identifier (e.g., [disclaimer name=lockersDisclaimer dismiss=never]).

  4. Save the page. The system will now automatically trigger the message when users access that location.

Best Practices and Considerations

Related Videos

Templates and Design

The Templates and Design module allows administrators to heavily customize the visual functionality and branding of the User Portal. Its primary purpose is to structure the visual layout around your core page content, ensuring the portal accurately reflects your corporate branding and provides a seamless user experience. This article is intended for OPS-COM administrators.

Setup and Configuration

Configuring your portal's design involves creating a foundational layout and then building specific templates within that layout.

Admin Side:

Creating a Layout

  1. Hover over System Configuration and click Templates and Design.

  2. Click the Create Layout button located at the top right of the page.

  3. Enter a descriptive name for your new layout in the provided field.

  4. Click the Save Changes button. The layout will now appear in your Layouts list.

  5. Click the Non-Default drop-down menu and select Default if you wish to make this the active layout for your system.

Creating Templates

  1. Hover over System Configuration and click Templates and Design.

  2. Click Toggle Templates next to your newly created layout to display its available templates.

  3. Click the Create button to begin adding specific section templates to the layout, including bilingual support for English and French.

User Side: End-users do not interact with the setup of templates. They will simply view the customized layout when navigating the User Portal to register, add vehicles, purchase permits, or pay violations.

Using this Feature

The OPS-COM User Portal is split into specific visual sections using templates. All core text content is added through Pages and Content Blocks, while templates wrap around that content to provide styling and structure.

Template Sections

Available Actions & Buttons

Default System Templates

If you adjust the scripts and styles to the point of breaking your site, or you are unsure what your changes have done, you can refer to the default templates below to quickly restore your page's functionality and style.

Default Script Template

 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
<script>
    $(function(){
        $.fn.shuffle = function() {
 
            var allElems = this.get(),
                getRandom = function(max) {
                    return Math.floor(Math.random() * max);
                },
                shuffled = $.map(allElems, function(){
                    var random = getRandom(allElems.length),
                        randEl = $(allElems[random]).clone(true)[0];
                    allElems.splice(random, 1);
                    return randEl;
                });
 
            this.each(function(i){
                $(this).replaceWith($(shuffled[i]));
            });
 
            return $(shuffled);
 
        };
        $('#slideshow-header div').shuffle();
        $("#slideshow-header > div:gt(0)").hide();
 
        setInterval(function() {
            $('#slideshow-header > div:first')
                .fadeOut(1000)
                .next()
                .fadeIn(1000)
                .end()
                .appendTo('#slideshow-header');
        },  10000);
    });
</script>
Default Style Template 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
<style>
  body {
    background: black url(/uploads/FILES/OC_TOMA/parking-deck.jpg) center center;
    background-size: cover;
    background-attachment: fixed;
    color: #FFF;
  }
  .card, .modal, .list-group-item {
    color: #333;
  }
  .slideshow-header {
    position:relative;
  }
  .slideshow-header .slides {
    z-index: 0;
    position:absolute;
    top:0px;
    left:0px;
    right:0px;
    bottom:0px;
    display:flex;
    align-items: center;
    justify-content: center;
  }
  .slideshow-header .overlay {
    z-index: 1;
    position:relative;
  }
  #slideshow-header {
    overflow: hidden;
    opacity:0.8;
    box-shadow: 0 0 20px rgba(0, 0, 0, 0.4);
  }
 
  #slideshow-header > div {
    width:100%;
    position: absolute;
  }
 
  #slideshow-header div img {
    width: 100%;
  }
</style>
Default Header Template 
 
1
2
3
4
5
6
7
8
9
10
<div class="text-center slideshow-header">
  <div class="slides" id="slideshow-header">
    <div><img src="https://tomahawku.parkadmin.com/uploads/FILES/OC_TOMA/cp-downtown.jpg" /></div>
    <div><img src="https://tomahawku.parkadmin.com/uploads/FILES/OC_TOMA/cp-hospital.jpg" /></div>
    <div><img src="https://tomahawku.parkadmin.com/uploads/FILES/OC_TOMA/cp-postoffice.jpg" /></div>
  </div>
  <div class="overlay">
    <img alt="" class="img-fluid" src="/MEDIA/demo_extras/TomahawkUniversity_logo.png" style="display:inline; width: 450px; margin-top: 80px; margin-bottom:80px;"/>
  </div>
</div>
[user_menu]

Best Practices and Considerations

Form 11 Shortcodes

The Form 11 Shortcodes feature allows administrators to dynamically auto-fill specific violation details into system templates. Its primary purpose is to automatically pull nested data directly from a violation record—such as ticket numbers, user profiles, or vehicle details—and populate the issued Form 11 accurately without manual data entry. This article is intended for OPS-COM administrators responsible for configuring system templates and violation notices.

Setup and Configuration

This feature involves adding specific formatting strings directly to your system templates.

Admin Side: Administrators must have the appropriate system role permissions to access and edit system templates.

  1. Navigate to the specific system template you wish to modify.

  2. Insert the required shortcode syntax into the text editor where you want the violation data to appear.

  3. Save the template.

User Side: This is strictly a backend configuration tool. End-users will simply see the fully rendered Form 11 document with their specific violation details already auto-filled.

Using this Feature

Administrators can use the following syntax rules and data packets to construct dynamic shortcodes for their Form 11 templates.

Understanding the Base Shortcode

The base shortcode for pulling Form 11 violation data is formatted as follows:

[values show=violation._____]

The blank space must be filled with a specific variable name to pull from the violation information packet. The packet itself is always called violation, and this identifier must be placed at the very start of any value call.

Navigating Nested Values

For each nested value within the system's data packet, the parent packet name must be added as part of the variable string. Each part of the path is separated by a period (.), with the specific variable you want to output placed at the end.

Example Shortcodes

The following table provides common examples of Form 11 shortcodes. To return a specific value in the same section, simply replace the provided variable name with the sibling value you want to output.

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 registered 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 a shortcode is entered incorrectly, or if the targeted data field is empty (null) for that specific user or vehicle, the system will simply leave that space blank on the generated Form 11.

Violation Packet Reference

The violation info packet is formatted like the JSON example below. The values on the left are the exact variable names you must use in your shortcode path, while the values on the right are example outputs returned by this packet.

{
    "ViolationID": 237,
    "SemPermitID": null,
    "Ticket": "TT-19026",
    "VehicleID": 5,
    "Spoiled": 0,
    "TicketType": 1,
    "Issued": "2024-07-17 16:11:00",
    "convNotice": null,
    "Due": "2024-07-27 16:11:00",
    "ViolationTypeID": -1,
    "Fine": "50.0000",
    "AdjustedFine": "20.0000",
    "Towing": "0.0000",
    "taxAmount": "0.0000",
    "Writer": 7,
    "LocationID": 10,
    "Comment": null,
    "TicketAppeal": null,
    "appealType": 0,
    "appealFormat": null,
    "AccessAdminID": 50,
    "ActionedPer": null,
    "Created": "2024-07-17 20:12:08",
    "AppealUserID": 0,
    "AppealProcessDate": null,
    "AppealAdminID": 0,
    "AppealComment": null,
    "AppealAdminComment": null,
    "AutoNotice": 0,
    "ProcessedByCollection": null,
    "SentToCollections": null,
    "PrivateComments": "",
    "DriveAway": 0,
    "UUID": null,
    "VioNotice": null,
    "latitude": null,
    "longitude": null,
    "Warning": null,
    "userid": null,
    "incidentID": null,
    "failToIdentify": null,
    "pin": "YL",
    "duplicate": null,
    "AdjustmentReason": null,
    "notices_count": 1,
  
    "user_info": {
            "UserID": 5,
            "studentNo": null,
            "employNo": "00800147",
            "username": "mashbury",
            "firstName": "Michael",
            "preferredname": null,
            "lastName": "Ashbury",
            "street": "688 Zaproxy Ridge",
            "city": "East Romaineburgh",
            "prov": 9,
            "postal": "K2G5B1",
            "email": "mash-bury@tomahawk.ca",
            "display_name": "Michael Ashbury",
            "account_no": "00800147",
            "prov_name": "Ontario",
    },
  
    "writer": {
            "AdminAccessID": 7,
            "Username": "admin",
            "DisplayName": "Administrator"
    },
  
    "vehicle": {
            "VehicleID": 5,
            "Active": 1,
            "Plate": "MASH",
            "Year": 1998,
            "TotalVio": 12,
            "TotalUnpaid": 2,
            "TotalWarning": 0,
            "vehicleAlert": true,
            "vin": "JNAMA43H9XGE50339",
            "electric_vehicle": false,
          
            "province": {
                    "ProvName": "West Virginia",
                    "ProvCode": "WV",
            },

            "make": {
                  "MakeName": "Toyota"
            },
            
            "colour": {
                  "ColourName": "Black"
            },
            
            "plate_type": {
                  "TypeName": " Passenger"
            }
        
            "vehicle_type": {
                  "TypeName": " Van"
            },
      
    },
  
    "location": {
            "LocationID": 10,
            "LocationName": "Hospital & Administration Building",
    },
  
    "details": {
            "ViolationsDetailID": 359,
            "ViolationID": 237,
            "Ticket": "TT-19026",
            "ViolationTypeID": 16,
            "LocationID": 10,
            "offenceFine": 50,
            "discountFlag": 1,
            "discountAmount": 20,
            "discountHours": 240,
          
            "type": {
                    "ViolationTypeID": 16,
                    "ViolationDescr": "No Parking Snow Route - Mandatory Towing",
                    "DefaultCost": 50,
                    "discountFlag": true,
                    "discountAmount": 20,
                    "discountHours": 240,
            }
    }
}

Best Practices and Considerations

User Information Shortcodes

The User Information Shortcodes feature allows administrators to dynamically insert specific user details into email templates and system messages. Its primary purpose is to personalize automated communications—such as password reset emails or portal greetings—by automatically pulling data directly from the recipient's user profile. This article is intended for OPS-COM administrators responsible for configuring system communications and customizing templates.

Setup and Configuration

This feature involves adding specific formatting strings directly to your system templates or messages.

Admin Side: Administrators must have the appropriate system role permissions enabled to access and edit email templates or system messaging pages.

  1. Navigate to the specific email template or system message you wish to modify.

  2. Insert the required shortcode syntax into the text editor exactly where you want the user data to appear.

  3. Save the template or message.

Using this Feature

Administrators can use the following specific shortcodes to construct dynamic and personalized communications. To use them, simply type or paste the exact shortcode string into the text editor of your chosen email template or system message.

Shortcode Description
[user show="firstname"] Returns the first name of the user account receiving the email or messaging.
[user show="lastname"] Returns the last name of the user account receiving the email or messaging.
[user show="email"] Returns the email address of the user account receiving the email or messaging.
[user show="username"] Returns the username of the user account receiving the email or messaging.
[user show="salutation"] Returns the salutation of the user account receiving the email or messaging.

Keep in mind that these shortcode descriptions are also conveniently located directly on the email template configuration page for lost passwords, allowing for quick reference while actively drafting recovery emails.

Best Practices and Considerations

News Items (RSS Feed)

The News Feed allows administrators to broadcast timely messages and updates directly to their users. Its primary purpose is to provide a simple content management dashboard for drafting, scheduling, and publishing announcements, paired with an open syndication channel (RSS) for power users. This article is intended for OPS-COM administrators responsible for managing site communications.

Setup and Configuration

This feature is a core communication tool used to push updates to the user portal and mobile application.

Admin Side: Administrators must have the appropriate system role permissions enabled to access the content and design configuration menus to manage news items.

User Side: End-users interact with the news feed directly from the main menu of the parking portal or mobile app. The system automatically checks for new messages once every 15 minutes, displaying an alert badge above the menu icon when unread messages are available. After new messages have been viewed, they will automatically be marked as read.

Using this Feature

Administrators can use the following instructions to navigate the management interface to create, schedule, and archive news broadcasts.

Accessing the Management Interface

  1. Hover over System Configuration and click Content & Designs then News Items. Navigating this will bring you to the messages page.

Creating New Messages

  1. Click the Create New Message button located at the top of the list.

  2. Enter the title of the news post into the Title field.

  3. Enter a short blurb describing what the post is about into the Description field.

  4. Enter a link to a related webpage or the full article into the Article Link field.

  5. Enter the exact text that will appear on the link button into the Link Text field.

  6. Select the exact date on which the message will appear to users in the Published field.

  7. Enable the Visible checkbox to ensure the message will be seen by users.

  8. Click the Save Changes button.

A message will only appear to site users if the Visible checkbox is enabled and the configured publish date has already passed. This allows administrators to draft and schedule messages to appear on a set date in the future.

Archiving and Deleting Messages

  1. Click the Archive button next to a specific record in the list.

  2. Click the View Archived button to open the list of historically archived messages.

  3. Click the Unarchive button to restore a message, or click the Delete button to permanently remove it from the system.

Once a message has been permanently deleted from the system via the archived list, it cannot be recovered.

Accessing the RSS Feed

Users can bypass the application entirely and pull updates directly into their favorite RSS feed readers (such as Feedly or Slack) using standard content syndication.

  1. Access the RSS feed by appending /newsfeed/rss to the end of your standard OPS-COM website URL.

Best Practices and Considerations

Changing the Organization Name Displayed to Parkers

This feature allows administrators to update the organization's display name across the entire platform. Its primary purpose is to control the branding that appears on the public-facing parking portal, connected handheld units, and printed violation notices. This article is intended for OPS-COM administrators responsible for managing global system configurations and organizational branding.

Setup and Configuration

This is a core system setting and does not require any special backend configuration to access or modify.

Admin Side: Administrators must have the appropriate system role permissions enabled to access the global system settings menus.

User Side: This feature is strictly a backend administrative configuration. End-users do not interact directly with this setting, but the configured name will automatically display on the parking portal when they log in or browse the site.

Using this Feature

Administrators can use the following instructions to seamlessly update the organization name displayed on the web portal and on enforcement handheld units.

  1. Hover over System Configuration and click System Settings.

  2. Click General System Settings from the provided list.

  3. Locate the Organization Name: Website field at the top of the page and enter the desired display name.

  4. Locate the Organization name: Handheld field and enter the desired display name.

  5. Scroll to the bottom of the page and click the Save Changes button.

The text entered into the Organization Name: Website field will appear directly on your public-facing user portal. The text entered into the Organization name: Handheld field will appear on your enforcement officers' handheld screens and on all violation notices printed from a handheld device.

Best Practices and Considerations