Skip to Content

Changes for page Changelog

Last modified by Treyfane Dingo on 2025/11/09 22:15
From version 149.2
edited by Treyfane Dingo
on 2025/09/18 21:26
Change comment: There is no comment for this version
To version 132.5
edited by Treyfane Dingo
on 2025/03/30 14:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,78 +3,11 @@
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.54 (18.09.2025) ===
7 -
8 -* Bugfix: Sending several individTelegram / Pager messages in Operation Status in a row now sends several messages
9 -
10 -=== 1.8.53 (28.08.2025) ===
11 -
12 -* Changed Column names in PNG Database to better reflect the placeholders for letters
13 -
14 -=== 1.8.52 (19.08.2025) ===
15 -
16 -* Changed Self-Scheduler to not show §C: shifts to Operatives, even if they are scheduled in them – this prevents “double-shifts” like §R: ODS Team 1 and §C: ODS at the same time shown
17 -* Changed Schedule to enable keyword filtering if a specific Operative is selected
18 -* Bugfix: counter in Schedule counted events over daybreak twice – no not more
19 -* Added Operative duty hours count to counter in Schedule if Operative is selected
20 -
21 -=== 1.8.51 (16.08.2025) ===
22 -
23 -* Added counter in Schedule to calculate the hours shown in the current search / display.
24 -* Added Chinese language options and changed the “unknown” flag from EU to translingual to Operatives Management
25 -
26 -=== 1.8.50 (14.08.2025) ===
27 -
28 -* Added handling of internal location URLs to L.A.S.S.I.E. Bot and Operations Status
29 -* Added Open Location to context menu for Security Operatives
30 -
31 -=== 1.8.49 (11.08.2025) ===
32 -
33 -* Changed the Self-Scheduler to not show the red warning stripes for understaffed shifts if “show unassigned” is selected
34 -
35 -=== 1.8.48 (12.07.2025) ===
36 -
37 -* Changed errors / warnings / messages in Operations Status about adding / removing / informing units to and from Incidents to give a clearer picture if more than one Dispatch are at work
38 -* Changed FTC client to not display warning message about pager system as it'll nearly never be there anyway
39 -
40 -=== 1.8.47 (05.07.2025) ===
41 -
42 -* Bugfix: added timezone consideration to the Briefings, Items DB and Assets DB modules and the Bigscreen
43 -* Bugfix: Changed maximum field length for floor in Incident Management to 6 and changed form field to reflect maximum length
44 -
45 -=== 1.8.46 (18.06.2025) ===
46 -
47 -* Changed Show Incident to include a better functionality to search for attendees in Involved and Witnesses
48 -
49 -=== 1.8.45 (14.06.2025) ===
50 -
51 -* Bugfix: the .ics will now also work in Thunderbird (which is way more strict than everything else if it comes to slight formatting errors in an .ics …)
52 -
53 -=== 1.8.44 (06.06.2025) ===
54 -
55 -* Bugfix: Various smaller spelling corrections
56 -* Changed standard Attendee CSV importer to make it more robust
57 -* Added standard Event (Schedule) CSV importer
58 -* Changed Autofill ODS-C script to accommodate for multiple parallel ODS
59 -
60 -=== 1.8.43 (14.04.2025) ===
61 -
62 -* Bugfix: Correctly displaying error messages for missing Lat/Long in Location Management
63 -* Bugfix: Correctly displaying missing Nationality in Operatives Lists
64 -
65 -=== 1.8.42 (09.04.2025) ===
66 -
67 -* Bugfix: Setting an Operative to INACTIVE now also sets the Access Level “No Access”
68 -
69 -=== 1.8.41 (02.04.2025) ===
70 -
71 -* Added standard CSV importer to Attendee Database for all clients without individual JSON API importer
72 -
73 73  === 1.8.40 (30.03.2025) ===
74 74  
75 75  * Bugfix: Fixed Permissions for Location Database entries
76 76  * Updated Schedule and Self-Scheduler, secured and updated POSTVAR / SQL statements
77 -* Changed Operations Status and enabled COMBIUNITS with no scheduled Operatives
10 +* Changed Operations Status and enab
78 78  
79 79  === 1.8.39 (20.03.2025) ===
80 80  
... ... @@ -87,23 +87,23 @@
87 87  
88 88  === 1.8.37 (25.02.2025) ===
89 89  
90 -* 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
91 -* 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
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.
92 92  
93 93  === 1.8.36 (24.02.2025) ===
94 94  
95 -* Bugfix: debugged about a thousand bugs from Operations Status
96 -* 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
97 -* Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable
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.
98 98  
99 99  === 1.8.35 (21.02.2025) ===
100 100  
101 -* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC
34 +* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC.
102 102  
103 103  === 1.8.34 (20.02.2025) ===
104 104  
105 -* Changed the complete JavaScript in Operations Status so the page is about 500% faster
106 -* 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
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.
107 107  
108 108  === 1.8.33 (11.02.2025) ===
109 109