Changes for page Changelog
Last modified by Treyfane Dingo on 2025/04/14 17:12
From version 135.1
edited by Treyfane Dingo
on 2025/04/09 16:02
on 2025/04/09 16:02
Change comment:
There is no comment for this version
To version 131.2
edited by Treyfane Dingo
on 2025/03/20 22:35
on 2025/03/20 22:35
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -3,24 +3,10 @@ 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. 42(09.04.2025) ===6 +=== 1.8.39 (02.03.2025) === 7 7 8 -* Bugfix: Settingan Operative toINACTIVE now also sets the Access Level “No Access”8 +* Bugfix: Alerting of 9 9 10 -=== 1.8.41 (02.04.2025) === 11 - 12 -* Added standard CSV importer to Attendee Database for all clients without individual JSON API importer 13 - 14 -=== 1.8.40 (30.03.2025) === 15 - 16 -* Bugfix: Fixed Permissions for Location Database entries 17 -* Updated Schedule and Self-Scheduler, secured and updated POSTVAR / SQL statements 18 -* Changed Operations Status and enabled COMBIUNITS with no scheduled Operatives 19 - 20 -=== 1.8.39 (20.03.2025) === 21 - 22 -* Bugfix: Alerting of Dispatch for Status 9 and 5 works correctly again 23 - 24 24 === 1.8.38 (02.03.2025) === 25 25 26 26 * Added a Radio Log function for DMR calls, which can be used with a FurCom Radio Logger ... ... @@ -28,23 +28,23 @@ 28 28 29 29 === 1.8.37 (25.02.2025) === 30 30 31 -* 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 32 -* 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 17 +* 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. 18 +* 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. 33 33 34 34 === 1.8.36 (24.02.2025) === 35 35 36 -* Bugfix: debugged about a thousand bugs from Operations Status 37 -* 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 38 -* Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable 22 +* Bugfix: debugged about a thousand bugs from Operations Status. 23 +* 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. 24 +* Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable. 39 39 40 40 === 1.8.35 (21.02.2025) === 41 41 42 -* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC 28 +* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC. 43 43 44 44 === 1.8.34 (20.02.2025) === 45 45 46 -* Changed the complete JavaScript in Operations Status so the page is about 500% faster 47 -* 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 32 +* Changed the complete JavaScript in Operations Status so the page is about 500% faster. 33 +* 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. 48 48 49 49 === 1.8.33 (11.02.2025) === 50 50