Skip to Content

Changes for page Changelog

Last modified by Treyfane Dingo on 2025/08/28 16:26
From version 144.1
edited by Treyfane Dingo
on 2025/08/14 14:50
Change comment: There is no comment for this version
To version 66.1
edited by Treyfane Dingo
on 2024/01/15 22:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,241 +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.50 (14.08.2025) ===
7 -
8 -* Added handling of internal location URLs to L.A.S.S.I.E. Bot and Operations Status
9 -* Added Open Location to context menu for Security Operatives
10 -
11 -=== 1.8.49 (11.08.2025) ===
12 -
13 -* Changed the Self-Scheduler to not show the red warning stripes for understaffed shifts if “show unassigned” is selected
14 -
15 -=== 1.8.48 (12.07.2025) ===
16 -
17 -* 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
18 -* Changed FTC client to not display warning message about pager system as it'll nearly never be there anyway
19 -
20 -=== 1.8.47 (05.07.2025) ===
21 -
22 -* Bugfix: added timezone consideration to the Briefings, Items DB and Assets DB modules and the Bigscreen
23 -* Bugfix: Changed maximum field length for floor in Incident Management to 6 and changed form field to reflect maximum length
24 -
25 -=== 1.8.46 (18.06.2025) ===
26 -
27 -* Changed Show Incident to include a better functionality to search for attendees in Involved and Witnesses
28 -
29 -=== 1.8.45 (14.06.2025) ===
30 -
31 -* 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 …)
32 -
33 -=== 1.8.44 (06.06.2025) ===
34 -
35 -* Bugfix: Various smaller spelling corrections
36 -* Changed standard Attendee CSV importer to make it more robust
37 -* Added standard Event (Schedule) CSV importer
38 -* Changed Autofill ODS-C script to accommodate for multiple parallel ODS
39 -
40 -=== 1.8.43 (14.04.2025) ===
41 -
42 -* Bugfix: Correctly displaying error messages for missing Lat/Long in Location Management
43 -* Bugfix: Correctly displaying missing Nationality in Operatives Lists
44 -
45 -=== 1.8.42 (09.04.2025) ===
46 -
47 -* Bugfix: Setting an Operative to INACTIVE now also sets the Access Level “No Access”
48 -
49 -=== 1.8.41 (02.04.2025) ===
50 -
51 -* Added standard CSV importer to Attendee Database for all clients without individual JSON API importer
52 -
53 -=== 1.8.40 (30.03.2025) ===
54 -
55 -* Bugfix: Fixed Permissions for Location Database entries
56 -* Updated Schedule and Self-Scheduler, secured and updated POSTVAR / SQL statements
57 -* Changed Operations Status and enabled COMBIUNITS with no scheduled Operatives
58 -
59 -=== 1.8.39 (20.03.2025) ===
60 -
61 -* Bugfix: Alerting of Dispatch for Status 9 and 5 works correctly again
62 -
63 -=== 1.8.38 (02.03.2025) ===
64 -
65 -* Added a Radio Log function for DMR calls, which can be used with a FurCom Radio Logger
66 -* Bugfix: Fixing many bugs in CSS, surely building in more
67 -
68 -=== 1.8.37 (25.02.2025) ===
69 -
70 -* 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
71 -* 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
72 -
73 -=== 1.8.36 (24.02.2025) ===
74 -
75 -* Bugfix: debugged about a thousand bugs from Operations Status
76 -* 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
77 -* Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable
78 -
79 -=== 1.8.35 (21.02.2025) ===
80 -
81 -* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC
82 -
83 -=== 1.8.34 (20.02.2025) ===
84 -
85 -* Changed the complete JavaScript in Operations Status so the page is about 500% faster
86 -* 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
87 -
88 -=== 1.8.33 (11.02.2025) ===
89 -
90 -* Bugfix: Removed some bugs from Qualification Management and Event Management that occured while adding stuff in Operatives Management
91 -
92 -=== 1.8.32 (31.01.2025) ===
93 -
94 -* Added external alerts to Incident Archive list
95 -* 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.
96 -* Bugfix: Files are now also accepted if the extension of an allowed file type is in UPPER CASE.
97 -
98 -=== 1.8.31 (06.01.2025) ===
99 -
100 -* Changed Briefing module to not have access levels any more, since they necessarily have been "W" for everybody anyways
101 -* Bugfix: Operative Collar IDs of C-Units in Operations Status now are correctly shown if > 999
102 -* Bugfix: Incident Archive table now does not reset scrolling position every 15 seconds any more
103 -* Bugfix: Operatives Duty Stats table (and others) now also scrolls header horizontally, not just content
104 -* Changed location of several files and scripts (backend)
105 -
106 -=== 1.8.30 (27.12.2024) ===
107 -
108 -* Added direct Telegram link to most of the Telegram Handles in Operatives Management and Operatives Lists
109 -* 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
110 -* (((
111 -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
112 -)))
113 -
114 -=== 1.8.29 (21.12.2024) ===
115 -
116 -* 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
117 -* Updated search field in Lost & Found Database to also search inside the Log Comments
118 -* Updated table scrolling behaviour to be more mobile friendly and coherent
119 -
120 -=== 1.8.28 (17.12.2024) ===
121 -
122 -* Added an option to change all duties / events with the same title in the Schedule at the same time
123 -
124 -=== 1.8.27 (16.12.2024) ===
125 -
126 -* 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
127 -* Added a delete option for Lost & Found images (click item to edit, then trash can next to image upload)
128 -* Added Log comment field to Add Lost & Found item
129 -
130 -=== 1.8.26 (16.11.2024) ===
131 -
132 -* Updated ConOps Incident Management, secured and updated POSTVAR / SQL statements, added error codes and error log
133 -* Added most of the recent features from Incident Management to ConOps Incident Management
134 -
135 -=== 1.8.25 (20.10.2024) ===
136 -
137 -* Added a module for changing Item Clearance Levels to System Settings
138 -* Changed the Log Reports printable from Incidents to a more readable format
139 -* Added an Incident Report to print out the whole Incident
140 -
141 -=== 1.8.24 (05.09.2024) ===
142 -
143 -* Added a System Setting to prevent Operatives un-registering from a duty in an otherwise writeable Self-Scheduler
144 -
145 -=== 1.8.23 (30.08.2024) ===
146 -
147 -* 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.
148 -
149 -=== 1.8.22 (29.08.2024) ===
150 -
151 -* Updated Self-Scheduler to include duty stats for the respective Operative
152 -
153 -=== 1.8.21 (27.08.2024) ===
154 -
155 -* 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
156 -
157 -=== 1.8.20 (21.08.2024) ===
158 -
159 -* Added a direct link to the Schedule of respective Operatives (click on the collar ID) to the Scheduler event popup
160 -
161 -=== 1.8.19 (11.08.2024) ===
162 -
163 -* Updated Operatives Duty Stats to make the table more readable. Also added EVAC as shift type.
164 -
165 -=== 1.8.18 (10.08.2024) ===
166 -
167 -* Updated the Self-Scheduler so that the buttons are better readable; also got rid of the "Save" button
168 -
169 -=== 1.8.17 (17.06.2024) ===
170 -
171 -* Bugfix: All language characters can now be used for searches in Schedule and Self-Scheduler
172 -* Bugfix: Special unicode language characters like the ꝥ which is a þat (þ) wið a stroke, and dating back to Old Engliſh, can now also be used in Schedule titles. One can alſo uſe emojis 😸 now ... why are you torturing me so much?
173 -* Added a searchable field for Car License Plate to Attendee DB. This can be imported from a REG DB via API or CSV.
174 -
175 -=== 1.8.16 (14.05.2024) ===
176 -
177 -* Bugfix: DOB can now again be initially set by users with write access to the Operatives Database
178 -* Bugfix: Convention Rank can now be set again by users with write access to the Operatives Database
179 -
180 -=== 1.8.15 (29.04.2024) ===
181 -
182 -* Updated Operatives Management so users with write access to the Operatives Database can no longer change Operative PII for Operatives once it is initially set; Operative PII has to be changed by the Operative themselves
183 -* Removed height / weight from Operative Database (unneeded PII)
184 -* Added the ability to change the Nickname for the Operatives in Personal Preferences
185 -
186 -=== 1.8.14 (19.04.2024) ===
187 -
188 -* Updated Operatives Management so users with write access to the Operatives Database can no longer set access permissions that exceed their own
189 -* Removed the Messaging Module as it was not used any more
190 -* Updated Operatives Management, secured and updated POSTVAR / SQL statements, added error codes and error log
191 -* Updated PNG Management, secured and updated POSTVAR / SQL statements, added error codes and error log
192 -
193 -=== 1.8.13 (16.04.2024) ===
194 -
195 -* Updated ARO Management, secured and updated POSTVAR / SQL statements, added error codes and error log
196 -* Updated Item Type Management, secured and updated POSTVAR / SQL statements, added error codes and error log
197 -* Bugfix: Items in the Item DB can now be edited if the item type that has been originally used was since deleted
198 -
199 -=== 1.8.12 (18.03.2024) ===
200 -
201 -* Updated Schedule to be able to send an information to scheduled Operatives on change of the content of a schedule item on request via L.A.S.S.I.E. Bot and to auto-send an information via L.A.S.S.I.E. Bot in case a schedule item is moved or deleted
202 -
203 -=== 1.8.11 (17.03.2024) ===
204 -
205 -* Updated L.A.S.S.I.E. Bot to include a reset password function
206 -* Bugfix: Hitting [Enter] now properly closes the dialogue window when creating new API Keys in API Keys Management
207 -
208 -=== 1.8.10 (14.03.2024) ===
209 -
210 -* Bugfix: Changing more than one access level in Operatives Management to a non-standard access level did not work correctly; it now does and even so without having to F2/save and reload the page
211 -
212 -=== 1.8.9 (10.03.2024) ===
213 -
214 -* Updated Operations Status to better reflect non-ongoing incidents since the fire mini-icon was not visible enough; non-ongoing incidents will now be displayed without a frame around the incident information instead
215 -
216 -=== 1.8.8 (08.03.2024) ===
217 -
218 -* Bugfix: ARO was not correctly displayed in Show Incident if incident was not ongoing
219 -* Bugfix: Incident Opening Time was incorrectly (re-)set on incident update under certain circumstances
220 -* Bugfix: Some read-only input fields were not correctly displayed as read-only
221 -
222 -=== 1.8.7 (01.03.2024) ===
223 -
224 -* Bugfix: tables in Lost & Found Database, Personal Assets Database and Items Database now refreshes on the currently selected page rather than to the first page
225 -* Bugfix: change of Personal Asset now does not mess up the dialogue window any more
226 -
227 -=== 1.8.6 (25.02.2024) ===
228 -
229 -* Updated Show Incident to make Log Comments individually printable
230 -* Updated Show Incident to make Log Comments deletable by the owner or Admin; deleted Log Comments will still be shown to the original owner of the Log Comment and Admins but not to other operatives
231 -* Updated Show Incident to make Log Comments flaggable as //Medic Log (Confidential)// by the owner or Admin after saving
232 -
233 -=== 1.8.5 (04.02.2024) ===
234 -
235 -* Updated Operative Collar ID / nickname in top right corner to directly link to Personal Preferences on click
236 -
237 237  === 1.8.4 (15.01.2024) ===
238 238  
239 239  * Updated Show Incident to display Medical / File log comments in another colour
240 -* Updated Show Incident to add a standard Patient Report text to Log Comment if //Medic Log (Confidential)// is selected upon an empty Log Comment field
9 +* Updated Show Incident to add a standard Patient Report text to Log Comment if Medic Log is selected upon an empty Log Comment field
241 241  
242 242  === 1.8.3 (26.12.2023) ===
243 243