Changes for page Changelog
Last modified by Treyfane Dingo on 2025/04/14 17:12
From version 133.1
edited by Treyfane Dingo
on 2025/03/30 14:46
on 2025/03/30 14:46
Change comment:
There is no comment for this version
To 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
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -3,6 +3,14 @@ 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) === 7 + 8 +* Bugfix: Setting an Operative to INACTIVE now also sets the Access Level “No Access” 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 + 6 6 === 1.8.40 (30.03.2025) === 7 7 8 8 * Bugfix: Fixed Permissions for Location Database entries ... ... @@ -20,23 +20,23 @@ 20 20 21 21 === 1.8.37 (25.02.2025) === 22 22 23 -* 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 .24 -* 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 .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 25 25 26 26 === 1.8.36 (24.02.2025) === 27 27 28 -* Bugfix: debugged about a thousand bugs from Operations Status .29 -* 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 .30 -* Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable .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 31 31 32 32 === 1.8.35 (21.02.2025) === 33 33 34 -* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC .42 +* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC 35 35 36 36 === 1.8.34 (20.02.2025) === 37 37 38 -* Changed the complete JavaScript in Operations Status so the page is about 500% faster .39 -* 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 .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 40 40 41 41 === 1.8.33 (11.02.2025) === 42 42