Skip to content

Bulk Changes

Source PDF page(s): 57 (of raw/specs/MMS features v2.5.pdf)

Summary: Centralized bulk configuration management — apply template amendments and assign base templates to large groups of devices/merchants in controlled, scheduled deployments.

Owner: Martin (project lead — confirm feature owner)

Status: in-development — EST 2026-05-31

Delivery map (web)

FE (mms-fe) BE (cloudbanking)
Routes / screens (to fill) —
API calls bulk template amendment / assign endpoints defines amendment + base-template-assign APIs and jobs
Figma (to link Bulk Changes / Template Amendments / Base Template Assign frames) —
OpenProject (FE WP ID(s)) (BE WP ID(s))

Why

Configuration changes need to be applied consistently across many devices and merchant environments without per-device edits. See MMS Features v2.5 §8.

What

Template Amendments (p.57) — In Progress (EST 2026-05-31)

  • Create, edit, activate, deactivate, and remove template amendment configurations.
  • Manage amendment rules for application parameters, transaction settings, fees, limits, and device behaviors.
  • Apply bulk configuration changes to groups of devices or merchant environments via centralized templates.
  • Support scheduled updates and controlled deployment to target devices.
  • Device filtering and saved filters to simplify device selection and amendment targeting.

Base Template Assign (p.57) — Design UI (EST 2026-05-31)

  • Assign base templates in bulk. (UI design stage; details not yet specified in the source.)

Out of scope

Creating the base templates themselves — see app-manager (Assign Applications → base templates).

Acceptance criteria

Product (E2E)

  • [ ] Bulk configuration changes can be safely applied to a selected group of devices/merchants and verified on staging.

Frontend

  • [ ] CRUD + activate/deactivate UI for template amendment configurations.
  • [ ] UI for configuring amendment rules (app params, transaction settings, fees, limits, device behaviors).
  • [ ] Flows for scheduling bulk deployments, selecting devices via filters/saved filters.
  • [ ] Base Template Assign UI implemented (per design).

Backend

  • [ ] APIs and jobs for CRUD + activate/deactivate template amendments.
  • [ ] Engines for applying amendment rules to devices/merchants.
  • [ ] Scheduling, execution, and status tracking for bulk deployments.
  • [ ] APIs for Base Template Assign (bulk assignment of base templates).

Done together

  • [ ] End-to-end bulk change executed on staging (amendment + base template assign) and verified on sample devices.

Linked pages

Status history

  • 2026-05-27 — ingested from features doc v2.5; Template Amendments "Progress - EST 05/31/2026", Base Template Assign "Design UI - EST 05/31/2026" → in-development, target 2026-05-31