RMA Staff
Overview
RMA Staff is the branch-staff build of the entity-facing RMA screen set whose head-office build is RMA HQ. Staff raise a return for the items a customer brings back — serial number, return type, reason — and head office approves each item; the supplier then accepts or rejects the approved items in RMA Supplier. The state lives in line-level extension rows on a generic document, described on the RMA HQ page.
It is not the Internal RMA applet, which is a different bundle with its own repository and a full page.
rma-staff-applet/prod/rma-staff-applet-elements.js has no source repository in any
organisation this documentation server can read (checked 2026-09-16). This page documents the
registry row, the two client-side permissions seeded for it, the backend it shares with RMA HQ and
the issues filed against it — and no screen, field or setting, because none has been read.Where it fits
| Registry | RMA_Staff · name RMA Staff · type TNT-APPLET · ACTIVE · row created 2025-09-25 |
| Route | applet/tnt/wavelet/rma-applet and custom element rma-applet-elements- — identical to RMA HQ; only the bundle differs. A tenant that assigns both to one user is assigning two builds of one screen set |
| Upstream | The sale the item came from; the customer who brought it back |
| Downstream | RMA HQ approval, then RMA Supplier |
Screens and menus
Not documented — no source read. Issues name an RMA listing, an Edit RMA module, an RGPL note module, and a View Request button; see RMA HQ for the shared modules.
Configuration
Before you can use it
See RMA HQ — Before you can use it; the builds share a backend.
Applet settings
No source read (bundle repository not found, 2026-09-16). Not documented.
Feature visibility / permissions
Two client-side permissions are seeded for this code in bl_applet_client_side_perm_dfn — the only
seeded rows in the whole RMA HQ / Staff / Supplier family:
| Permission | Seeded | What the name and its issue say it does |
|---|---|---|
SHOW_VIEW_REQUEST_BUTTON | 2024-02-01 | Shows the View Request button. Filed as “to hide the view request / grant by permission” (blg-intranet#3927, closed) — a per-role reopen of a hidden button, the SHOW_* pattern used across the product |
SHOW_APPROVAL_BUTTONS | 2024-07-03 | Shows the approval buttons — the HQ-side action — to a role on the staff build |
Grant them on Settings → Client-side permission listing in this applet. They are not seeded for
RMA_HQ or rma_supplier, so the same buttons cannot be reopened per role there.
Fields
Not documented — no form model read. The line-level extension rows the backend reads
(serial_number, rma_type, return_reason, rma_itm_hq_approval, rma_itm_supplier_acceptance,
consignment_number) are tabulated on the RMA HQ page.
Lifecycle and effects
Same document and the same extension-row state machine as RMA HQ. Both RMA document types the
backend declares (INTERNAL_SALES_RMA, INTERNAL_PURCHASE_RMA) are 0 / 0 — every line carries
quantity signum 0 and amount signum 0, so raising or approving a return here moves no stock and
posts nothing. Which type the build actually creates is not visible without the UI source.
Related applets
- RMA HQ — the head-office build of the same code.
- RMA Supplier — the supplier’s acceptance step.
- Rma Applet (Internal) — the service-note based RMA applet.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| The View Request button is missing for a role | SHOW_VIEW_REQUEST_BUTTON not granted to the role | Grant it under Settings → Client-side permission listing |
| Approval buttons are missing for a role | SHOW_APPROVAL_BUTTONS not granted | Same |
| Edit RMA / RGPL note module does not work | Open defects against both builds (blg-intranet#4424, #4425) | No workaround recorded |