Most operational time is spent in lists, not forms: open orders, pending waybills, critical stock, collection queues. In EQLEM every list follows the same pattern. When the module changes, search, filter, sort, and drill-in behavior stay familiar. That is the backbone of everyday work experience.
List experience is not a “pretty table”; it is decision speed. The right filter prevents opening the wrong document; the right columns let you read status without calling someone.
Who is it for?
Every role uses lists. Warehouse operators scan pending transfers; sales sees open quotes; finance works collection/payment lists; managers watch exception lists. IT and power users want to share saved filters with the team. In multi-branch setups, list default scope is limited by multi-company; users are protected from noise.
How it works
The page list carries main records (orders, stock cards, accounts, vouchers). A sub-list shows a record’s child relations (lines, related documents, sub-definitions) in the same language. Users search text, apply field filters, pick date ranges, and narrow by status. Clicking a row opens document entry or a definition card.
Permissions decide which list actions appear (new, edit, delete, print, send). Unlicensed modules do not appear in menus or lists. Mobile lists may be simplified; full scanning and bulk work stay on the web. Dashboard widgets can shortcut frequent lists; depth still lives in the list + document pair.
Pagination and server-side filtering keep lists usable as data grows instead of downloading everything at once.
Benefits
The learning curve shortens: knowing one list transfers quickly to another. Operational rhythms standardize; morning “open items” filter, evening “created today.” Exception hunting gets easier with status and date filters. Many questions are answered in lists before reporting; reports are for deep analysis, lists for “what should I do now?”
Support cost drops: “where is the filter on this screen?” gets the same answer across modules. Opening a new module does not force a new UX language.
Relation to modules and products
Almost all business modules use the same list pattern: inventory, sales, purchase, finance, e-document queues, CRM lists, POS definitions, fleet, and assets. Platform Web is the primary screen. Notifications can take you to the related list or record. Reporting is the next step for period/summary needs. Definition cards also open from the same list family.
FAQ
What is the difference between a page list and a sub-list? A page list is main-record scanning; a sub-list shows a record’s child collections with the same pattern.
Can filters be saved? Frequent filters and views are supported by scenario; clarifying team standards is good practice.
Is bulk action on every list? It depends on document type and permission. Risky actions such as bulk delete may be restricted.
Are mobile lists the same? Same concept, different density. Heavy scanning and office queues stay on web.
Next step
Define two or three “morning lists” per role (filter + sort). Try Free to build your queues; support document quality with document entry.