Changes for page Changelog

Summary

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

Details

Page properties

Content

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