Releases
Review and promote application changes across environments
Build in development, compare with the next environment, choose what goes, and promote it as a reviewed release. Rollback is on the roadmap, not available yet.
Environments and releases
The problem
Changing the app your customers use this morning is risky
Editing production by hand, or moving changes as exports nobody can read, leaves no clear record of what changed.
By hand
- A checklist of what was changed
- Choice lists re-entered in each environment
- Database scripts run from someone’s laptop
A release on TechAppForce
- One object you can inspect
- You see what is in it
- And what it will change, before it changes anything
How we solve it
Add a new approval rule in development, check it in QA, then release it to production with every change visible.
Follow one change: a customer needs finance to approve any order over 10,000. The reviewer sees exactly what changes, and nothing else.
- Order.ApprovalLimit field
- Approval step: Finance, over 10,000
- Order form: Approval section
- Role: Finance approver
- Invoice dashboard (in progress)stays behind
- + Order.ApprovalLimit
- + Approval step: Finance
- ~ Order form
- + Role: Finance approver
- 014_set_default_approval_limit
- Developmentv15 built
- QAv15 testedfrom TAF Studio
- Productionv15 livea separate, deliberate step
What you get
What a release carries
Everything the change needs to work in the next environment. Open a tile for detail.
v15A configuration version
The changes you selected become a new version of the app in the target environment. Items you did not select stay as they were.
parents → childrenReference data, in a safe order
Choice lists and lookup tables move with the release, parents before children, so references never break halfway.
appliedfailedpendingMigration scripts
Scripts run in the target environment, each tracked as applied, failed or pending.
Only what you chose
Half-finished work in development does not leak into production.
+ added− deletedA readable diff
Added, updated and deleted items, for configuration and data, so someone who did not build the change can check it.
.csCode in the same release
Custom scripts are part of the configuration, so a rule written in code moves with the screens it belongs to.
Use cases
Examples you can build
Example apps, each with its records, approvals, screens and reports.
- Purchase and expense approvalsApprovals and back office
- Vendor onboardingApprovals and back office
- CRM-style sales pipelineCustomers and sales
- Intake forms with reviewCustomers and sales
- Admin tools on an existing databaseData and IT
- Scheduled operational reportingData and IT
What each example covers
- Purchase and expense approvals: Route every purchase request and expense claim to the right approvers, with deadlines.
- Vendor onboarding: Collect supplier documents, review them properly, and approve new vendors with a record.
- CRM-style sales pipeline: Configure leads, accounts and deals around how your team actually sells.
- Intake forms with review: Forms that ask the right questions, then route each submission to the right reviewer.
- Admin tools on an existing database: Put screens, roles and change history on tables you already have.
- Scheduled operational reporting: The reports people ask for every week, built once and sent on time.
See TechAppForce on your own use case
On a call we make a change on a real app, show you the diff, and promote it.