The OperationsCommander web application has an upcoming maintenance release. Please take some time to review this information to assess the impact on your production environment and workflow.
The updates will be available on preview sites February 27th and released to production environments on March 6th.
To ensure compliance with the PCI DSS standards, OperationsCommander (OPS-COM) will removing TLS 1.0 support from our servers May 30th 2018. Our servers will refuse connections to servers and clients using TLS 1.0 from that date. More secure encryption protocols must be used – TLS 1.1 or higher (TLS v1.2 is strongly encouraged) in order to meet the PCI Data Security Standard (PCI DSS) for safeguarding data.
For more details visit https://wiki.ops-com.com/x/KAGGAg
OPS-COM can now accept EFT payments from your clients if you have done the necessary custom development to use this system. Currently, we only offer this service our clients that accept payments through the Royal Bank of Canada. Users making payments may use any financial institution to make a payment through EFT. Contact your Sales Representative if you are using another provider.
EFT is used as a recurring payment method when paying for permits through the rollover process only. EFT cannot be used in any other way in OPS-COM. For more information about configuring OPS-COM for EFT refer to the following wiki articles: https://wiki.ops-com.com/x/LQB4Ag and https://wiki.ops-com.com/x/oQBwAg
Subscriptions are new to OPS-COM. They are used to allow you to tag a default method of payment for any parking permits that you roll over from month to month. You can use payroll deductions, EFT or Credit cards as subscription payment methods. Subscriptions only affect permits that are being rolled over from a previous allocation period. For more information about subscriptions refer to the following wiki article.
Our municipal clients have a specific process that all violations go through. This process includes sending out to the Transportation authority for more information and ultimately sending unpaid violations to court for collections. In the municipal setting, most of these violations would be issued to a vehicle by license plate number. Unless this driver is a registered user in the OPS-COM system, the actual owner of the vehicle would not be known. For a detailed explanation of the life-cycle of a violation for one municipality in Ontario, including interactions with the MTO and the Ontario Court system refer to this wiki article.
There are new filters for emailing Company Managers only, as well as emailing all other users without a Company setting. For more information about using Bulk Email Options refer to this wiki article.
Invoicing Users is now supported in OPS-COM. Invoicing is only supported for permits rolling over at this time.
Our municipal clients now have a field on each offence item to store their bylaw information. This information will be stored in a format that can be picked correctly on the Court export file.
Temp permits can now be issued in a 24 hour window instead of only between 7:00am and 5:00pm
User notes are now included in OPS-COM. These notes are private and will eventually replace the Private Comments field on the user profile.
The wording for adding Aliases has been changed to to "Update Alias"
There is now restricted access to Incident reports when accessing them through the Contact History page. Admins must have the following permissions to access them: