Skip to Content

Changes for page Changelog

Last modified by Treyfane Dingo on 2025/11/09 22:15
From version 97.1
edited by Treyfane Dingo
on 2024/08/29 21:35
Change comment: There is no comment for this version
To version 158.1
edited by Treyfane Dingo
on 2025/11/09 22:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,10 +3,194 @@
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.21 (27.08.2024) ===
6 +=== 1.8.59 (09.11.2025) ===
7 7  
8 -* Updated Self Scheduler to include duty stats for the respective Operative
8 +* Changed all other System Settings modules to be way more mobile friendly
9 9  
10 +=== 1.8.58 (08.11.2025) ===
11 +
12 +* Changed Personal Preferences and General Settings to be way more mobile friendly
13 +
14 +=== 1.8.57 (06.10.2025) ===
15 +
16 +* Added a badge counter for Service entries in Operatives Management which will show the total number of entries and turn red if some of them are less than one year old
17 +
18 +=== 1.8.56 (05.10.2025) ===
19 +
20 +* Changed Self-Scheduler so it can be configured to prevent shifts that overlap with already selected shifts and back-to-back shifts at different locations to prevent double-booking and ensuring realistic handovers/travel time
21 +
22 +=== 1.8.55 (29.09.2025) ===
23 +
24 +* Changed Schedule and Self-Scheduler so a change of the Options will not reset the selected calendar view (week/day) any more
25 +
26 +=== 1.8.54 (18.09.2025) ===
27 +
28 +* Bugfix: Having an individual RIC but no configured POCSAG transmitter now does not throw a Javascript error in Operation Status any more
29 +* Bugfix: Sending several individual Telegram / Pager messages in Operation Status in a row now sends several individual messages … and not the same one over and over
30 +
31 +=== 1.8.53 (28.08.2025) ===
32 +
33 +* Changed Column names in PNG Database to better reflect the placeholders for letters
34 +
35 +=== 1.8.52 (19.08.2025) ===
36 +
37 +* 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
38 +* Changed Schedule to enable keyword filtering if a specific Operative is selected
39 +* Bugfix: counter in Schedule counted events over daybreak twice – no not more
40 +* Added Operative duty hours count to counter in Schedule if Operative is selected
41 +
42 +=== 1.8.51 (16.08.2025) ===
43 +
44 +* Added counter in Schedule to calculate the hours shown in the current search / display.
45 +* Added Chinese language options and changed the “unknown” flag from EU to translingual to Operatives Management
46 +
47 +=== 1.8.50 (14.08.2025) ===
48 +
49 +* Added handling of internal location URLs to L.A.S.S.I.E. Bot and Operations Status
50 +* Added Open Location to context menu for Security Operatives
51 +
52 +=== 1.8.49 (11.08.2025) ===
53 +
54 +* Changed the Self-Scheduler to not show the red warning stripes for understaffed shifts if “show unassigned” is selected
55 +
56 +=== 1.8.48 (12.07.2025) ===
57 +
58 +* 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
59 +* Changed FTC client to not display warning message about pager system as it'll nearly never be there anyway
60 +
61 +=== 1.8.47 (05.07.2025) ===
62 +
63 +* Bugfix: added timezone consideration to the Briefings, Items DB and Assets DB modules and the Bigscreen
64 +* Bugfix: Changed maximum field length for floor in Incident Management to 6 and changed form field to reflect maximum length
65 +
66 +=== 1.8.46 (18.06.2025) ===
67 +
68 +* Changed Show Incident to include a better functionality to search for attendees in Involved and Witnesses
69 +
70 +=== 1.8.45 (14.06.2025) ===
71 +
72 +* 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 …)
73 +
74 +=== 1.8.44 (06.06.2025) ===
75 +
76 +* Bugfix: Various smaller spelling corrections
77 +* Changed standard Attendee CSV importer to make it more robust
78 +* Added standard Event (Schedule) CSV importer
79 +* Changed Autofill ODS-C script to accommodate for multiple parallel ODS
80 +
81 +=== 1.8.43 (14.04.2025) ===
82 +
83 +* Bugfix: Correctly displaying error messages for missing Lat/Long in Location Management
84 +* Bugfix: Correctly displaying missing Nationality in Operatives Lists
85 +
86 +=== 1.8.42 (09.04.2025) ===
87 +
88 +* Bugfix: Setting an Operative to INACTIVE now also sets the Access Level “No Access”
89 +
90 +=== 1.8.41 (02.04.2025) ===
91 +
92 +* Added standard CSV importer to Attendee Database for all clients without individual JSON API importer
93 +
94 +=== 1.8.40 (30.03.2025) ===
95 +
96 +* Bugfix: Fixed Permissions for Location Database entries
97 +* Updated Schedule and Self-Scheduler, secured and updated POSTVAR / SQL statements
98 +* Changed Operations Status and enabled COMBIUNITS with no scheduled Operatives
99 +
100 +=== 1.8.39 (20.03.2025) ===
101 +
102 +* Bugfix: Alerting of Dispatch for Status 9 and 5 works correctly again
103 +
104 +=== 1.8.38 (02.03.2025) ===
105 +
106 +* Added a Radio Log function for DMR calls, which can be used with a FurCom Radio Logger
107 +* Bugfix: Fixing many bugs in CSS, surely building in more
108 +
109 +=== 1.8.37 (25.02.2025) ===
110 +
111 +* 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
112 +* 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
113 +
114 +=== 1.8.36 (24.02.2025) ===
115 +
116 +* Bugfix: debugged about a thousand bugs from Operations Status
117 +* 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
118 +* Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable
119 +
120 +=== 1.8.35 (21.02.2025) ===
121 +
122 +* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC
123 +
124 +=== 1.8.34 (20.02.2025) ===
125 +
126 +* Changed the complete JavaScript in Operations Status so the page is about 500% faster
127 +* 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
128 +
129 +=== 1.8.33 (11.02.2025) ===
130 +
131 +* Bugfix: Removed some bugs from Qualification Management and Event Management that occured while adding stuff in Operatives Management
132 +
133 +=== 1.8.32 (31.01.2025) ===
134 +
135 +* Added external alerts to Incident Archive list
136 +* Bugfix: Lost & Found and Item Database now also accepts photos via L.A.S.S.I.E. Bot if they are of rather low resolution.
137 +* Bugfix: Files are now also accepted if the extension of an allowed file type is in UPPER CASE.
138 +
139 +=== 1.8.31 (06.01.2025) ===
140 +
141 +* Changed Briefing module to not have access levels any more, since they necessarily have been "W" for everybody anyways
142 +* Bugfix: Operative Collar IDs of C-Units in Operations Status now are correctly shown if > 999
143 +* Bugfix: Incident Archive table now does not reset scrolling position every 15 seconds any more
144 +* Bugfix: Operatives Duty Stats table (and others) now also scrolls header horizontally, not just content
145 +* Changed location of several files and scripts (backend)
146 +
147 +=== 1.8.30 (27.12.2024) ===
148 +
149 +* Added direct Telegram link to most of the Telegram Handles in Operatives Management and Operatives Lists
150 +* Added an upload function for training certificates to Qualification & Training in Operatives Management; the qualification types First Aider, EMT / Paramedic, 34a, SiA, Firefighter and M.D. will require a certificate to be uploaded upon adding or changing them
151 +* (((
152 +Changed the add and change form for the qualification types First Aider, EMT / Paramedic and Firefighter in Qualification & Training in Operatives Management to account for standard training levels
153 +)))
154 +
155 +=== 1.8.29 (21.12.2024) ===
156 +
157 +* Added autocomplete for the Item Type in Lost & Found Database – it will display the types from all lost or found items, but not the returned ones
158 +* Updated search field in Lost & Found Database to also search inside the Log Comments
159 +* Updated table scrolling behaviour to be more mobile friendly and coherent
160 +
161 +=== 1.8.28 (17.12.2024) ===
162 +
163 +* Added an option to change all duties / events with the same title in the Schedule at the same time
164 +
165 +=== 1.8.27 (16.12.2024) ===
166 +
167 +* Added options to only show one particular status to Lost & Found Database which should make it more easy to display items reported as lost only
168 +* Added a delete option for Lost & Found images (click item to edit, then trash can next to image upload)
169 +* Added Log comment field to Add Lost & Found item
170 +
171 +=== 1.8.26 (16.11.2024) ===
172 +
173 +* Updated ConOps Incident Management, secured and updated POSTVAR / SQL statements, added error codes and error log
174 +* Added most of the recent features from Incident Management to ConOps Incident Management
175 +
176 +=== 1.8.25 (20.10.2024) ===
177 +
178 +* Added a module for changing Item Clearance Levels to System Settings
179 +* Changed the Log Reports printable from Incidents to a more readable format
180 +* Added an Incident Report to print out the whole Incident
181 +
182 +=== 1.8.24 (05.09.2024) ===
183 +
184 +* Added a System Setting to prevent Operatives un-registering from a duty in an otherwise writeable Self-Scheduler
185 +
186 +=== 1.8.23 (30.08.2024) ===
187 +
188 +* Added a FAQ system for L.A.S.S.I.E. Bot  to answer questions in a non-PM Telegram chat with the word "tell" as trigger if directly addressed (e.g.: "@LassieBot tell me about Tuesday"). Answer keywords and answers can be set in System Settings → Bot FAQ Answers. The Telegram chat IDs, which the bot shall answer questions for any convention in, have to be set as comma separated list in System Settings → Settings → Group IDs of L.A.S.S.I.E. Bot FAQ System.
189 +
190 +=== 1.8.22 (29.08.2024) ===
191 +
192 +* Updated Self-Scheduler to include duty stats for the respective Operative
193 +
10 10  === 1.8.21 (27.08.2024) ===
11 11  
12 12  * Updated Schedule to also send information about //what// has changed to scheduled Operatives on change of the content of a schedule item via L.A.S.S.I.E. Bot