Skip to content

Localization and Lookups ​

Backlog fieldValue
Story IDAP-SHR-002
EpicShared Platform
Story typeBusiness workflow
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 operational users, I want to receive localized labels and controlled lookup values so that forms use consistent business terminology and valid choices.

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 ​

Culture and authorized tenant/module context are required.

Optional or conditional ​

Search/filter and fallback culture are optional.

Action behavior ​

Lookup/localization reads are side-effect free and return active values unless history explicitly requests inactive.

Blocking rule or downstream effect ​

Stable IDs/codes remain language-independent.

Internal Documentation — Microtec