Press Ctrl+K anywhere in the application (or click the “Search…” box in the header) and start typing.
HQSFlow searches customers (code, name, tax ID), items (code, name, symbol, every barcode), employees of the
current company, operators and companies at once — and the names of screens in the menu too. Results respect
permissions: nobody sees records in search that they have no access to. With no query, the window shows
recently opened records.
Change history — with an on/off switch
“Who changed this customer’s payment term?” — the answer is on the record’s History tab. Each save is
one entry on a timeline: operator, date and time, and below it the fields with their values before and after.
Dictionary values show by name, not by number, and changes on other tabs (addresses, contacts, bank accounts,
limits, consents, units, barcodes, groups, attributes) appear on the record they belong to.
History nobody needs just takes up space. So the administrator switches logging on separately for each
record type — customers, items, employees, operators, roles, companies, structure, settings and individual
dictionaries — and sets a retention period; older entries are removed automatically. Security and
configuration changes are logged from day one, and switching history on or off always leaves a trace.
The Change log screen gathers changes from all registers in one place.
A list view that remembers how you work
A salesperson wants to see phone and e-mail, an accountant — tax ID and country. Instead of choosing columns
every time, everyone saves their own list view: columns and their order, widths, filters, sorting, rows
per page and the archived switch. A view can be set as the default, so the list opens in it straight away,
or shared with the whole team. When the layout differs from the saved one, the system shows it. The mechanism
is part of the shared list, so it works the same on every list in the system.
Attributes instead of requests to a developer
Every company has a few pieces of information no standard anticipated: customer segment, region, shelf
life, packaging colour. In HQSFlow the administrator adds them as attributes in the Dictionaries module
— chooses the data type (text, whole number, decimal, date, yes/no, list of values), decides whether the
field is required, and which records it applies to. The field appears on the records straight away, with
value validation.
Attachments where you look for them
The contract next to the customer, the data sheet and photo next to the item. Files are stored in the
database — a database backup covers attachments too, with no separate network folder to look after.
The maximum file size and the list of blocked extensions are set by the administrator.