Releases and change control
During the Embedded Build, working software reaches the people who use it every week. This page covers how a change gets from our forward-deployed engineers to your order desk without surprising anyone: the test and production environments, the weekly release, who approves what, how a release is rolled back and what happens when a change touches the ERP.
Two environments
Section titled “Two environments”| Test | Production | |
|---|---|---|
| What it is for | Trying a change before anyone depends on it | Real work |
| Who works in it | Our engineers, the workflow owner and the people they ask to try a change | Your people and your agents |
| ERP it connects to | A test copy of your ERP | Your live ERP |
| Sends nothing to real customers or suppliers | Sends real email | |
| Data | A copy of your real data | Your real data |
Our engineers work to three rules.
- Nothing reaches production without passing through test.
- Test never writes to the live ERP and never emails a real customer or supplier.
- Test uses a copy of your real data, because made-up data hides the exceptions that matter. The copy is kept in the same agreed location and under the same access rules as production.
If your ERP has no test copy, we record that in the Systems and Data Audit and agree with your IT team how write-backs get tested before the first one goes live.
The weekly release
Section titled “The weekly release”Embedded Build describes how the week runs for your team. This is the path one change takes through it.
- Plan. Our engineers and the workflow owner agree what changes this week, based on last week’s measurements and the Automation Backlog.
- Build. Our engineers make the change and run it against recorded real work: last month’s purchase orders, not invented ones. A change to an agent is tested the same way, and its results are compared with the version it replaces.
- Try it in test. The workflow owner, or someone they name from the order desk or the purchasing team, tries the change in test on real examples.
- Approve. The workflow owner signs off. Without that, the change does not go to production.
- Release. The change goes to production on a day and at an hour agreed with the workflow owner, away from the desk’s busy times and from month-end close. A short note in plain language says what changed, for whom and what to watch for.
- Watch and measure. Our engineers watch the first real work go through the new version with the people who use it. From then on, the workflow’s measurements count against the new version.
A fix for something broken in production does not wait for the next weekly release. It takes the same path, faster, and is recorded the same way.
After the build, under Operate & Automate, every change still takes this path.
Who approves what
Section titled “Who approves what”| Change | Who approves |
|---|---|
| A screen, queue or rule in a workflow | The workflow owner |
| An agent’s instructions or rules | The workflow owner |
| An agent’s limits | The workflow owner. Every change is recorded. |
| A workflow moving up a level on the autonomy ladder | A promotion review, ending in the workflow owner’s sign-off |
| A workflow moving down a level | The workflow owner, at once, with no review |
| A change of AI model or of its provider | Your IT manager agrees first, then the workflow owner signs off |
| Anything that touches the ERP | Your change control, as well as the workflow owner |
| The day and hour of a release | The workflow owner |
Our engineers do not approve their own changes into your production. Every release is recorded: what changed, who approved it, when it went live and how it was tested.
Rolling back
Section titled “Rolling back”Every release can be undone. The previous version is kept, and our engineers put it back when the workflow owner or your IT manager asks. The old way of doing the work also stays available until the workflow owner retires it, so the desk always has a way to work. Three points matter.
- Rolling back software does not undo transactions. Orders or invoices already written to the ERP stay there. If a release wrote something wrong, the record of write-backs shows which transactions it touched, and they are corrected in the ERP with the ERP’s own functions: cancel, reverse, credit.
- Changes to stored data are made so the previous version still works. If a change cannot be made that way, we say so before the release and take a backup first.
- For an agent, the fastest way back is not a release. The stop switch halts the agent at once, and the workflow owner can move the workflow down a level without waiting for a release. The fix then follows the normal path.
Changes that touch the ERP
Section titled “Changes that touch the ERP”A change touches the ERP when it does any of these:
- adds or alters a write-back
- asks for new access for a person or an agent
- needs something created on the ERP side, such as a view, an export or an import job
- needs a change inside the ERP itself, such as a new field.
These changes go through your change control, not ours.
- Our engineers write the request in the form your IT team uses. It says what changes, why, what it touches, how to test it and how to undo it.
- Your IT manager or ERP administrator approves it, like any other ERP change.
- Your ERP administrator or your ERP partner makes any change inside the ERP. Our engineers do not change your ERP’s configuration.
- The ERP change and the software that depends on it are tested together before either reaches production.
- Both go live on your calendar: not during month-end close, a physical inventory or a freeze you have declared.
If you have no formal change control today, we still work to a minimum: a written request and a named approver for every change that touches the ERP.
It works in the other direction too. Tell us before you upgrade or patch the ERP. We run the attachment’s tests against the upgraded test copy first, so a changed screen or field is found there and not on your order desk.
Working with your IT team and ERP partner covers who owns what between our engineers, your IT team and your ERP partner.