Appearance
AppsPortal.Apis Traceability
Backend ownership map
| Story module | Primary controller area | Application area |
|---|---|---|
| Shared Platform | Controllers root | Core, BackgroundJobs |
| Accounting | Controllers/Accounting | Accounting |
| Finance | Controllers/Finance | Finance |
| General Settings | Controllers/GeneralSettings | GeneralSettings |
| Purchase | Controllers/Purchase | Purchase |
| Sales | Controllers/Sales | Sales |
| Fixed Assets | Controllers/FixedAssets | FixedAssets |
| Van Sales | Controllers/VanSales | VanSales |
| HR | Controllers/HR | HR |
| Dynamic Templates | Controllers/DynamicTemplates | DynamicTemplates |
Coverage rules
- Closely related controllers are represented by one business feature when they form a single user workflow. For example, account section, account type, account level, and chart controllers are covered by Chart of Accounts.
- Separate reports are grouped only when they serve one business decision area. Their controller-level behavior should be expanded when detailed report specifications are requested.
- Infrastructure-only endpoints such as tenant resolution, translation, lookups, authorization, and transaction logs are covered by Shared Platform stories.
InventoryControllercalls within AppsPortal.Apis are cross-module integration capabilities. The full Inventory business workflow is owned by the dedicated Inventory story set.- MFE pages remain the source of truth for screen boundaries; API commands remain the source of truth for server-side state transitions and invariants.