Limitations in Genetec Mission Control™ Web API 2.2 - Genetec Mission Control™ Web API 2.2

Genetec Mission Control™ Web API Release Notes 2.2

Genetec Mission Control™
Content type
Release notes
Last updated

Genetec Mission Control™ Web API includes the following known limitations.

Issue First reported in Description
2594509 Web API 2.0 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 Web API 1.5 To apply filters on active incidents through Web API Report privilege is required.
2280989 Web API 1.3 The ChangeLocation command in Genetec Mission Control™ Web API only accepts latitude and longitude coordinates for georeferenced maps.
2117590 Web API 1.1 When triggering an incident through the Web API, if you specify the location as both an entity identifier and geographic coordinates, the location will show as the entity in the incident list, but the incident will appear on the map at the provided coordinates.
2117554 Web API 1.1 WAPI: 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 Web API 1.0 WAPI: Genetec Mission Control™ Web API does not support automatic failover like other Security Center roles.
2030530 Web API 1.0 WAPI: C# code sample is not visible when the Web API developer documentation is open in Internet Explorer.
2025944 Web API 1.0 WAPI: Audit trail report shows logon events from the machine where the Web API is installed, not the machine where the request originated.
1957969 Web API 1.0 WAPI: Cannot connect to Security Center with the Web API after changing the secure HTTP port in Server Admin.
Workaround: Restart the Genetec™ Server service.