Appearance
Templates and Core Reporting
| Backlog field | Value |
|---|---|
| Story ID | AP-SHR-003 |
| Epic | Shared Platform |
| Story type | Report |
| Review status | Draft - business analyst and business owner review required |
| Source evidence | AppsPortal.Apis controller, application command/query handlers, validators, domain entities, and matching MFE workflow where available |
| Last source review | 2026-07-10 |
User story
As administrators, I want to configure screen/print templates and generate standardized reports so that documents follow company policy and remain reproducible.
Acceptance criteria
- Only authorized users can view or execute the feature's actions.
- Required business data, active dependencies, tenant/branch scope, and current document state are validated.
- Invalid requests return actionable validation errors without applying a partial change.
- Search, list, view, print, and export operations use the same authorized business scope.
- Material create, edit, status, approval, posting, reversal, and integration actions are auditable where applicable.
- Financial or stock effects are applied atomically and no more than once.
Business rules
Required
Authorized report/template identity and valid parameters are required.
Optional or conditional
Format, language, branding, filters, and layout variant are optional.
Action behavior
Generate/print/export are read-only snapshots and must not change source status.
Blocking rule or downstream effect
Templates cannot bypass data authorization.