Intranet requests

This page describes the requests sub-module in src/cluster_erp/modules/intranet/requests/. It is a generic engine for employee requests: the organisation defines request types with their own form fields, and employees file requests that move through submission, decision, and fulfilment (src/cluster_erp/modules/intranet/requests/services.py:1-2). Leave has its own sub-module; see leave.

Scope and source¶

• Defined in: src/cluster_erp/modules/intranet/models.py (IntranetRequestType, IntranetRequest), requests/services.py, requests/routes.py, requests/schemas.py, requests/metadata.py, and requests/seeds.py.
• Count: 2 tables, 11 routes in requests/routes.py, 5 ActionMeta entries in requests/metadata.py.

Fields¶

The categories are leave, advance, expense_claim, document_request, equipment, access, travel, and general (src/cluster_erp/modules/intranet/models.py:104-113). form_schema is a list of fields with a key, a label per language, a field type, and a required flag; the answers are stored in payload (src/cluster_erp/modules/intranet/requests/seeds.py:14-27). The module seeds six request types on start when their codes are missing: advance, expense_claim, document_request, equipment, access, and general (src/cluster_erp/modules/intranet/requests/seeds.py:10-136, src/cluster_erp/modules/intranet/module.py:97-131).

Statuses and actions¶

A request is draft, submitted, in_review, approved, rejected, cancelled, or fulfilled (src/cluster_erp/modules/intranet/models.py:114-122). The service allows these transitions (src/cluster_erp/modules/intranet/requests/services.py:48-54):

stateDiagram-v2
 [*] --> draft
 draft --> submitted: submit
 submitted --> approved: approve
 in_review --> approved: approve
 submitted --> rejected: reject
 in_review --> rejected: reject
 approved --> fulfilled: fulfill
 draft --> cancelled: cancel
 submitted --> cancelled: cancel
 in_review --> cancelled: cancel

In prose: a request is drafted, submitted, decided, and, when approved, fulfilled. It can be cancelled before a decision. No transition in the service writes in_review.

Rules¶

• Every field marked required in the type's form_schema must have a non-empty answer. The check runs on create, on update of the payload, and again on submit (src/cluster_erp/modules/intranet/requests/services.py:26-46, src/cluster_erp/modules/intranet/requests/services.py:224, src/cluster_erp/modules/intranet/requests/services.py:248, src/cluster_erp/modules/intranet/requests/services.py:281-287).
• On submit, the service asks GetApprovalChainForAction for the resource intranet_request. With a chain and a known actor it calls SubmitForApproval and stores the approval request id (src/cluster_erp/modules/intranet/requests/services.py:289-309).
• Approve and reject record the decision time, the decider, and an optional note. Fulfil can store a result document id (src/cluster_erp/modules/intranet/requests/services.py:310-321).
• Approve, reject, and fulfil notify the requester in-app and by e-mail with the i18n key intranet.notif_request_ plus the new status (src/cluster_erp/modules/intranet/requests/services.py:322-339).
• The action route lets a caller act only on requests in their scope; Approve, Reject, and Fulfill also need intranet_request.approve (src/cluster_erp/modules/intranet/requests/routes.py:181-203).
• Creating a request for another person needs intranet_request.read_all, and the named party must be an active employee (src/cluster_erp/modules/intranet/requests/routes.py:132-150).
• A subscription to ApprovalCompleted was not found in the intranet package; decisions are recorded through the action route.

Routes¶

Terms introduced¶

Related pages¶

• Intranet module
• Leave
• Approvals and approval chains

Verified against commit 92f8051 on 2026-11-13.