Changes for page Changelog
Last modified by Treyfane Dingo on 2025/11/09 22:15
From version 157.1
edited by Treyfane Dingo
on 2025/11/08 02:55
on 2025/11/08 02:55
Change comment:
There is no comment for this version
To version 34.1
edited by Treyfane Dingo
on 2023/11/12 20:34
on 2023/11/12 20:34
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -3,335 +3,6 @@ 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.58 (08.11.2025) === 7 - 8 -* Changed Personal Preferences and General Settings to be way more mobile friendly 9 - 10 -=== 1.8.57 (06.10.2025) === 11 - 12 -* 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 13 - 14 -=== 1.8.56 (05.10.2025) === 15 - 16 -* 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 17 - 18 -=== 1.8.55 (29.09.2025) === 19 - 20 -* Changed Schedule and Self-Scheduler so a change of the Options will not reset the selected calendar view (week/day) any more 21 - 22 -=== 1.8.54 (18.09.2025) === 23 - 24 -* Bugfix: Having an individual RIC but no configured POCSAG transmitter now does not throw a Javascript error in Operation Status any more 25 -* 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 26 - 27 -=== 1.8.53 (28.08.2025) === 28 - 29 -* Changed Column names in PNG Database to better reflect the placeholders for letters 30 - 31 -=== 1.8.52 (19.08.2025) === 32 - 33 -* 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 34 -* Changed Schedule to enable keyword filtering if a specific Operative is selected 35 -* Bugfix: counter in Schedule counted events over daybreak twice – no not more 36 -* Added Operative duty hours count to counter in Schedule if Operative is selected 37 - 38 -=== 1.8.51 (16.08.2025) === 39 - 40 -* Added counter in Schedule to calculate the hours shown in the current search / display. 41 -* Added Chinese language options and changed the “unknown” flag from EU to translingual to Operatives Management 42 - 43 -=== 1.8.50 (14.08.2025) === 44 - 45 -* Added handling of internal location URLs to L.A.S.S.I.E. Bot and Operations Status 46 -* Added Open Location to context menu for Security Operatives 47 - 48 -=== 1.8.49 (11.08.2025) === 49 - 50 -* Changed the Self-Scheduler to not show the red warning stripes for understaffed shifts if “show unassigned” is selected 51 - 52 -=== 1.8.48 (12.07.2025) === 53 - 54 -* 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 55 -* Changed FTC client to not display warning message about pager system as it'll nearly never be there anyway 56 - 57 -=== 1.8.47 (05.07.2025) === 58 - 59 -* Bugfix: added timezone consideration to the Briefings, Items DB and Assets DB modules and the Bigscreen 60 -* Bugfix: Changed maximum field length for floor in Incident Management to 6 and changed form field to reflect maximum length 61 - 62 -=== 1.8.46 (18.06.2025) === 63 - 64 -* Changed Show Incident to include a better functionality to search for attendees in Involved and Witnesses 65 - 66 -=== 1.8.45 (14.06.2025) === 67 - 68 -* 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 …) 69 - 70 -=== 1.8.44 (06.06.2025) === 71 - 72 -* Bugfix: Various smaller spelling corrections 73 -* Changed standard Attendee CSV importer to make it more robust 74 -* Added standard Event (Schedule) CSV importer 75 -* Changed Autofill ODS-C script to accommodate for multiple parallel ODS 76 - 77 -=== 1.8.43 (14.04.2025) === 78 - 79 -* Bugfix: Correctly displaying error messages for missing Lat/Long in Location Management 80 -* Bugfix: Correctly displaying missing Nationality in Operatives Lists 81 - 82 -=== 1.8.42 (09.04.2025) === 83 - 84 -* Bugfix: Setting an Operative to INACTIVE now also sets the Access Level “No Access” 85 - 86 -=== 1.8.41 (02.04.2025) === 87 - 88 -* Added standard CSV importer to Attendee Database for all clients without individual JSON API importer 89 - 90 -=== 1.8.40 (30.03.2025) === 91 - 92 -* Bugfix: Fixed Permissions for Location Database entries 93 -* Updated Schedule and Self-Scheduler, secured and updated POSTVAR / SQL statements 94 -* Changed Operations Status and enabled COMBIUNITS with no scheduled Operatives 95 - 96 -=== 1.8.39 (20.03.2025) === 97 - 98 -* Bugfix: Alerting of Dispatch for Status 9 and 5 works correctly again 99 - 100 -=== 1.8.38 (02.03.2025) === 101 - 102 -* Added a Radio Log function for DMR calls, which can be used with a FurCom Radio Logger 103 -* Bugfix: Fixing many bugs in CSS, surely building in more 104 - 105 -=== 1.8.37 (25.02.2025) === 106 - 107 -* 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 108 -* 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 109 - 110 -=== 1.8.36 (24.02.2025) === 111 - 112 -* Bugfix: debugged about a thousand bugs from Operations Status 113 -* 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 114 -* Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable 115 - 116 -=== 1.8.35 (21.02.2025) === 117 - 118 -* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC 119 - 120 -=== 1.8.34 (20.02.2025) === 121 - 122 -* Changed the complete JavaScript in Operations Status so the page is about 500% faster 123 -* 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 124 - 125 -=== 1.8.33 (11.02.2025) === 126 - 127 -* Bugfix: Removed some bugs from Qualification Management and Event Management that occured while adding stuff in Operatives Management 128 - 129 -=== 1.8.32 (31.01.2025) === 130 - 131 -* Added external alerts to Incident Archive list 132 -* 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. 133 -* Bugfix: Files are now also accepted if the extension of an allowed file type is in UPPER CASE. 134 - 135 -=== 1.8.31 (06.01.2025) === 136 - 137 -* Changed Briefing module to not have access levels any more, since they necessarily have been "W" for everybody anyways 138 -* Bugfix: Operative Collar IDs of C-Units in Operations Status now are correctly shown if > 999 139 -* Bugfix: Incident Archive table now does not reset scrolling position every 15 seconds any more 140 -* Bugfix: Operatives Duty Stats table (and others) now also scrolls header horizontally, not just content 141 -* Changed location of several files and scripts (backend) 142 - 143 -=== 1.8.30 (27.12.2024) === 144 - 145 -* Added direct Telegram link to most of the Telegram Handles in Operatives Management and Operatives Lists 146 -* 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 147 -* ((( 148 -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 149 -))) 150 - 151 -=== 1.8.29 (21.12.2024) === 152 - 153 -* 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 154 -* Updated search field in Lost & Found Database to also search inside the Log Comments 155 -* Updated table scrolling behaviour to be more mobile friendly and coherent 156 - 157 -=== 1.8.28 (17.12.2024) === 158 - 159 -* Added an option to change all duties / events with the same title in the Schedule at the same time 160 - 161 -=== 1.8.27 (16.12.2024) === 162 - 163 -* 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 164 -* Added a delete option for Lost & Found images (click item to edit, then trash can next to image upload) 165 -* Added Log comment field to Add Lost & Found item 166 - 167 -=== 1.8.26 (16.11.2024) === 168 - 169 -* Updated ConOps Incident Management, secured and updated POSTVAR / SQL statements, added error codes and error log 170 -* Added most of the recent features from Incident Management to ConOps Incident Management 171 - 172 -=== 1.8.25 (20.10.2024) === 173 - 174 -* Added a module for changing Item Clearance Levels to System Settings 175 -* Changed the Log Reports printable from Incidents to a more readable format 176 -* Added an Incident Report to print out the whole Incident 177 - 178 -=== 1.8.24 (05.09.2024) === 179 - 180 -* Added a System Setting to prevent Operatives un-registering from a duty in an otherwise writeable Self-Scheduler 181 - 182 -=== 1.8.23 (30.08.2024) === 183 - 184 -* 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. 185 - 186 -=== 1.8.22 (29.08.2024) === 187 - 188 -* Updated Self-Scheduler to include duty stats for the respective Operative 189 - 190 -=== 1.8.21 (27.08.2024) === 191 - 192 -* 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 193 - 194 -=== 1.8.20 (21.08.2024) === 195 - 196 -* Added a direct link to the Schedule of respective Operatives (click on the collar ID) to the Scheduler event popup 197 - 198 -=== 1.8.19 (11.08.2024) === 199 - 200 -* Updated Operatives Duty Stats to make the table more readable. Also added EVAC as shift type. 201 - 202 -=== 1.8.18 (10.08.2024) === 203 - 204 -* Updated the Self-Scheduler so that the buttons are better readable; also got rid of the "Save" button 205 - 206 -=== 1.8.17 (17.06.2024) === 207 - 208 -* Bugfix: All language characters can now be used for searches in Schedule and Self-Scheduler 209 -* 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? 210 -* Added a searchable field for Car License Plate to Attendee DB. This can be imported from a REG DB via API or CSV. 211 - 212 -=== 1.8.16 (14.05.2024) === 213 - 214 -* Bugfix: DOB can now again be initially set by users with write access to the Operatives Database 215 -* Bugfix: Convention Rank can now be set again by users with write access to the Operatives Database 216 - 217 -=== 1.8.15 (29.04.2024) === 218 - 219 -* 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 220 -* Removed height / weight from Operative Database (unneeded PII) 221 -* Added the ability to change the Nickname for the Operatives in Personal Preferences 222 - 223 -=== 1.8.14 (19.04.2024) === 224 - 225 -* Updated Operatives Management so users with write access to the Operatives Database can no longer set access permissions that exceed their own 226 -* Removed the Messaging Module as it was not used any more 227 -* Updated Operatives Management, secured and updated POSTVAR / SQL statements, added error codes and error log 228 -* Updated PNG Management, secured and updated POSTVAR / SQL statements, added error codes and error log 229 - 230 -=== 1.8.13 (16.04.2024) === 231 - 232 -* Updated ARO Management, secured and updated POSTVAR / SQL statements, added error codes and error log 233 -* Updated Item Type Management, secured and updated POSTVAR / SQL statements, added error codes and error log 234 -* Bugfix: Items in the Item DB can now be edited if the item type that has been originally used was since deleted 235 - 236 -=== 1.8.12 (18.03.2024) === 237 - 238 -* 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 239 - 240 -=== 1.8.11 (17.03.2024) === 241 - 242 -* Updated L.A.S.S.I.E. Bot to include a reset password function 243 -* Bugfix: Hitting [Enter] now properly closes the dialogue window when creating new API Keys in API Keys Management 244 - 245 -=== 1.8.10 (14.03.2024) === 246 - 247 -* 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 248 - 249 -=== 1.8.9 (10.03.2024) === 250 - 251 -* 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 252 - 253 -=== 1.8.8 (08.03.2024) === 254 - 255 -* Bugfix: ARO was not correctly displayed in Show Incident if incident was not ongoing 256 -* Bugfix: Incident Opening Time was incorrectly (re-)set on incident update under certain circumstances 257 -* Bugfix: Some read-only input fields were not correctly displayed as read-only 258 - 259 -=== 1.8.7 (01.03.2024) === 260 - 261 -* 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 262 -* Bugfix: change of Personal Asset now does not mess up the dialogue window any more 263 - 264 -=== 1.8.6 (25.02.2024) === 265 - 266 -* Updated Show Incident to make Log Comments individually printable 267 -* 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 268 -* Updated Show Incident to make Log Comments flaggable as //Medic Log (Confidential)// by the owner or Admin after saving 269 - 270 -=== 1.8.5 (04.02.2024) === 271 - 272 -* Updated Operative Collar ID / nickname in top right corner to directly link to Personal Preferences on click 273 - 274 -=== 1.8.4 (15.01.2024) === 275 - 276 -* Updated Show Incident to display Medical / File log comments in another colour 277 -* 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 278 - 279 -=== 1.8.3 (26.12.2023) === 280 - 281 -* Updated Lists in Operatives Management to differentiate between the UnitTypes in regards to inactive Operatives 282 -* Added button in Operatives Management / Lists to copy respective Wiki List on click 283 -* Added information about duration of inactivity to inactive Operatives in Operatives Management Lists 284 - 285 -=== 1.8.2 (01.12.2023) === 286 - 287 -* Updated Briefings to not show briefings sent by the Operative themselves per default and added a checkbox to also show those briefings 288 -* Updated Briefings to show sent briefings in green and unread briefings in orange 289 - 290 -=== 1.8.1 (29.11.2023) === 291 - 292 -* Updated Schedule to show the currently running half hour as slight grey overlay 293 -* Updated Briefing Management, secured and updated POSTVAR / SQL statements, added error codes and error log 294 -* Updated Briefing Management forms and mobile layout to be more mobile friendly 295 - 296 -=== 1.8.0 (25.11.2023) === 297 - 298 -* Updated L.A.S.S.I.E. CSS, modules and includes ... got rid of very, very much legacy code there. And tables. Many tables. 299 -* Bugfix: the Operations Status now again shows warnings about stale incidents 300 -* Bugfix: some minor corrections in the light theme 301 -* Updated the complete Incident Management module, secured and updated POSTVAR / SQL statements, added error codes and error log 302 -* Updated all Incident Management module forms and mobile layouts to be more mobile friendly 303 -* Updated New Incident / Show Incident to not save 'brief' Descriptions, Locations or Reported by fields over 99 characters and instead show an error message 304 - 305 -=== 1.7.97 (23.11.2023) === 306 - 307 -* Updated Access Review, secured and updated POSTVAR / SQL statements, added error codes and error log 308 -* Updated Access Review forms and mobile layout to be more mobile friendly 309 -* Bugfix: Multiple image uploads in Operative Management and Personal Preferences should not throw the cropping function off tracks any more 310 - 311 -=== 1.7.96 (21.11.2023) === 312 - 313 -* Bugfix: "show my shifts" in Self-Scheduler now is working properly again 314 -* Bugfix: Logfile in Lost & Found Database item is now always displayed 315 -* Changed Menu completely and added Sub-Menu items 316 -* Removed the menu tabs for more mobile friendly user experience 317 -* Added page name under convention name 318 -* Moved Schedule Stats to Operatives Duty Stats for clarification of content 319 -* Added Planned Duty Stats to graphically compare duties planned vs. operatives scheduled per timeslot 320 - 321 -=== 1.7.95 (19.11.2023) === 322 - 323 -* Removed 'Delete' function from ARO Management to maintain audit trail / database integrity 324 -* Added 'Deactivate' function to ARO Management 325 -* Updated ARO Management to not show deactivated ARO items per default and added a checkbox to also show deactivated ARO items 326 -* Updated Unit Types Management, secured and updated POSTVAR / SQL statements, added error codes and error log 327 -* Updated Unit Types Management forms and mobile layout to be more mobile friendly 328 -* Bugfix: Unit Types Management no longer able to delete Unit Type that is in use by an ARO item 329 - 330 -=== 1.7.94 (14.11.2023) === 331 - 332 -* Updated PNG Forms, added multiple organisational %placeholder% 333 -* Updated Convention Settings to show basic Convention Information which can only be changed by L.A.S.S.I.E. admin but be used as %placeholder% in PNG Forms 334 - 335 335 === 1.7.93 (12.11.2023) === 336 336 337 337 * Updated Event Management, secured and updated POSTVAR / SQL statements, added error codes and error log