Changes for page Changelog

Summary

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

Details

Page properties

Content

...	...	@@ -3,20 +3,120 @@
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.35 (21.02.2025) ===
	6	+=== 1.8.57 (06.10.2025) ===
7	7
8		-* Bugfix: debugged about a thousand bugs from Operations Status.
9		-* 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.
10		-* Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable.
	8	+* 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
11	11
	10	+=== 1.8.56 (05.10.2025) ===
	11	+
	12	+* 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
	13	+
	14	+=== 1.8.55 (29.09.2025) ===
	15	+
	16	+* Changed Schedule and Self-Scheduler so a change of the Options will not reset the selected calendar view (week/day) any more
	17	+
	18	+=== 1.8.54 (18.09.2025) ===
	19	+
	20	+* Bugfix: Having an individual RIC but no configured POCSAG transmitter now does not throw a Javascript error in Operation Status any more
	21	+* 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
	22	+
	23	+=== 1.8.53 (28.08.2025) ===
	24	+
	25	+* Changed Column names in PNG Database to better reflect the placeholders for letters
	26	+
	27	+=== 1.8.52 (19.08.2025) ===
	28	+
	29	+* 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
	30	+* Changed Schedule to enable keyword filtering if a specific Operative is selected
	31	+* Bugfix: counter in Schedule counted events over daybreak twice – no not more
	32	+* Added Operative duty hours count to counter in Schedule if Operative is selected
	33	+
	34	+=== 1.8.51 (16.08.2025) ===
	35	+
	36	+* Added counter in Schedule to calculate the hours shown in the current search / display.
	37	+* Added Chinese language options and changed the “unknown” flag from EU to translingual to Operatives Management
	38	+
	39	+=== 1.8.50 (14.08.2025) ===
	40	+
	41	+* Added handling of internal location URLs to L.A.S.S.I.E. Bot and Operations Status
	42	+* Added Open Location to context menu for Security Operatives
	43	+
	44	+=== 1.8.49 (11.08.2025) ===
	45	+
	46	+* Changed the Self-Scheduler to not show the red warning stripes for understaffed shifts if “show unassigned” is selected
	47	+
	48	+=== 1.8.48 (12.07.2025) ===
	49	+
	50	+* 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
	51	+* Changed FTC client to not display warning message about pager system as it'll nearly never be there anyway
	52	+
	53	+=== 1.8.47 (05.07.2025) ===
	54	+
	55	+* Bugfix: added timezone consideration to the Briefings, Items DB and Assets DB modules and the Bigscreen
	56	+* Bugfix: Changed maximum field length for floor in Incident Management to 6 and changed form field to reflect maximum length
	57	+
	58	+=== 1.8.46 (18.06.2025) ===
	59	+
	60	+* Changed Show Incident to include a better functionality to search for attendees in Involved and Witnesses
	61	+
	62	+=== 1.8.45 (14.06.2025) ===
	63	+
	64	+* 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 …)
	65	+
	66	+=== 1.8.44 (06.06.2025) ===
	67	+
	68	+* Bugfix: Various smaller spelling corrections
	69	+* Changed standard Attendee CSV importer to make it more robust
	70	+* Added standard Event (Schedule) CSV importer
	71	+* Changed Autofill ODS-C script to accommodate for multiple parallel ODS
	72	+
	73	+=== 1.8.43 (14.04.2025) ===
	74	+
	75	+* Bugfix: Correctly displaying error messages for missing Lat/Long in Location Management
	76	+* Bugfix: Correctly displaying missing Nationality in Operatives Lists
	77	+
	78	+=== 1.8.42 (09.04.2025) ===
	79	+
	80	+* Bugfix: Setting an Operative to INACTIVE now also sets the Access Level “No Access”
	81	+
	82	+=== 1.8.41 (02.04.2025) ===
	83	+
	84	+* Added standard CSV importer to Attendee Database for all clients without individual JSON API importer
	85	+
	86	+=== 1.8.40 (30.03.2025) ===
	87	+
	88	+* Bugfix: Fixed Permissions for Location Database entries
	89	+* Updated Schedule and Self-Scheduler, secured and updated POSTVAR / SQL statements
	90	+* Changed Operations Status and enabled COMBIUNITS with no scheduled Operatives
	91	+
	92	+=== 1.8.39 (20.03.2025) ===
	93	+
	94	+* Bugfix: Alerting of Dispatch for Status 9 and 5 works correctly again
	95	+
	96	+=== 1.8.38 (02.03.2025) ===
	97	+
	98	+* Added a Radio Log function for DMR calls, which can be used with a FurCom Radio Logger
	99	+* Bugfix: Fixing many bugs in CSS, surely building in more
	100	+
	101	+=== 1.8.37 (25.02.2025) ===
	102	+
	103	+* 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
	104	+* 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
	105	+
	106	+=== 1.8.36 (24.02.2025) ===
	107	+
	108	+* Bugfix: debugged about a thousand bugs from Operations Status
	109	+* 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
	110	+* Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable
	111	+
12	12	=== 1.8.35 (21.02.2025) ===
13	13
14		-* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC.
	114	+* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC
15	15
16	16	=== 1.8.34 (20.02.2025) ===
17	17
18		-* Changed the complete JavaScript in Operations Status so the page is about 500% faster.
19		-* 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.
	118	+* Changed the complete JavaScript in Operations Status so the page is about 500% faster
	119	+* 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
20	20
21	21	=== 1.8.33 (11.02.2025) ===
22	22