Changes for page Changelog
Last modified by Treyfane Dingo on 2025/04/14 17:12
From version 127.2
edited by Treyfane Dingo
on 2025/02/23 22:24
on 2025/02/23 22:24
Change comment:
There is no comment for this version
To version 136.1
edited by Treyfane Dingo
on 2025/04/14 17:12
on 2025/04/14 17:12
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -3,19 +3,53 @@ 3 3 All user relevant changes to L.A.S.S.I.E. will also be explained in our L.A.S.S.I.E. Developer News Channel [[https:~~/~~/t.me/+DouU4F1US69mYzhk>>https://t.me/+DouU4F1US69mYzhk]] 4 4 ))) 5 5 6 -=== 1.8.3 5(21.02.2025) ===6 +=== 1.8.43 (14.04.2025) === 7 7 8 +* Bugfix: Correctly displaying error messages for missing Lat/Long in Location Management 9 +* Bugfix: Correctly displaying missing Nationality in Operatives Lists 10 + 11 +=== 1.8.42 (09.04.2025) === 12 + 13 +* Bugfix: Setting an Operative to INACTIVE now also sets the Access Level “No Access” 14 + 15 +=== 1.8.41 (02.04.2025) === 16 + 17 +* Added standard CSV importer to Attendee Database for all clients without individual JSON API importer 18 + 19 +=== 1.8.40 (30.03.2025) === 20 + 21 +* Bugfix: Fixed Permissions for Location Database entries 22 +* Updated Schedule and Self-Scheduler, secured and updated POSTVAR / SQL statements 23 +* Changed Operations Status and enabled COMBIUNITS with no scheduled Operatives 24 + 25 +=== 1.8.39 (20.03.2025) === 26 + 27 +* Bugfix: Alerting of Dispatch for Status 9 and 5 works correctly again 28 + 29 +=== 1.8.38 (02.03.2025) === 30 + 31 +* Added a Radio Log function for DMR calls, which can be used with a FurCom Radio Logger 32 +* Bugfix: Fixing many bugs in CSS, surely building in more 33 + 34 +=== 1.8.37 (25.02.2025) === 35 + 36 +* Added a whole new location mapping system to Incident Management which makes use of OpenStreetMap and can make use of a C3Nav compatible navigation system, e.g. EFnav 37 +* Added a function to L.A.S.S.I.E. Bot to enable Operatives to send their current geo-location which then can be used by Dispatch to find them on OpenStreetMap 38 + 39 +=== 1.8.36 (24.02.2025) === 40 + 8 8 * Bugfix: debugged about a thousand bugs from Operations Status 9 -* Changed the whole pager system connector to show better status of connections, auto-reconnect on connection failure and 42 +* Changed the whole pager system connector in Operations Status to better show the status of connections, auto-reconnect on connection failure, and have a pager status symbol just below the L.A.S.S.I.E. menu 43 +* Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable 10 10 11 11 === 1.8.35 (21.02.2025) === 12 12 13 -* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC .47 +* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC 14 14 15 15 === 1.8.34 (20.02.2025) === 16 16 17 -* Changed the complete JavaScript in Operations Status so the page is about 500% faster .18 -* Changed the stale counter for Incidents which now takes recent log entries into account, so a long-sunning incident with a recent log entry isn't shown as red blinking stale for half the day any more .51 +* Changed the complete JavaScript in Operations Status so the page is about 500% faster 52 +* Changed the stale counter for Incidents which now takes recent log entries into account, so a long-sunning incident with a recent log entry isn't shown as red blinking stale for half the day any more 19 19 20 20 === 1.8.33 (11.02.2025) === 21 21