For AL developers
Start from a written requirement and an approved design.
A requirements document and a design the client has approved come first. Then the extension is built to written coding standards.
Where does your work start?
- Does it start with a clear requirement, or a vague one?
- Did the client agree what it should do before you wrote the first object?
- Who tests it against what was agreed?
How it works, in developer terms
- 01
Clarify, structure, document
Needs are clarified and written as a requirements document that the client corrects and approves.
- 02
Standard fit
We research how standard Business Central handles the need. An extension adds to Business Central without changing the standard product, and we build nothing that bypasses its security or licensing.
- 03
Design approval
The client reviews an illustrated storyboard and a functional document. Nothing is built until a version is approved. Acceptance criteria are produced with the design.
- 04
Build
The extension is built to our written AL coding standards.
- 05
Test and review
The extension is tested against the acceptance criteria in the approved design. A separate AI reviewer that did not write it checks the work against the approved design and the standards.
- 06
Sandbox install
Installed in the client's sandbox first, with the CRONUS sample company used for design and testing, never live records. Production follows once the client accepts.
What is received
- The client receives a functional document in plain language and an HTML5 training manual.
- The technical details stay on our side.
- If you want the source code, it can be bought for an app after it is delivered, under a separate licence. Downloading the app package is available only to customers who have bought the source code for that app, after accepting the licence terms.
- Business Dynamics Pro keeps the intellectual property. The customer receives a licence to use the extension in the environments it names. The source is a licence, not a transfer.
What you do and what we do
| You | We |
|---|---|
| Read the functional document the client receives. | Write the requirement, check standard Business Central, produce the design. |
| Test in the client's sandbox before production. | Build to written standards, test against acceptance criteria, separate AI review. |
| Buy the source if you want to read or maintain it. | Install in the sandbox first and production after acceptance. |
Objections and answers
Will the AL follow proper standards?
The extension is built to our written coding standards and checked by a separate AI reviewer. Source can be bought after delivery if you want to read it.
Can I see the code before the client installs?
Not by default. The client reviews the storyboard and the functional document; the technical details stay on our side. Source is a separate purchase after delivery.
Is this meant to replace developers?
We make no such claim.
Will it clash with our other extensions?
An extension adds to Business Central without changing the standard product. You test fit in your sandbox. We make no compatibility guarantee.
Questions
Could the AI write something that bypasses permissions or licensing?
We do not build things that bypass the standard product's security or licensing. The reviewer checks against the design and our standards, and the client tests in a sandbox.
Who owns the extension?
Business Dynamics Pro keeps the intellectual property. The customer gets a licence for the environments it names.
Can I get the .app file?
Only a customer who has bought the source code for that app can download the app package, after accepting the licence terms.
What does the client see?
A storyboard and a functional document. The technical details stay on our side.
Is the review done by a person?
No. It is a separate AI reviewer that did not write the extension.
How long does a build take?
It depends on the size and the number of review rounds. We give no turnaround time.
See how the design review works
A written requirement, an approved design, then the build.
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.