Introduction
Project Four is a configurable business application built around transactions, approvals and reporting. It also serves as the reference template for onboarding a new product into this documentation portal.
What this manual covers
Section titled “What this manual covers”This is the complete operating manual for Project Four 1.0. It is written for the people who use the application day to day, and is organised by module so you can read it front to back as training material or dip into a single task.
The modules
Section titled “The modules”Features
What the application does, module by module.
Configuration
Set the application up before users start work.
Workflows
The three procedures that make up the transaction cycle.
Reports
Summary and detailed reporting with exports.
Administration
Accounts, roles and the audit trail.
How to read a page in this manual
Section titled “How to read a page in this manual”Every task page follows the same shape, so once you have read one you know where to look on all of them.
| Step | Action | Result |
|---|---|---|
| 1 | Overview | What the screen is for and when to use it |
| 2 | Prerequisites | What must already exist before you start |
| 3 | Procedure | The numbered steps, with screenshots |
| 4 | Expected result | How to tell it worked |
| 5 | Field reference | Every field, its type and its rules |
| 6 | Common problems | What usually goes wrong, and the fix |
The structure of a task page
Conventions
Section titled “Conventions”| Field | Type | Description |
|---|---|---|
| Bold text | Notation | A button, menu item or field label exactly as it appears on screen. |
| Sales → Transactions | Notation | A navigation path through the menu. |
| Monospace | Notation | A value you type, or data as the application stores it. |
| Required | Flag | The field is mandatory; the screen will not save without it. |
Notation used throughout this manual