Approval steps for Business Central, designed with you first
Who must say yes before an order, a payment or a change goes ahead? Describe your approval rule in plain words. AppoGen shows you the design before anything is built.
The problem
Approvals live in email, in memory or in a spreadsheet. A manager sees a large order only after it has gone out. A change to a vendor's bank details has no second pair of eyes. You want the rule inside Business Central, so the right person decides at the right moment, and the system records who decided and why.
How an extension helps
An extension can add an approval step to a process without changing the standard product. It can send an item to a named approver, pause the next step until a decision is made, and keep a record of the decision. Approval rules usually depend on things like amount, department or customer, so the design needs to say exactly which rule applies when.
How AppoGen handles the request
You describe the rule: who approves, above what amount, and what happens if they say no. Plain words are enough.
We ask about anything unclear, for example what happens when the approver is away. Then we write the need down as a requirements document for you to approve.
We check standard Business Central first. It already has approval features, and the assessment names what is supported and what really needs extending.
You review a storyboard. In the sample storyboard, the approver's scene shows a choice of Approve or Reject, with a reason, or asking for more information. Your own storyboard is shaped by your need. You comment, and each round gives a new version.
Quote and build. The price follows the size of the approved design. Approvals make a job larger, and the breakdown says so in plain words. You accept the quote and pay 50 % to start.
Test, review, install. The extension is tested against your acceptance criteria and reviewed by a separate AI reviewer that did not write it. Then it goes to your sandbox, and to production once you accept.
What you receive
A requirements document, a storyboard with before-and-after steps, a functional document, an HTML5 training manual with the approver's daily tasks, and the installed extension.
An example
Suppose purchase orders above a set amount need the department manager's approval. The design would set approval levels by amount and department. It would send each order to the right approver and remind them if it waits. It would hold the order back from the supplier until it is approved. It is a standard-size job: several new screens, a few changed ones, and an approval. This is an illustration, not a delivered app.
Questions
Can I use the approvals already in Business Central?
Maybe. We check standard Business Central first and tell you honestly if a standard feature fits.
Can the rule depend on amount and department?
The design can describe it. You approve the exact rule in the storyboard and functional document before the build.
Who sees the decision record?
The design says who sees what. You confirm it when you review.
Does an approval step make the price higher?
Approvals are one of the things that make a job harder, and the breakdown shows it in plain words.
Can I change the rule later?
A later change is a change request, designed with you and priced only on the difference, within your plan's allowance.
How do we try it safely?
In your sandbox first, ideally with the CRONUS sample company.
Keep reading
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.
Describe the need. See the design before the build.
You approve the design before anything is built.