Skip to Content

Changes for page Changelog

Last modified by Treyfane Dingo on 2025/11/09 22:15
From version 156.1
edited by Treyfane Dingo
on 2025/11/07 23:43
Change comment: There is no comment for this version
To version 117.5
edited by Treyfane Dingo
on 2025/01/06 12:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,142 +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.58 (08.11.2025) ===
6 +=== 1.8.31 (~-~-) ===
7 7  
8 -* Changed Personal Preferences 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 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)
9 +* Bugfix: Incident Archive table now does not reset scrolli
142 142  
143 143  === 1.8.30 (27.12.2024) ===
144 144