Changes for page Changelog

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -3,6 +3,70 @@
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: Having an individual RIC but no configured POCSAG transmitter now does not throw a Javascript error in Operation Status any more
	9	+* 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
	10	+
	11	+=== 1.8.53 (28.08.2025) ===
	12	+
	13	+* Changed Column names in PNG Database to better reflect the placeholders for letters
	14	+
	15	+=== 1.8.52 (19.08.2025) ===
	16	+
	17	+* 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
	18	+* Changed Schedule to enable keyword filtering if a specific Operative is selected
	19	+* Bugfix: counter in Schedule counted events over daybreak twice – no not more
	20	+* Added Operative duty hours count to counter in Schedule if Operative is selected
	21	+
	22	+=== 1.8.51 (16.08.2025) ===
	23	+
	24	+* Added counter in Schedule to calculate the hours shown in the current search / display.
	25	+* Added Chinese language options and changed the “unknown” flag from EU to translingual to Operatives Management
	26	+
	27	+=== 1.8.50 (14.08.2025) ===
	28	+
	29	+* Added handling of internal location URLs to L.A.S.S.I.E. Bot and Operations Status
	30	+* Added Open Location to context menu for Security Operatives
	31	+
	32	+=== 1.8.49 (11.08.2025) ===
	33	+
	34	+* Changed the Self-Scheduler to not show the red warning stripes for understaffed shifts if “show unassigned” is selected
	35	+
	36	+=== 1.8.48 (12.07.2025) ===
	37	+
	38	+* 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
	39	+* Changed FTC client to not display warning message about pager system as it'll nearly never be there anyway
	40	+
	41	+=== 1.8.47 (05.07.2025) ===
	42	+
	43	+* Bugfix: added timezone consideration to the Briefings, Items DB and Assets DB modules and the Bigscreen
	44	+* Bugfix: Changed maximum field length for floor in Incident Management to 6 and changed form field to reflect maximum length
	45	+
	46	+=== 1.8.46 (18.06.2025) ===
	47	+
	48	+* Changed Show Incident to include a better functionality to search for attendees in Involved and Witnesses
	49	+
	50	+=== 1.8.45 (14.06.2025) ===
	51	+
	52	+* 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 …)
	53	+
	54	+=== 1.8.44 (06.06.2025) ===
	55	+
	56	+* Bugfix: Various smaller spelling corrections
	57	+* Changed standard Attendee CSV importer to make it more robust
	58	+* Added standard Event (Schedule) CSV importer
	59	+* Changed Autofill ODS-C script to accommodate for multiple parallel ODS
	60	+
	61	+=== 1.8.43 (14.04.2025) ===
	62	+
	63	+* Bugfix: Correctly displaying error messages for missing Lat/Long in Location Management
	64	+* Bugfix: Correctly displaying missing Nationality in Operatives Lists
	65	+
	66	+=== 1.8.42 (09.04.2025) ===
	67	+
	68	+* Bugfix: Setting an Operative to INACTIVE now also sets the Access Level “No Access”
	69	+
6	6	=== 1.8.41 (02.04.2025) ===
7	7
8	8	* Added standard CSV importer to Attendee Database for all clients without individual JSON API importer
...	...	@@ -24,23 +24,23 @@
24	24
25	25	=== 1.8.37 (25.02.2025) ===
26	26
27		-* 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.
28		-* 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.
	91	+* 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
	92	+* 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
29	29
30	30	=== 1.8.36 (24.02.2025) ===
31	31
32		-* Bugfix: debugged about a thousand bugs from Operations Status.
33		-* 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.
34		-* Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable.
	96	+* Bugfix: debugged about a thousand bugs from Operations Status
	97	+* 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
	98	+* Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable
35	35
36	36	=== 1.8.35 (21.02.2025) ===
37	37
38		-* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC.
	102	+* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC
39	39
40	40	=== 1.8.34 (20.02.2025) ===
41	41
42		-* Changed the complete JavaScript in Operations Status so the page is about 500% faster.
43		-* 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.
	106	+* Changed the complete JavaScript in Operations Status so the page is about 500% faster
	107	+* 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
44	44
45	45	=== 1.8.33 (11.02.2025) ===
46	46