Changes for page Changelog

Summary

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

Details

Page properties

Content

...	...	@@ -3,6 +3,237 @@
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.56 (05.10.2025) ===
	7	+
	8	+* Changed Self-Scheduler so shifts that overlap with already selected shifts and back-to-back shifts at different locations are hidden to prevent double-booking and ensuring realistic handovers/travel time
	9	+
	10	+=== 1.8.55 (29.09.2025) ===
	11	+
	12	+* Changed Schedule and Self-Scheduler so a change of the Options will not reset the selected calendar view (week/day) any more
	13	+
	14	+=== 1.8.54 (18.09.2025) ===
	15	+
	16	+* Bugfix: Having an individual RIC but no configured POCSAG transmitter now does not throw a Javascript error in Operation Status any more
	17	+* 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
	18	+
	19	+=== 1.8.53 (28.08.2025) ===
	20	+
	21	+* Changed Column names in PNG Database to better reflect the placeholders for letters
	22	+
	23	+=== 1.8.52 (19.08.2025) ===
	24	+
	25	+* 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
	26	+* Changed Schedule to enable keyword filtering if a specific Operative is selected
	27	+* Bugfix: counter in Schedule counted events over daybreak twice – no not more
	28	+* Added Operative duty hours count to counter in Schedule if Operative is selected
	29	+
	30	+=== 1.8.51 (16.08.2025) ===
	31	+
	32	+* Added counter in Schedule to calculate the hours shown in the current search / display.
	33	+* Added Chinese language options and changed the “unknown” flag from EU to translingual to Operatives Management
	34	+
	35	+=== 1.8.50 (14.08.2025) ===
	36	+
	37	+* Added handling of internal location URLs to L.A.S.S.I.E. Bot and Operations Status
	38	+* Added Open Location to context menu for Security Operatives
	39	+
	40	+=== 1.8.49 (11.08.2025) ===
	41	+
	42	+* Changed the Self-Scheduler to not show the red warning stripes for understaffed shifts if “show unassigned” is selected
	43	+
	44	+=== 1.8.48 (12.07.2025) ===
	45	+
	46	+* 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
	47	+* Changed FTC client to not display warning message about pager system as it'll nearly never be there anyway
	48	+
	49	+=== 1.8.47 (05.07.2025) ===
	50	+
	51	+* Bugfix: added timezone consideration to the Briefings, Items DB and Assets DB modules and the Bigscreen
	52	+* Bugfix: Changed maximum field length for floor in Incident Management to 6 and changed form field to reflect maximum length
	53	+
	54	+=== 1.8.46 (18.06.2025) ===
	55	+
	56	+* Changed Show Incident to include a better functionality to search for attendees in Involved and Witnesses
	57	+
	58	+=== 1.8.45 (14.06.2025) ===
	59	+
	60	+* 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 …)
	61	+
	62	+=== 1.8.44 (06.06.2025) ===
	63	+
	64	+* Bugfix: Various smaller spelling corrections
	65	+* Changed standard Attendee CSV importer to make it more robust
	66	+* Added standard Event (Schedule) CSV importer
	67	+* Changed Autofill ODS-C script to accommodate for multiple parallel ODS
	68	+
	69	+=== 1.8.43 (14.04.2025) ===
	70	+
	71	+* Bugfix: Correctly displaying error messages for missing Lat/Long in Location Management
	72	+* Bugfix: Correctly displaying missing Nationality in Operatives Lists
	73	+
	74	+=== 1.8.42 (09.04.2025) ===
	75	+
	76	+* Bugfix: Setting an Operative to INACTIVE now also sets the Access Level “No Access”
	77	+
	78	+=== 1.8.41 (02.04.2025) ===
	79	+
	80	+* Added standard CSV importer to Attendee Database for all clients without individual JSON API importer
	81	+
	82	+=== 1.8.40 (30.03.2025) ===
	83	+
	84	+* Bugfix: Fixed Permissions for Location Database entries
	85	+* Updated Schedule and Self-Scheduler, secured and updated POSTVAR / SQL statements
	86	+* Changed Operations Status and enabled COMBIUNITS with no scheduled Operatives
	87	+
	88	+=== 1.8.39 (20.03.2025) ===
	89	+
	90	+* Bugfix: Alerting of Dispatch for Status 9 and 5 works correctly again
	91	+
	92	+=== 1.8.38 (02.03.2025) ===
	93	+
	94	+* Added a Radio Log function for DMR calls, which can be used with a FurCom Radio Logger
	95	+* Bugfix: Fixing many bugs in CSS, surely building in more
	96	+
	97	+=== 1.8.37 (25.02.2025) ===
	98	+
	99	+* 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
	100	+* 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
	101	+
	102	+=== 1.8.36 (24.02.2025) ===
	103	+
	104	+* Bugfix: debugged about a thousand bugs from Operations Status
	105	+* 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
	106	+* Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable
	107	+
	108	+=== 1.8.35 (21.02.2025) ===
	109	+
	110	+* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC
	111	+
	112	+=== 1.8.34 (20.02.2025) ===
	113	+
	114	+* Changed the complete JavaScript in Operations Status so the page is about 500% faster
	115	+* 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
	116	+
	117	+=== 1.8.33 (11.02.2025) ===
	118	+
	119	+* Bugfix: Removed some bugs from Qualification Management and Event Management that occured while adding stuff in Operatives Management
	120	+
	121	+=== 1.8.32 (31.01.2025) ===
	122	+
	123	+* Added external alerts to Incident Archive list
	124	+* 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.
	125	+* Bugfix: Files are now also accepted if the extension of an allowed file type is in UPPER CASE.
	126	+
	127	+=== 1.8.31 (06.01.2025) ===
	128	+
	129	+* Changed Briefing module to not have access levels any more, since they necessarily have been "W" for everybody anyways
	130	+* Bugfix: Operative Collar IDs of C-Units in Operations Status now are correctly shown if > 999
	131	+* Bugfix: Incident Archive table now does not reset scrolling position every 15 seconds any more
	132	+* Bugfix: Operatives Duty Stats table (and others) now also scrolls header horizontally, not just content
	133	+* Changed location of several files and scripts (backend)
	134	+
	135	+=== 1.8.30 (27.12.2024) ===
	136	+
	137	+* Added direct Telegram link to most of the Telegram Handles in Operatives Management and Operatives Lists
	138	+* 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
	139	+* (((
	140	+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
	141	+)))
	142	+
	143	+=== 1.8.29 (21.12.2024) ===
	144	+
	145	+* 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
	146	+* Updated search field in Lost & Found Database to also search inside the Log Comments
	147	+* Updated table scrolling behaviour to be more mobile friendly and coherent
	148	+
	149	+=== 1.8.28 (17.12.2024) ===
	150	+
	151	+* Added an option to change all duties / events with the same title in the Schedule at the same time
	152	+
	153	+=== 1.8.27 (16.12.2024) ===
	154	+
	155	+* 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
	156	+* Added a delete option for Lost & Found images (click item to edit, then trash can next to image upload)
	157	+* Added Log comment field to Add Lost & Found item
	158	+
	159	+=== 1.8.26 (16.11.2024) ===
	160	+
	161	+* Updated ConOps Incident Management, secured and updated POSTVAR / SQL statements, added error codes and error log
	162	+* Added most of the recent features from Incident Management to ConOps Incident Management
	163	+
	164	+=== 1.8.25 (20.10.2024) ===
	165	+
	166	+* Added a module for changing Item Clearance Levels to System Settings
	167	+* Changed the Log Reports printable from Incidents to a more readable format
	168	+* Added an Incident Report to print out the whole Incident
	169	+
	170	+=== 1.8.24 (05.09.2024) ===
	171	+
	172	+* Added a System Setting to prevent Operatives un-registering from a duty in an otherwise writeable Self-Scheduler
	173	+
	174	+=== 1.8.23 (30.08.2024) ===
	175	+
	176	+* 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.
	177	+
	178	+=== 1.8.22 (29.08.2024) ===
	179	+
	180	+* Updated Self-Scheduler to include duty stats for the respective Operative
	181	+
	182	+=== 1.8.21 (27.08.2024) ===
	183	+
	184	+* 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
	185	+
	186	+=== 1.8.20 (21.08.2024) ===
	187	+
	188	+* Added a direct link to the Schedule of respective Operatives (click on the collar ID) to the Scheduler event popup
	189	+
	190	+=== 1.8.19 (11.08.2024) ===
	191	+
	192	+* Updated Operatives Duty Stats to make the table more readable. Also added EVAC as shift type.
	193	+
	194	+=== 1.8.18 (10.08.2024) ===
	195	+
	196	+* Updated the Self-Scheduler so that the buttons are better readable; also got rid of the "Save" button
	197	+
	198	+=== 1.8.17 (17.06.2024) ===
	199	+
	200	+* Bugfix: All language characters can now be used for searches in Schedule and Self-Scheduler
	201	+* 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?
	202	+* Added a searchable field for Car License Plate to Attendee DB. This can be imported from a REG DB via API or CSV.
	203	+
	204	+=== 1.8.16 (14.05.2024) ===
	205	+
	206	+* Bugfix: DOB can now again be initially set by users with write access to the Operatives Database
	207	+* Bugfix: Convention Rank can now be set again by users with write access to the Operatives Database
	208	+
	209	+=== 1.8.15 (29.04.2024) ===
	210	+
	211	+* 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
	212	+* Removed height / weight from Operative Database (unneeded PII)
	213	+* Added the ability to change the Nickname for the Operatives in Personal Preferences
	214	+
	215	+=== 1.8.14 (19.04.2024) ===
	216	+
	217	+* Updated Operatives Management so users with write access to the Operatives Database can no longer set access permissions that exceed their own
	218	+* Removed the Messaging Module as it was not used any more
	219	+* Updated Operatives Management, secured and updated POSTVAR / SQL statements, added error codes and error log
	220	+* Updated PNG Management, secured and updated POSTVAR / SQL statements, added error codes and error log
	221	+
	222	+=== 1.8.13 (16.04.2024) ===
	223	+
	224	+* Updated ARO Management, secured and updated POSTVAR / SQL statements, added error codes and error log
	225	+* Updated Item Type Management, secured and updated POSTVAR / SQL statements, added error codes and error log
	226	+* Bugfix: Items in the Item DB can now be edited if the item type that has been originally used was since deleted
	227	+
	228	+=== 1.8.12 (18.03.2024) ===
	229	+
	230	+* 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
	231	+
	232	+=== 1.8.11 (17.03.2024) ===
	233	+
	234	+* Updated L.A.S.S.I.E. Bot to include a reset password function
	235	+* Bugfix: Hitting [Enter] now properly closes the dialogue window when creating new API Keys in API Keys Management
	236	+
6	6	=== 1.8.10 (14.03.2024) ===
7	7
8	8	* 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