Skip to content

Templates and Core Reporting

Backlog fieldValue
Story IDAP-SHR-003
EpicShared Platform
Story typeReport
Review statusDraft - business analyst and business owner review required
Source evidenceAppsPortal.Apis controller, application command/query handlers, validators, domain entities, and matching MFE workflow where available
Last source review2026-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

  1. Only authorized users can view or execute the feature's actions.
  2. Required business data, active dependencies, tenant/branch scope, and current document state are validated.
  3. Invalid requests return actionable validation errors without applying a partial change.
  4. Search, list, view, print, and export operations use the same authorized business scope.
  5. Material create, edit, status, approval, posting, reversal, and integration actions are auditable where applicable.
  6. 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.

Internal Documentation — Microtec