Admin tools on an existing database
Put screens, roles and change history on tables you already have.
- Requested
- Approved
- AppliedDone
PassedWaits for a personEvery move is kept in the record's history
The problem
What goes wrong today
Today
Support and operations staff need to look up and correct data in a production database, so they ask engineers to run queries for them. Building an internal admin tool is always next quarter’s job, and direct database access is a risk nobody likes.
How It Works
How this use case runs, step by step
Amber steps wait for a person's decision; everything else moves on its own.
- Point it at the databaseA subscription box company connects its development environment to a copy of its PostgreSQL database, and compatible tables are registered as entities with list and detail screens.
- Decide who sees whatThe team creates roles for support and finance, each with the screens it needs.
- A customer callsA support agent filters the orders grid by the customer’s email, finds the duplicate order and requests a refund adjustment.
- Approved and applied Approve or rejectThe team lead approves. The existing refund procedure runs, and the change is kept on the order’s history.
- Released properlyThe admin tool is promoted from development as a release, so production gets exactly what was reviewed.
Product Capabilities
What you configure in this app
Mostly configuration. Rules that configuration cannot express are written in C#.
Records 3
- Adjustment4 fields + history, files, comments
- Customer account5 fields + history, files, comments
- Order5 fields + history, files, comments
Stages 3
- Requested
- Approved
- Applied
Automatic 3
- WorkflowAn approved adjustment runs a stored procedure you already have
- CodeA C# record hook blocks changes that break a rule specific to your business
- NotifyThe requester is notified in-app when their correction has been applied
Screens and reports 4
- Data grid over each registered table, with filters and CSV export
- Detail screens with related records from lookups
- Corrections applied this month, by reason, in Excel
- Open orders by status, as a CSV export of the grid
Who approves, in detail
Data corrections such as refunds or plan changes go to the team lead role before they are applied, and corrections above a set amount also need finance.
When the rules change
See TechAppForce on your own use case
Bring your own version of “Admin tools on an existing database” and we will model its records, stages and approvals with you. A change a few months in is a reviewed release, not a rebuild.
Release: Registered: orders table
Screens
Added: + List Orders by status
Added: + Detail Order and lines
Fields
Added: + Refund reason (lookup)
- Developmentmake the change
- QAreview the diff, test it
- Productionpromote the release