TechAppForce

Data and IT

Admin tools on an existing database

Put screens, roles and change history on tables you already have.

Book a demoSee how it runs
  1. Requested
  2. Approved
  3. 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.
Who feels it: IT and engineering teams who own a database but not a usable interface to it

How it runs on TechAppForce

A day with it, step by step

Amber steps wait in a person's work inbox; everything else moves on its own.

  1. 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.
  2. Decide who sees whatThe team creates roles for support and finance, each with the screens it needs.
  3. A customer callsA support agent filters the orders grid by the customer’s email, finds the duplicate order and requests a refund adjustment.
  4. Approved and appliedApprove or rejectThe team lead approves. The existing refund procedure runs, and the change is kept on the order’s history.
  5. Released properlyThe admin tool is promoted from development as a release, so production gets exactly what was reviewed.
Illustration. The organisation and people are invented.

What gets configured

Settings you can read, change and release

No code for any of this, unless a rule truly needs it.

Records 4

  • Existing tables and views, registered as entities in development0 fields + history, files, comments
  • Customer account5 fields + history, files, comments
  • Order5 fields + history, files, comments
  • Adjustment4 fields + history, files, comments

Stages 3

  1. Requested
  2. Approved
  3. 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

Bring your version of this.

A change a few months in is a reviewed release, not a rebuild. We will configure your version with you in a demo.

Book a demoAll use cases

Release: Registered: orders table

Screens
Added: + List Orders by status
Added: + Detail Order and lines
Fields
Added: + Refund reason (lookup)
  1. Developmentmake the change
  2. QAreview the diff, test it
  3. Productionpromote the release
Illustration.