Skip to content

V3.0.0

Release Notes – Version 3.0.0

New Features

  • System Log
    Added a site to view logs emitted by the system in real time. These logs are only fetched inside the client session, to see the full log-history use the log files.

  • Info Page
    Added an Information page at Configuration -> Info where the currently installed version of GroundControl VGRS is displayed, as well as the license information of the external packages used.

  • Custom Event
    Added a new type of event called Custom Event to the Rule Engine. This event can currently hold up to 10 parameters to which conditions can be applied to. Custom Events may be fired by additional services or by users who want to chain multiple rules. By using the Raise Custom Event-Action inside the Rule Engine, users can specify their own custom set of parameters to publish as a Custom Event.

  • Fallback Gateway
    Changed the Tetra-Gateway Configuration to allow multiple Gateways. Users can select a primary Gateway and configure fallback Gateways to prepare for unexpected events and minimize system downtime.

  • Clear SDS
    Added Clear SDS as a schedulable action. This action functions similar to the already added Clear Event Log-Action.

  • Weather Warning Service
    Added the optional WeaterWarning-Service, which is a new custom service that will emit Custom Events based on a provided Weather Alert Information XML. For further information see the documentation of this service.

  • Terminal Gateway
    Added the Terminal Gateway Service, which provides an additional way of connecting GroundControl VGRS to the Tetra-ecosystem. For further information on the prerequisites and how to configure the Terminal Gateway see the documentation of this service.

Improvements

  • Added the number of elements to the Map-Sidebar and management tables
  • Improved the Rule Engine
    Added a more complex condition builder, allow multiple Actions, added autocomplete to the input fields. This improves the flexibility of the Rules and allows to further automate processes.
  • Expanded Rule Engine Actions
    Added additional rules to handle DGNA (Assign / Remove DGNA) and to send Mails (Send Mail). Added dropdown to choose the message type when sending SDS (Send SDS).
  • Changed services so multiple instances can be run in the same ecosystem
  • Removed the language selector, default to english
  • Removed individual licenses for Subscriber Register, Mail-Configuration and any type of Map to expand the base feature set
  • Expanded the amount of EventLogging used inside the Rule Engine
  • Added a flexible logging framework to allow a single rotating log file for all services
  • Messages sent by the RuleEngine (system) are now visible as chat-messages in chats with the respective receipient
  • Choose a default color and icon in the TrackedObject and GeoFence dialogs to increase usability
  • Rename Subscriber Management to Subscriber Register
  • Added dropdowns to choose the DGNA Assignment Mode and Class of Usage for GeoFences
  • Removed unsupported Map-Types, allow users to switch between default and custom tiling providers, added feedback when uploading files, show filename and coordinates after uploading a Map-File
  • Added a list of licensed / available features to the License overview
  • Removed configuration section for unsupported feature MailToSDSGateway
  • Allow users to modify the code of an existing Custom Status Message

Bug Fixes

  • Fixed an issue where circular GeoFences could not be deleted in the Map-Sidebar
  • Fixed an issue where some TrackedObjects did not display the correct time inside the LastSeen field
  • Fixed an issue where message templates with a lot of text would break the Chat-UI
  • Fixed an issue where changes in dialogs would immediately affect the table data without saving
  • Fixed an issue where imported GeoFences would not be added to the table immediately
  • Fixed an issue where circular GeoFences and GeoFences associated with a TrackedObject would not emit text/voice warnings
  • Fixed an issue where the details dialog could not be opened for some EventLog items
  • Fixed an issue where an error message was displayed after a successful logout

Breaking Changes / Notices

  • Updated to project to dotnet 8, requires a new runtime
  • Moved messages (including SDS) to the EventLogging DB
  • Rule Engine
    Changed the underlying structure. If your rules are not automatically migrated, use POST http://path-to-gc.url/api/rules/transformrules endpoint to trigger a migration manually