Differences

This shows you the differences between two versions of the page.

--- support:08_private_property_tows:11_lot_configuration [2023/04/27 13:10]
edmondsj
+++ support:08_private_property_tows:11_lot_configuration [2023/08/15 07:41] (current)
edmondsj [Disable violation communications flag]
@@ Line 1: / Line 1: @@
-===== Linkage of lot to Vigilant location =====
+====== Lot configuration ======
-  * The key to linking a Ranger lot to a Vigilant location is the
+  * The ''Lot spreadsheet'' screen is shown below
 {{:support:08_private_property_tows:lot_config_1.jpg}}
+===== Linkage of lot to Vigilant location =====
+  * The key to linking a Ranger lot to a Vigilant location is the <html><span style="color:red;font-weight:bold;font-style:italic;text-decoration:underline red">Vig loc name</span></html> as shown below on the ''Lot spreadsheet'' screen above
+  * The value in the ''Name'' column is irrelevant
+  * The value in <html><span style="color:red;font-weight:bold;font-style:italic;text-decoration:underline red">Vig loc name</span></html> must EXACTLY match the value in the **Location name** as shown below in the Vigilant client portal Locations screen
 {{:support:08_private_property_tows:lot_config_2.jpg}}
+  * After the Ranger lot is configured with a Vigilant location name, the unified authorized list source will become available AFTER the first FTP upload after the configuration.  It will be named something like ''Unified-'' and location, such as the example shown below (e.g., ''Unified-Downtown'')
+  * If the <html><span style="color:red;font-weight:bold;font-style:italic;text-decoration:underline red">Diff upload?</span></html> flag is checked on a lot, the differential authorized list source will become available ONLY AFTER THE FIRST PERMIT FOR THE LOT IS ENTERED AND UPLOADED.  It will be named something like ''Differential-'' and company ID and location, such as the example shown below (e.g., ''Differential-6621-Downtown'')
+{{:support:08_private_property_tows:lot_config_3.jpg}}
+===== Communications =====
+  * Communications that are ALWAYS enabled:
+    * Permit receipts
+      * Email for non-P2P (email available) permits
+        * <html><span style="color:red">NOTE: text messages are never sent for permit receipts that have an email address</span></html>
+      * Text messages for P2P (phone number only) permits
+    * Email for guest permit receipts
+      * <html><span style="color:red">NOTE: text messages for guest permit receipts are controlled by the property flag</span></html>
+    * Ticket payment receipts
+      * <html><span style="color:red">NOTE: text messages are never sent for ticket payment receipts</span></html>
+    * Permits nearing expiration reminder (typically for P2P permits)
+      * Text messages are always sent
+==== Disable permit communications flag ====
+  * Communications that are disabled if checked:
+    * Both first time and ongoing permit approval invitation notices
+      * <html><span style="color:red">NOTE: text messages for first time notices are controlled by the property flag</span></html>
+      * Text messages are never sent for ongoing notices
+    * Unpaid permit
+    * Transfer confirmation
+    * Permit nearing expiration (long term permits)
+    * Permit approval request confirmation
+    * Permit approval extension
+==== Disable violation communications flag ====
+  * Communications that are disabled if checked:
+    * Unpaid ticket reminders
+    * Tow notices
+|  ^Frequency  ^Email  ^Text message^
+^Non-P2P permit receipt|Once  |Always|  |
+^P2P permit receipt|Once  |  |Always|
+^Guest permit receipt|Once  |Always|<html><span style="color:black;background-color: yellow">Property flag</span></html>|
+^Ticket paid receipt|Once  |Always|  |
+^P2P permit nearing expiration|Once  |  |Always|
+^Approval invitations, first time|Once  |<html><span style="color:black;background-color: yellow">Lot permit comms flag</span></html>|<html><span style="color:black;background-color: yellow">Property flag</span></html>|
+^Approval invitations, ongoing|Recurring  |<html><span style="color:black;background-color: yellow">Lot permit comms flag</span></html>|<html><span style="color:black;background-color: yellow">Property flag</span><br />First 3 days if turned on</html>|
+^Unpaid permit|Recurring  |<html><span style="color:black;background-color: yellow">Lot permit comms flag</span></html>|  |
+^Transfer confirmation|Once  |<html><span style="color:black;background-color: yellow">Lot permit comms flag</span></html>|  |
+^Permit nearing expiration (non-P2P permits)|Once  |<html><span style="color:black;background-color: yellow">Lot permit comms flag</span></html>|  |
+^Permit approval extension|Once  |<html><span style="color:black;background-color: yellow">Lot permit comms flag</span></html>|  |
+^Unpaid ticket|Recurring  |<html><span style="color:black;background-color: yellow">Lot violation comms flag</span></html>|  |
+^Tow notice|Once  |<html><span style="color:black;background-color: yellow">Lot violation comms flag</span></html>|  |
+===== Permit approval not renewable flag =====
+  * This is intended to control Property Portal and prevent the setting of future expiration date of an approval
+  * It is intended for use at properties such as university parking lots, for which an approval should be created for each new period (e.g., semester)

RangerSST Support Center

User Tools

Site Tools

Differences

Page Tools