﻿# What's new

> WorkSmartHub releases with their most important changes and the complete change list. Latest: version 24, Foreign clients, currencies and invoice corrections.

Source: https://workwise-solutions.net/changelog/ · Language: en · Hungarian version: https://workwise-solutions.net/hu/changelog/

## Version 24: Foreign clients, currencies and invoice corrections

15 November 2026. Számlázz.hu invoicing now handles foreign clients, VAT treatments other than domestic, euro and dollar invoices converted at the exchange rate you enter, advance invoices and correction invoices. Before an invoice is issued, a preview shows its lines, VAT breakdown and totals.

- **Foreign clients and VAT treatment**: A client can have a country, an EU VAT number and an invoice language, and the issue dialog offers domestic, reverse charge, intra-EU, export and third-country VAT treatments.
- **Euro and dollar invoices**: An invoice can be issued in a currency other than the prices, converted at the exchange rate entered at issue, with the euro or dollar bank account, IBAN and SWIFT from the company details.
- **Advance and correction invoices**: An advance invoice records a received advance and the final invoice deducts it automatically. A correction invoice changes the quantities and unit prices of an issued final invoice.
- **Preview and safe retries**: Before issuing, a preview shows the lines, the VAT breakdown, the totals and the exchange rate, and a retry after a dropped connection never issues a second invoice.

**Before you upgrade**

- New database migrations run automatically at start. Once an advance invoice or a correction invoice has been issued, an earlier version can be restored only from a database backup.
- Notification templates that were never edited are replaced with the new default version during the upgrade. Edited templates stay as they are.

### New

- Invoicing: A client can have a country, an EU VAT number and an invoice language (11 languages); the fields are shown while invoicing is on
- Invoicing: Acting works, components and deliveries can have their own VAT rate, with a TAM mark at 0 %; the component Excel file gets an optional VAT rate column
- Invoicing: The VAT treatment can be chosen at issue: domestic, domestic reverse charge, intra-EU supply of goods or service, export of goods, service to a third country
- Invoicing: Preview before issue with the lines, the VAT breakdown, the totals and the exchange rate
- Invoicing: Euro or dollar invoices can be issued from forint prices, and forint invoices from euro or dollar prices, at the exchange rate entered at issue
- Invoicing: On euro and dollar invoices the exchange rate used by the company can be entered and is stored; its source can be set in the Számlázz.hu settings
- Invoicing: The company details can hold euro and dollar bank account numbers, IBAN and SWIFT for foreign-currency invoices
- Invoicing: A final invoice paid in cash or by card can be issued as already paid
- Invoicing: Correction invoice for the quantity and unit price of the lines of an issued final invoice
- Invoicing: Advance invoice when the advance is received, deducted automatically by the final invoice
- Invoicing: A retry after a dropped connection does not issue a second invoice
- Invoicing: The background job also looks up an issue that got no answer in Számlázz.hu, stores the invoice it finds and releases the held fee request (díjbekérő)
- Invoicing: After a correction the invoice shows the amount still due or the amount owed back; before a correction the payment state is refreshed from Számlázz.hu
- Invoicing: The summary on the Számlák (Invoices) page shows the amounts per currency
- E-mail: Advance invoices and correction invoices are sent with their own text, and foreign-currency invoices with the exchange rate

### Changed

- Invoicing: Automatic invoicing skips foreign clients and work tickets with an advance; the skip is shown on Hiba Események (Error events)
- Invoicing: An invoice is overdue from the day after its payment deadline, and only while an amount is still due on it; the overdue notification shows the amount still due
- Invoicing: Amounts are shown in Hungarian number format, euro and dollar amounts with two decimals
- Notifications: Templates that were not edited are replaced with the new default version on upgrade; edited templates do not change
- Work tickets: With different VAT rates, the delivery notification shows only the net and gross totals
- Work tickets: The costs in the summary are shown in Hungarian number format
- Database: New migrations for client, catalog and invoice fields run automatically at start. Once an advance invoice or a correction invoice exists, returning to an earlier version is possible only by restoring a database backup

### Fixed

- Invoicing: Of two issues started at the same time for one work ticket, only one is completed
- Invoicing: Confirmation texts and notifications use the correct Hungarian article
- Invoicing: The summary does not count credit notes, correction invoices or fee requests converted into a final invoice as payments; the unpaid and overdue amounts show the amount due including corrections
- Invoicing: A corrected invoice shows a single amount due, and a fee request converted into a final invoice shows no outstanding amount
- Invoicing: Issuing an invoice starts with the configured payment deadline
- Invoicing: With invoicing off, the Ügyfelek (Clients) page shows no invoice data, and the Számlák page cannot be opened by its address either
- Invoicing: On forint invoices the VAT of the lines is rounded to whole forints
- Invoicing: A credit note request from a work ticket does not issue an invoice
- Clients: The invoice history totals the outstanding amount per currency
- Database: When a Schema setting is given with MySQL, the start-up error message names MySQL and explains that the database can be set in the connection string

## Version 23: .NET 10 and automatic invoicing

9 November 2026. WorkSmartHub runs on .NET 10 LTS, comes with a smaller Docker image and a Helm chart for Kubernetes, and can issue the final invoice automatically when a work ticket is set to Számlázandó (To be invoiced). The release also fixes many invoicing, file storage and security issues.

- **.NET 10 LTS runtime**: The application runs on .NET 10 LTS with Entity Framework Core 10 and updated dependencies.
- **Docker and Kubernetes**: The Docker image is based on Ubuntu 24.04 LTS and is about a third smaller, and a Helm chart starts WorkSmartHub on Kubernetes with built-in PostgreSQL and Redis.
- **Automatic invoicing on status change**: When a ticket admin sets a work ticket to Számlázandó, the final invoice is issued once, the same way as a manual issue.
- **Invoice PDFs in file storage**: Invoice PDFs are kept in the work ticket's file storage instead of the database, and with WorkSmartHub delivery the application e-mails the PDF to the buyer.

**Before you upgrade**

- Install the ASP.NET Core 10.0 runtime before upgrading.
- Windows (IIS): install the ASP.NET Core 10.0 Hosting Bundle before upgrading, then run iisreset.
- Linux: install the aspnetcore-runtime-10.0 package before upgrading (on Ubuntu 22.04 from the dotnet/backports PPA). The systemd unit does not change.
- Docker and file storages need no configuration change, and no database migration is needed.
- Invoice PDFs move out of the database into the work ticket's file storage, or into the automatically created local file storage Számlák (automatikus), which under Docker and Kubernetes is on the /app/data volume. A file storage that holds invoice PDFs cannot be deleted.
- Replacing a valid licence requires Super Admin permission.

### New

- Docker and Kubernetes: Install scripts and a Helm chart in the WorkSmartHub-Docker-Kubernetes repository; on Kubernetes, built-in PostgreSQL and Redis start without configuration
- Invoicing: The Automatikus számlázás státuszváltáskor (Automatic invoicing on status change) setting works; when a ticket admin sets a work ticket to the Számlázandó (To be invoiced) status, the final invoice is issued the same way as a manual issue, at most once per work ticket; on error the status change is kept
- Invoicing: With the WorkSmartHub delivery method the application e-mails the invoice PDF to the buyer; the result of the sending is shown on the invoice and the e-mail can be sent again
- Invoicing: The PDFs of credit notes and storno invoices can be downloaded too
- Invoicing: With Számlázz.hu invoicing on, the VAT rate can be 27, 18, 5 or 0 % and the currency HUF, EUR or USD; an invalid value gives a field error at save

### Changed

- Platform: The application runs on the .NET 10 LTS runtime. Install the ASP.NET Core 10.0 runtime before upgrading
- Platform: For Windows (IIS) installations, install the ASP.NET Core 10.0 Hosting Bundle before upgrading, then run iisreset
- Platform: For Linux installations, install the aspnetcore-runtime-10.0 package before upgrading (on Ubuntu 22.04 from the dotnet/backports PPA); the systemd unit does not change
- Docker: The image is built on the ASP.NET Core 10.0 Ubuntu 24.04 LTS base image and is about a third smaller; no settings change is needed
- Database: Entity Framework Core 10 and its providers, on MySQL the Microting provider that continues the development of Pomelo; no database migration is needed
- Notifications: E-mail and notification templates are rendered by a new template engine; edited templates work without changes, and a change takes effect without a restart
- File storage: New major version of the file storage packages; existing files stay available, no settings change is needed
- Security: Dependency updates: Microsoft Graph 6, Bot Framework 4.23, Serilog 10, Swashbuckle 10
- Invoicing: Invoice PDFs are stored in the work ticket's file storage, or without one in an automatically created local file storage (Számlák (automatikus)), not in the database; under Docker and Kubernetes this is on the /app/data volume. A file storage that holds invoice PDFs cannot be deleted
- Security: Replacing a valid licence requires Super Admin permission; without a licence or with an expired licence, uploading is still possible without signing in
- Security: The data of the Alkalmazás állapota (Application status) page and the lists of application-level notification channels and file storages are available through the API too only to users who see the menu item or have read permission
- Security: Profile data of other users can be requested only by a Super Admin

### Fixed

- Invoicing: The invoice is always issued in the currency of the prices, and requesting another currency gives an error message before Számlázz.hu is called; previously the amounts of a forint work ticket could end up on a euro invoice without conversion
- Invoicing: A final invoice issued from a fee request (díjbekérő) keeps the delivery method of the fee request
- Invoicing: A cancelled (stornó) or credited invoice shows no outstanding debt
- Logs: A refused invoice PDF download does not leave an unhandled error in the log
- Warehouse: When a work ticket is deleted, the component quantities return to stock
- Components: Component images can be uploaded to S3 and Azure file storages too
- Work tickets: A work ticket can be created without an e-mail sender setting, and the skipped confirmation e-mail is logged
- Work tickets: A warning about the delivery notification is logged only when sending fails
- File storage: The connection test writes the same way as an upload, so an S3 key without list permission fails at the test and not at the first upload
- File storage: The application does not follow symbolic links inside the root of a local file storage
- Attachments: Files downloaded from object storages get a Content-Length header
- E-mail: The SMTP timeout applies in seconds; e-mails sent with the default e-mail settings show the real version number of the application
- Cache: The SQL Server cache gave an error at start
- Portal: After an upgrade the browser loads the new portal version immediately, on deep links too
- Portal: Typos in the labels of the work ticket statuses and of the client delete button
- Database: A new SQLite database logs no PRAGMA foreign_keys warnings; an SQLite migration lock left by an interrupted first start does not block the next start
- Database: Several servers starting at the same time on an empty database do not fail at the first stored file; on PostgreSQL, when the password is refused, the start-up log explains clearly what to do
- Logs: XLSX exports work on Linux installations too; log file queries give an error message when a parameter is missing
- Sign-in: The Apple (AppleConnect) sign-in type starts; the proxy gives an error message when the route is missing
- Platform: The installation package contains no debug symbols and no development settings
- Security: Files in the template folders cannot be downloaded over HTTP with any path spelling; password reset gives the same answer for existing and non-existing addresses

## Version 22: Docker image on Ubuntu 24.04 LTS

23 October 2026. The Docker image moves from Debian 12, whose security support ended in July 2026, to the Microsoft ASP.NET Core 8.0 Ubuntu 24.04 LTS base image. No configuration change is needed.

- **Supported base image**: The image no longer uses Debian 12, which container scanners flag as an end-of-life component.

### Fixed

- Security: The Docker image is built on the Microsoft ASP.NET Core 8.0 Ubuntu 24.04 LTS base image instead of Debian 12, whose security support ended in July 2026 and which container scanners flag as an end-of-life component; no settings change is needed

## Version 21: Security updates for runtime and packages

19 October 2026. The Docker image uses the ASP.NET Core 8.0.32 runtime, which fixes the Kestrel vulnerability CVE-2026-70188, and the packages flagged by vulnerability scanners are updated. No configuration change is needed.

- **Updated runtime and packages**: The image is built on ASP.NET Core 8.0.32, and the packages reported by scanners are updated to fixed versions.

### Fixed

- Security: The Docker image is built on the current ASP.NET Core 8.0 runtime (8.0.32), which fixes the Kestrel vulnerability CVE-2026-70188 and the other runtime findings that container scanners reported in earlier images
- Security: Package updates for vulnerabilities reported by scanners: Microsoft.AspNetCore.Authentication.Negotiate 8.0.32, System.Security.Cryptography.Pkcs 8.0.2 and Xml 8.0.5, SQLite engine 3.54.0 (SQLitePCLRaw 2.1.14), Scriban 7.5.1, AngleSharp 1.8.5, Microsoft.Rest.ClientRuntime 2.3.24; no settings change is needed

## Version 20: Shutdown time, connection tests and settings log

11 October 2026. Background jobs get 45 seconds to finish at shutdown, connection tests are limited to administrators and no longer accept secrets in the URL, and every change to the application settings is logged. Attachments uploaded to Box in several parts are no longer truncated.

- **Settings changes in the log**: Every save, restore and logo change of the application settings is logged with the changed fields and their old and new values, never with secrets.
- **Connection tests for administrators**: Connection tests of notification channels and file storages are available only to application or workspace administrators, and secret settings sent in the URL are refused.
- **Complete Box uploads**: Attachments and images uploaded to Box in several parts are stored complete.
- **Windows and Linux install guide**: The README describes installation on Windows (IIS) and on Linux (systemd, nginx).

**Before you upgrade**

- The application gives background jobs 45 seconds at shutdown. Raise stop-timeout to 60 in the Docker start command, TimeoutStopSec to 75 in the systemd unit, and shutdownTimeLimit to 60 under IIS, as described in the README.
- A local file storage whose root folder name ends with a dot or a space, or is a device name, reports an error at save. Rename the definition and, on Linux, move the storage folder under the definition to the new name.

### New

- Logs: Every save, restore and logo change of the Alkalmazásbeállítások (Application settings) gets a log entry with the changed fields and their old and new values; secrets never get into the log
- Documentation: Installation guide for Windows (IIS) and Linux (systemd, nginx) in the README

### Changed

- The application gives background jobs 45 seconds at shutdown, so stop-timeout in the Docker start command must be raised to 60, TimeoutStopSec in the systemd unit to 75, and shutdownTimeLimit under IIS to 60, as described in the README
- If the root folder name of a local file storage ends with a dot or a space or is a device name, the storage reports an error at save; the definition must be renamed and, on Linux, the storage folder under the definition moved to the new name

### Fixed

- File storage: Attachments and images uploaded to Box file storage in several parts were stored truncated. The file storage packages are updated, no settings change is needed
- File storage: The root folder of a local file storage is checked at save; a name ending with a dot or a space and a device name cannot be used, and an invalid value gives a field error
- Security: The connection test of notification channels and file storages is available only to application or workspace level administrators, and sending secret settings in the URL is refused. The test of the default e-mail settings is available only to SuperAdmin
- E-mail: Without SSL the connection test does not send the password unencrypted and does not test authentication, and the result says so. The SMTP send timeout applies in seconds, and the Teams channel timeout applies too
- Personal access tokens: The access token does not outlive the expiry of the token, a past or non-positive expiry is refused, and a missing expiry warning list causes no error
- Background jobs: Expiry warnings and the invoice status sync record their result during shutdown too, and warnings are not sent twice after a restart
- Error messages of the connection tests contain no call stack, and a storage error during attachment upload gives the user a general message
- Docker: A read-only appsettings.json is logged once, at information level

## Version 19: Lasting sign-ins and multi-server operation

9 October 2026. Sign-ins survive restarts, container replacement and upgrades and are valid on every server, and scheduled jobs run only once when several servers run together. Secret values can no longer be read back, and the server checks access to work tickets and invoices.

- **Sign-ins that last**: The sign-in keys are stored in the database, so a sign-in stays valid after a restart, a container replacement or an upgrade, and on every server.
- **Several servers, one schedule**: With several servers, each scheduled background job runs only once per occurrence, and the database migration at start is locked.
- **Write-only secrets**: Secret values such as the Vault token, the Számlázz.hu keys and the secrets of file storages and notification channels cannot be read back, and an empty field keeps the stored value.
- **Real Számlázz.hu fee requests**: New fee requests (díjbekérő) are real Számlázz.hu fee requests and can be converted into a final invoice from the paid status too.

**Before you upgrade**

- After the upgrade everyone has to sign in again once.
- Replacing the Vault token and the Box secrets after the upgrade is recommended. Secret values must be entered again when the target of a setting changes.
- Earlier fee requests appear as advance invoices and cannot be converted into final invoices. Having them reviewed by an accountant is recommended.
- E-mail notification channels that use Windows integrated authentication need a user name and password.
- Links in e-mails use the optional PublicBaseUrl setting; a warning appears at start while it is missing.

### New

- Optional PublicBaseUrl setting for links sent in e-mails (password reset, unsubscribe), with a warning at start when it is missing
- Sign-in keys are stored in the database, so a sign-in survives restarts, container replacement and upgrades, and is valid on several servers. After the upgrade everyone has to sign in again once
- When running on several servers, scheduled background jobs run only once per occurrence, Run-once claim cleanup background job, locked database migration at start, warning when the InMemory cache is used
- Docker: /health endpoint, security updates in the image, and edited e-mail and notification templates are stored on the persistent volume
- Log levels switch; when it is off, the levels from appsettings.json and the environment variables apply
- 0 % VAT rate and VAT exemption code (AAM, TAM) for Számlázz.hu invoices

### Changed

- E-mail notification channels that use Windows integrated authentication need a user name and password

### Fixed

- Secret values (Vault token, Számlázz.hu keys, Box, file storages, notification channels) cannot be read back, are kept when left empty, and must be entered again when the target changes. Replacing the Vault token and the Box secrets after the upgrade is recommended
- Personal access tokens can be used only for API calls and stop being valid within about 1 minute of revocation, and the refresh token can also be sent in the request body
- The server also checks access to work tickets and invoices based on assignment. Data of clients recorded in the Ügyfelek (Clients) menu can be changed from a work ticket only by a client admin. The invoice overview and the invoice section of the work ticket belong to ticket admins, and so does refetching the PDF. Ticket admins can select the client and the delivery without global client and delivery permissions. Attachments are kept after the file storage is changed
- New fee requests (díjbekérő) are real Számlázz.hu fee requests; they can be converted into a final invoice from the paid status too, and the final invoice refers to the fee request; a failed deletion or stornó reports an error, and recording a payment does not report an error by mistake. Earlier fee requests appear as advance invoices and cannot be converted into final invoices; having them reviewed by an accountant is recommended
- Számlázz.hu: A paid fee request can be converted into a final invoice only with a recorded payment, a failed payment recording can be started again, and a payment is never recorded twice. The sync closes invoices cancelled (stornó) in Számlázz.hu and fee requests deleted there, and checks the invoice before the overdue notification
- New SQL Server installations work again, the MinIO file storage can be used again, and a retention period of 0 does not delete all data. The e-mail templates for the overdue deadline, the service user warning and the new user were missing from the package; they are sent again
- Saving the configuration does not delete the Számlázz.hu signing key and shows save errors; the low stock e-mail is sent only when there is an actual shortage
- Only PNG or JPEG files can be uploaded as component images. Security fixes, fixes and optimizations on both the UI and the server side

## Version 18: Számlázz.hu integration and persistent Docker data

26 September 2026. WorkSmartHub connects to Számlázz.hu, the Hungarian online invoicing service, and adds Google Cloud Storage as a file storage. Under Docker the database, the files and the logs are kept on a persistent volume, and download links of attachments are checked more strictly.

- **Számlázz.hu integration**: WorkSmartHub can be connected to Számlázz.hu, the Hungarian online invoicing service.
- **Persistent Docker volume**: The database, the file storage and the log files are kept in the worksmarthub-data volume, so they survive container restarts, replacements and upgrades.
- **Google Cloud Storage**: Google Cloud Storage is available as a file storage option.
- **Stricter download links**: Download links of attachments and images are checked more strictly, and attachments are always served as downloads.

**Before you upgrade**

- Check the existing file storages before upgrading: storages whose root path contains a ".." element or, for local disk and SharePoint, a colon cannot be used after the upgrade until the path is corrected.
- A warning appears at start while the signing keys in appsettings.json (sign-in, attachment and image links) still have their default values.
- The Docker installation guide covers data persistence, backup and restore, and moving from an earlier version.

### New

- When running under Docker, the database, the file storage and the log files are stored in a persistent volume (worksmarthub-data), so they are kept after the container is restarted, replaced or upgraded
- Warning at start when the signing keys in appsettings.json (sign-in, attachment and image links) still have their default values
- Számlázz.hu integration
- Google Cloud Storage file storage option

### Fixed

- Stricter security checks for the download links of work ticket attachments and images; attachments are always served as downloads
- The root path of file storages is checked at creation, modification and use. Check the existing file storages before upgrading: storages whose root path contains a ".." element or (for local disk and SharePoint) a colon cannot be used after the fix until the path is corrected
- Docker installation guide (data persistence, backup and restore, moving from an earlier version)
- Download links of attachments and images are built with the current server address on every request, so links of previously uploaded files keep working after the server address, port or proxy setting changes

## Version 17: Component export and import with Excel

25 December 2025. Warehouse components can be exported to Excel, edited there and imported back with checks.

- **Edit components in Excel**: Export the warehouse components to Excel, edit them and import the file back; the import checks the data.

### New

- Export of warehouse components to Excel, editing and importing them back with checks

### Fixed

- Fixes and optimizations on both the UI and the server side

## Version 16: Account e-mails and component images

22 December 2025. With the local user store, new users receive an e-mail with their account details and any steps they need to take. Warehouse components can have images, saved and served in three sizes.

- **E-mail for new accounts**: With the local user store, users get an e-mail with the details of their new account and any steps they need to take.
- **Component images**: Images can be uploaded to warehouse components and are saved and served in three sizes.

### New

- With the local userStore, an e-mail is sent to the user with the details of the created account and any steps to take
- Image upload for warehouse components, saved and served in 3 different sizes

### Fixed

- E-mail templates apply the CSS styling correctly with different SMTP services too
- Fixes and optimizations on both the UI and the server side

## Version 15: Custom properties for external user stores

15 December 2025. Active Directory, LDAP and Azure Entra ID user stores get extraProperties options that can be tailored to custom needs, and LDAP recursion is fixed and optimized.

- **User store extraProperties**: Active Directory, LDAP and Azure Entra ID user stores can be fitted to custom needs with extraProperties options.

### New

- ActiveDirectory, LDAP and Azure Entra ID UserStores get extraProperties options, so they can be tailored to custom needs

### Fixed

- LDAP UserStore recursion fixes and optimizations
- Small UI fixes and optimizations

## Version 14: Small user interface fixes

27 October 2025. A maintenance release with small fixes and optimizations in the user interface.

### Fixed

- Small UI fixes and optimizations

## Version 13: Service user catalog with HashiCorp Vault

30 August 2025. The new service user catalog records service users and sends warning notifications about them, and it can use HashiCorp Vault as its store.

- **Service user catalog**: Service users are kept in one catalog, with warning notifications.
- **HashiCorp Vault integration**: The service user catalog can store its data in HashiCorp Vault.

### New

- Service user catalog, with warning notifications
- HashiCorp Vault integration for the service user catalog

### Fixed

- Server-side optimizations and extra checks for processes
- Small UI fixes and optimizations

## Version 12: Box file storage and Swagger switch

22 June 2025. Box is available as a file storage, and the Swagger API documentation page can be enabled or disabled.

- **Box file storage**: Box is available as a file storage option.
- **Swagger page on or off**: The Swagger API documentation page can be enabled or disabled.

### New

- Box file storage option
- Option to enable or disable the Swagger API documentation page

### Fixed

- Server-side optimizations
- Small UI fixes and optimizations

## Version 11: Log service fixes and security options

11 May 2025. The log service gets fixes and extra security options, along with small user interface fixes.

- **Log service fixes**: The log service gets fixes and extra security options.

### Fixed

- Log Service fixes, extra security options
- Small UI fixes and optimizations

## Version 10: Cross-platform e-mail logo fixes

5 April 2025. E-mail logo processing gets cross-platform fixes, with small optimizations on the server and in the user interface.

- **E-mail logo on every platform**: Fixes in e-mail logo processing apply across platforms.

### Fixed

- Small server-side optimizations
- Cross-platform fixes for e-mail logo processing
- Small UI fixes and optimizations

## Version 9: Override component prices on tickets

27 February 2025. The prices of components on a work ticket can be overridden or changed.

- **Component prices per ticket**: The price of a component can be overridden or changed on the work ticket.

### New

- Overriding/changing the prices of work ticket components

## Version 8: More error checks and details

27 January 2025. A maintenance release with user interface fixes, extra error checks and more detailed error information.

### Changed

- UI fixes, optimizations
- Extra error checks and extended error information

## Version 7: .NET 8 and mobile app setup

1 January 2025. WorkSmartHub moves from .NET 6 to the .NET 8 LTS runtime. A QR code window configures the mobile app, the LDAP user store gets more configuration options, and log files are easier to filter from the user interface.

- **.NET 8 LTS runtime**: The application runs on .NET 8 (LTS) instead of .NET 6 (LTS).
- **Mobile app setup by QR code**: A QR code window provides the configuration for the mobile app.
- **Broader LDAP user store**: The LDAP user store is extended and generalized, with more configuration options and combinations with the sign-in options.
- **Faster log filtering**: Logging is reworked, so information in the log files can be filtered more simply and faster from the user interface.

**Before you upgrade**

- The application now needs the .NET 8 (LTS) runtime instead of .NET 6 (LTS); install it before upgrading.

### New

- Mobile app configuration QR code window
- User stores: LDAP extended and generalized, with more configuration options and combinations with the sign-in options
- Work tickets: Warning dialog for saving or discarding certain changes

### Changed

- Optimized and fixed work ticket processing on the server side
- File storage: Extended configuration options for Azure Blob Storage
- Logging reworked, with simpler and faster filtering of information in the log files from the UI
- Extra information about the internal database on the status page
- Upgrade to the .NET 8 (Long Term Supported) runtime from the earlier .NET 6 (LTS) version

### Fixed

- Background job optimization, error handling that covers significant edge cases
- Small UI fixes and optimizations
- Follow-up of the hosting changes on the Azure portal that affect .NET 8

## Version 6: Active Directory and LDAP sign-in fixes

21 March 2024. The automatic SSPI authentication window can be turned off for Active Directory sign-in, the LDAP user store searches user groups recursively, and a 403 SSPI authentication error in some AD setups is fixed.

- **Optional SSPI window**: A setting turns off the automatic SSPI authentication window for Active Directory sign-in.
- **Recursive LDAP groups**: The LDAP user store searches user groups recursively.

### New

- Setting to disable the automatic SSPI authentication window with ActiveDirectory sign-in

### Changed

- The LDAP UserStore now searches user groups recursively

### Fixed

- 403 SSPI authentication error in some AD setups

## Version 5: New ticket statuses and client e-mail log

11 January 2024. Work tickets get new status options, and a new page shows and records the e-mails sent to clients. The guarantor option is available in every work ticket query.

- **New status options**: Work tickets get new status options.
- **E-mails sent to clients**: A new component shows and records the e-mail entries sent to clients.
- **Guarantor filter everywhere**: The guarantor option is available in every work ticket query, not only for archived tickets.

### New

- Work tickets: New status options
- New component - overview and recording of the e-mail entries sent to the client

### Changed

- Work ticket query - the guarantor option is always available, previously only for archived tickets
- Minor optimizations, validation changes

## Version 4: Out for delivery status and searchable lists

2 January 2024. Work tickets get the Kiszállítás alatt (Out for delivery) status, and manufacturers, groups and product types are chosen with a search field instead of a drop-down menu. Ticket printouts show the assigned users and groups.

- **Out for delivery status**: Work tickets can be set to the new Kiszállítás alatt (Out for delivery) status.
- **Search instead of drop-downs**: Manufacturers, groups and product types are chosen with a search and filter field instead of a drop-down menu.
- **Assignees on printouts**: Work ticket printouts show the users and groups assigned to the ticket.

### New

- Work tickets: New status option - "Kiszállítás alatt" (Out for delivery)
- Work tickets: Search/filter option instead of the drop-down menu for manufacturers, groups and product types

### Changed

- Work ticket print components, display of the users/groups assigned to the work ticket
- Minor optimizations, validation changes

## Version 3: Ticket operating modes and automatic naming

28 December 2023. A configuration page selects how work tickets operate, and the Klasszikus (Classic) option names tickets with a number fully automatically. The delivery route and the delivery status can be changed and saved in one step.

- **Ticket operating mode**: A new configuration page selects the operating mode of work tickets.
- **Classic numbering**: The Klasszikus (Classic) option generates the ticket name as a number fully automatically, not only as a suggestion.
- **Delivery in one save**: After the delivery route is chosen, the delivery status can be changed and saved together with it.

### New

- Further extension of the work ticket configuration options
- Work ticket configuration page for choosing the operating mode of the ticket
- Work tickets: "Klasszikus" (Classic) name generation option (numeric identifier), where the name is generated fully automatically, not just suggested

### Changed

- Work tickets: After the delivery route is selected, no save is needed before changing to the delivery statuses; both changes can be made at once and saved
- Work ticket print components, more dynamic fields (a field without a value does not appear on the page, to use the sheet effectively)
- Minor optimizations

## Version 2: Automatic ticket names and better search

23 December 2023. Work tickets can get their name or identifier generated automatically, unique identifiers have an overview page, and ticket search and archive filters are extended. Printouts are simpler and have more options.

- **Automatic names and identifiers**: Work tickets can get their name or identifier generated automatically, and unique identification numbers have their own overview page.
- **Better ticket search**: Ticket search is optimized and extended, with more filters for tickets in archive status.

### New

- Extension of the work ticket configuration options
- Work tickets: Overview page of unique identification numbers
- Work tickets: Automatic name / identifier generation option
- Work ticket search optimization and extension
- More filtering options for work tickets in archive status

### Changed

- Printouts simplified / optimized and extended with more options
- Minor optimizations

## Version 1: First release of WorkSmartHub

19 December 2023. The first version manages clients and work tickets in workspaces, with user stores, personal access tokens for the API, logs and audit, notification channels, file storages, a calendar and printouts.

- **Work tickets in workspaces**: Workspaces provide complete management of work tickets, with configurable ticket sections.
- **Users and groups**: User stores manage users and groups, including an external user store.
- **Notifications and file storage**: Notification channels with notification templates and file storage services can be set up on application and workspace level.
- **API access with tokens**: Personal access tokens give access to the API for automation.

### New

- Client management
- Workspaces - complete work ticket management
- Work ticket configuration sections
- User stores - user and group management, external user store
- Personal access tokens - API access, automation
- Log and audit processes
- Application configuration panels
- Scheduling and configuration of background jobs
- Notification channels on application and workspace level, notification templates
- File storage services and configurations on application and workspace level
- Modular, optimized user interface
- Calendar feature
- Printouts
