Resolved issues in Pay-by-Plate Sync 4.4 - Pay-by-Plate Sync 4.4

Pay-by-Plate Sync Plugin Guide 4.4

Applies to
Pay-by-Plate Sync 4.4
Last updated
2018-03-01
Content type
Guides
Guides > Plugin and extension guides
Language
English (United States)
Product line
AutoVu > Pay-by-Plate Sync
Version
4.4

Resolved issues are software issues from previous releases which have been fixed in the current release.

The following software issues were resolved in Pay-by-Plate Sync 4.4.

Issue Description
1600858 For every call made from the Pay-by-Plate Sync plugin to the service, a redundant no authentication call is also made by the language's built-in basic authentication mechanism.
1212041 In a system that includes AutoVu™ Free-Flow and Pay-by-Plate Sync, it is not possible to use Security Center static permits instead of a third-party parking provider. However, in such a configuration, the Pay-by-Plate Sync permit is not populated because the static permit first looks for a provider, which does not exist.
1052374 When updating a system's permits, the update can result in Windows Event errors in the event logs and in the Pay-by-Plate Sync logs. This results in a slow permit update.
1045973 When you configure a Pay-by-Plate Sync system to manage transactions using the Pay-by-phone payment provider, the system generates an error.
897589 If a full Pay-by-Plate Sync permit update fails to save all of the plates to the database, and then an incremental update is performed, the plates that were not saved correctly in the full update are lost from the database.
796010 If parking zones include many permit restrictions, there can be a performance impact on the system when Pay-by-Plate Sync performs a last chance lookup.
689587 For Pay-by-Plate Sync integrations with the T2 Systems parking provider, new plates can sometimes not appear in the permit list following an incremental permit update. In such cases, a full update correctly adds the missing plates.
660523 If the same token is used to make concurrent API requests to the Pay-by-Plate Sync plugin, the system can generate a token not available error.
674506 The Pay-by-Plate Sync plugin can sometimes be installed on systems that do not meet the minimum Security Center version requirements.
653297 Pay-by-Plate Sync permit updates are performed even if the existing records have not changed. This can cause a performance impact for systems that include a large number of permits.
649231 For Pay-by-Plate Sync systems that use the generic HTTP REST service API provider, the plugin does not load if a communication error occurs during startup.
574467 When performing a permit update, the Pay-by-Plate Sync plugin can sometimes generate an error for duplicate plates in the database.
522947 When the Pay-by-Plate Sync plugin requests data from the EziCom parking provider, issues with failed permit updates and time zone handling can result in missing plates in the permit lists.
392089 When Genetec Patroller™ generates a hit on an out of zone permit using the Digital Payment Technologies parking provider, the Pay-by-Plate Sync last-chance lookup always determines that there is no infraction.
151486 When you click Update now in Security Center to perform a full permit update, the Update now button is greyed out for 60 seconds, or until the update is complete (whichever occurs first).