How we review
Who checks the work, and what you check yourself
AppoGen uses AI to help with research, design, building and testing. So it is fair to ask who checks the result. Here is the plain answer, in four checks. Two are ours. Two are yours.
Four checks, as designed
- 01
You approve the design first
Before anything is built, you read the design as a storyboard, comment on any scene, and approve one version. Nothing is built until you approve.
- 02
The work is built to written standards and tested
We build the extension to our written coding standards. We test it against the acceptance criteria in your approved design, and fix what fails before anything reaches you.
- 03
A separate AI reviewer checks it
The work is reviewed by a separate AI reviewer that did not write it, and checked against your approved design and the standards.
- 04
You test it in your sandbox
We install it first in your sandbox, a safe copy of your system, where you test it. Production comes after you are happy, and only with your consent.
What "a separate AI reviewer" means
- The reviewer is a separate AI. It is not the one that built the extension, so it is not marking its own work.
- It checks the work against two things: the design you approved, and our written standards.
What this does not mean
- We do not promise bug-free software or a guarantee that it works. Review and testing are checks, not a promise that nothing is wrong.
- For 30 days after installation we fix anything that does not match the design you approved.
- We have not yet delivered a customer project, so there are no review results to show. What you see here is how the process is designed.
Want to see the design review?
Read how the design is reviewed, or start a request.
Microsoft Dynamics 365 Business Central is a product of Microsoft. AppoGen is an independent service and is not affiliated with, endorsed by or sponsored by Microsoft.