Limitations in Mission Control Web API 2.16.4.0

Genetec Mission Controlâ„¢ Web API Release Notes 2.16.4.0

Content type
Release notes
Product line
Mission Control
Version
2.16
ft:locale
en-US
Applies to
Mission Control Web API 2.16.4.0
Issue Description
2594509
Even when there are multiple items retrieved for the GET /v2/Incidents endpoint with the IsRecipient filter set to false and the GET /v2/Incidents/{id}/Events endpoint, the TotalResultsCount still shows null value
2489269
To apply filters on active incidents through Web API Report privilege is required.
2280989 The ChangeLocation command in Genetec Mission Controlâ„¢ Web API only accepts latitude and longitude coordinates for georeferenced maps.
2117590 When triggering an incident through the Web API, if you specify the location as both an entity identifier and geographic coordinates, the location shows up as the entity in the incident list but the incident appears on the map at the provided coordinates.
2117554 After changing the language in Security Center, incident states and priorities retrieved by the Web API are shown in the language set at installation. 


Workaround:
 Change culturename in the Security Center language.xml file to the correct language.
2047551 Mission Control Web API does not support automatic failover like other Security Center roles.
2030530 C# code sample is not visible when the Web API developer documentation is opened in Internet Explorer.
2025944 Audit trail report shows logon events from the machine where the Web API is installed, not the machine where the request originated.
1957969
Cannot connect to Security Center with the Web API after changing the secure HTTP port in Server Admin.


Workaround:
 Restart the Genetecâ„¢ Server service.