Modules
Each module is a part of the product a workspace can switch on, with its own endpoints, scopes and concepts. All five are written.
A module is configured on the workspace, not requested by a client. GET /capabilities reports which are on, and an endpoint whose module is off refuses with feature_disabled rather than pretending to work.
| Page | What it covers |
|---|---|
| Custom objects | Adding objects and fields at runtime, the key rules, and how a relation makes a related list |
| Commerce and CPQ | The policy, the pricing profile, price books and purchase costs, and quote versions |
| Approvals | Definitions of up to three stages, what a submission pins, and why one rejection ends it |
| Reports and dashboards | What a definition holds, previewing against saving, and widget visibility |
| Document generation | Templates, the queue and its statuses, and the short-lived download link |