General System Usage
Every module in QDMS Now is built on the same screen conventions. Learning them once means the second module you use is mostly already familiar.
This page describes the shared behaviour. Module pages only describe what is specific to that module.
Lists
Most modules open on a list of records.
| Element | What it does |
|---|---|
| Columns | Configurable. You can show, hide and reorder them; your choice is remembered. |
| Filters | Filter on any filterable column. Filters combine — each one narrows the result further. |
| Sorting | Click a column header to sort; click again to reverse. |
| Search | Free-text search across the list. |
| Row actions | Per-record actions — view, edit, delete — shown at the end of the row. |
| Bulk actions | Select several rows to act on them together, where the module supports it. |
| Export to Excel | Exports the current result set, respecting your filters and column selection. |
Export honours what is on screen. If the export has the wrong rows or columns, fix the filters and column selection first rather than editing the spreadsheet afterwards.
Detail pages
Opening a record shows its detail page. The layout is consistent across modules:
- Header — the record's code, name and current state, plus the actions available to you right now.
- Field sets — the record's own fields, grouped into panels.
- Tabs — child collections: actions, attachments, history, related records.
- State actions — the buttons that move the record through its lifecycle. Which ones appear depends on the record's state and on whether you hold an open task for it.
If an action you expect is missing, it is usually one of three things: the record is in a state that does not allow it, you do not hold a task for it, or your role lacks the permission. The first two are the most common.
Codes and auto-numbering
Most records have a code generated from a number template. Once the record exists, the code becomes read-only — it is the stable identifier other systems and documents refer to.
States and tasks
Records move through named states. What you can do depends on the current state, and the system creates a task for whoever needs to act next.
Work through your task rather than editing the record directly: acting on the task is what completes it and lets the record advance. See Task Management.
Attachments
Attachments follow the same pattern everywhere:
- Upload the file. It is held temporarily.
- Save the record. Only then is the file moved into permanent storage.
An uploaded file is not stored until the record is saved. Leaving a screen after uploading but before saving loses the file.
Many modules keep planning attachments and performance attachments as separate collections — what you intended and what you did are different evidence.
Identities
Wherever the system asks for a person, it usually accepts an identity: a user, a role, a user group, a position or an organization unit.
Prefer roles, positions and groups over named individuals. Membership is resolved when the work is read, so a responsibility assigned to a position keeps working when the person in it changes.
Language
The interface and the documentation are available in English and Turkish. Switch languages from the selector in the navigation bar. Documents themselves can carry a separate file per language — see Documents.
Reports and Excel
Most list screens offer:
- Export to Excel — the current result set.
- Report — a formatted report for a single record.
- List report — a formatted report for the whole result set. Large ones run in the background and notify you when ready.
Configurable screens
Screens are configured through Function Design. Your organization may have renamed labels, hidden fields, added custom fields or retargeted task assignments.
If a field described in this knowledge base is missing from your screen, it has most likely been hidden for your role rather than removed from the product.