Scope and layout of the documentation
Spis sekcji dokumentacji z zakresem każdej z nich, punkt wyjścia w zależności od rodzaju zadania, znaczenie powtarzających się elementów oraz to, czego te strony nie opisują.
How to use the documentation
This documentation is reference material, not a manual to be read from cover to cover. Every topic is a separate, self-contained whole: any one of them can be opened and understood without reading the previous ones.
To begin, the First steps section is enough. Read the rest when the need arises.
Documentation sections
The sections follow the order in which the system is learned in practice: first getting around the screens, then working with data, and finally the areas used less often.
| Section | Scope |
|---|---|
| 01. Introduction | what Opero is and how to read these pages |
| 02. First steps | the first day of work, the screen layout, vocabulary, the rhythm of the day |
| 03. Getting around the system | menu, modules, custom pages, and dashboards |
| 04. Record lists | an object's list and its views, searching, filters, export to Excel |
| 05. Records | creating and editing a record, the form, fields, relations, attachments, comments, history |
| 06. Processes and tasks | the flow of matters, stages, transitions, approvals, tasks, the kanban board |
| 07. Automation | rules, triggers, notifications sent by the system |
| 08. Reports and documents | summaries, charts, report filters, document templates |
| 09. Built-in modules | contractors, service catalog, sales and cost invoices |
| 10. Integrations | data exchange with other systems, KSeF |
| 11. Account and access | profile, roles, working across companies, languages, reporting problems |
Where to start depending on the task
| Situation | Starting point |
|---|---|
| First day in the system | First steps, then Getting oriented in the system |
| Unfamiliar vocabulary | Basic concepts |
| Looking for a specific matter | the Record lists section |
| Entering and completing data | the Records section |
| Running matters through the flow | the Processes and tasks section |
| Issuing invoices and documents | the Built-in modules section |
| Reading summaries | the Reports and documents section |
| A problem occurred | Reporting problems |
Recurring elements
The same kinds of content recur across topics. It is worth recognizing them, because it speeds up reading.
- An example shows a thing in a concrete situation and appears in almost every topic. If a description reads abstractly, skip to the example and come back to the description.
- A highlight marks the thing whose omission costs the most: a trap, a boundary, or a principle that is easy to forget.
- A symptom table lays out the symptom, the cause, and the fix. It appears in topics where there is something to diagnose, and is then the fastest route to an answer.
- Related, at the end of a topic, points to neighboring topics.
The last two elements appear where they make sense, not in every topic.
Example. With an invoice problem, open the invoices topic and first check the symptom table, if the topic has one. This is usually thirty seconds instead of ten minutes of reading the whole thing.
Names in the documentation are examples
These pages describe the system's capabilities, while an instance is built for the organization's needs. Objects, fields, and stages may be named differently in a given instance than in the examples.
The principle stays the same. When the documentation talks about contracts and the same thing is called agreements in a given instance, everything in that topic still applies.
What the documentation does not cover
- System configuration. These pages describe working in the system: what to do, what to expect, what to watch for. Direct the question "how do I set this up" to the person responsible for the system at your company.
- A step-by-step guide for every screen. Screens differ between instances, so we describe the principles, not the sequence of clicks.
- A description of the processes in force in a given instance. These arise during the implementation and are known to the person running the system at the company.
- Accounting and tax matters. Opero runs the document flow, not the settlements.
Related
What Opero is describes the system as a whole. First steps describes the first day of work. Basic concepts explains the vocabulary. Getting oriented in the system describes the screen layout. Reporting problems describes what to do in case of a fault.
What Opero is
Do czego służy Opero, czym różni się od arkusza i skrzynki pocztowej, z czego składa się system i dlaczego u każdej firmy wygląda trochę inaczej.
First steps in Opero
Co zrobić w pierwszym dniu pracy z systemem: od zaproszenia i logowania, przez sprawdzenie profilu i firmy, po odnalezienie przypisanych zadań i pierwszego rekordu.