Glossary: extension terms in plain words

An add-on that gives Business Central a new feature without changing the standard product.

It can add a field, a rule, an approval step, a report or a link to another system. It can be added, updated and removed on its own.

We build things that add to or change how your system works. We do not build anything that bypasses its security or licensing.

Related: app, AL, standard product

Another word for an extension, as a package that is installed.

You will see both words. An app is the installable form of an extension.

Related: extension, install

The programming language used to write Business Central extensions.

You do not need to know it to ask AppoGen for an extension.

Related: extension, codeunit

Where Business Central stores one kind of record, such as customers or sales orders.

A table holds fields. An extension can add fields to an existing table without changing the standard table.

Related: field, table extension

A part of an extension that adds fields to an existing table.

The standard table stays as it is. Your new field sits beside it.

Related: table, field, page extension

One piece of information in a record, such as a customer's name or a weight limit.

Adding a field is one of the common things an extension does.

Related: table, table extension

A screen you see in Business Central, such as a list or a card.

Pages are what people use each day. An extension can change a page, for example by showing an extra field.

Related: page extension, role center

A part of an extension that changes an existing page.

For example, it can show an extra field or add a button, and the standard page stays as delivered.

Related: page, action

A button or menu item on a page that does something.

An extension can add an action, such as a button to send an order for approval.

Related: page, page extension

A container for business logic written in AL, such as a rule that runs when an order is released.

Rules in an extension are written in codeunits. You describe the rule in plain words; the codeunit is how it is written.

Related: AL, event

A point in the standard process where an extension can add its own logic.

This is one way an extension adds to the standard product without editing it.

Related: codeunit, extension

A printed or on-screen summary of data, such as a list of orders on hold.

A new report is one of the things that counts toward the size of a design.

Related: page

A defined way for another system to read or send data to Business Central.

An extension can add a link to another system. A link to another system makes a job larger when it is priced.

Related: integration

A link between Business Central and another system.

It makes a job larger when priced, because it is one of the things that makes a design harder.

Related: API, background job

A task that runs without a user, for example every night.

A nightly reminder about service contracts that are about to end is an example. A background job makes a job larger when priced.

Related: integration

A named group of permissions that decides what a user may read, change or run.

We build nothing that bypasses a system's security. As designed, the training manual explains the permissions for each extension.

Related: role, user

A job someone does, such as sales order processor.

A role decides what a person sees and may do. We ask for a role and user count when you describe your need.

Related: permission set, role center, user

The home page a user sees for their role.

It is the first screen a person opens each day.

Related: role, page

A person who signs in to Business Central.

The request asks how many users will use the extension, and in which roles.

Related: role

Recording a transaction in the books, such as an invoice.

A change that touches posting makes a job larger when it is priced.

Related: sales order, release

A document recording what a customer has ordered.

A common request is to stop shipping when a customer is over a credit limit.

Related: purchase order, release, credit limit

A document recording what a company orders from a supplier.

A common request is to route big purchase orders to the right manager.

Related: sales order, approval workflow

Marking a document as ready for the next step, such as shipping.

Many rules hook in at release, for example a check or an approval.

Related: sales order, approval workflow

A set of steps that sends an item to a named person for a decision before it can go on.

Standard Business Central already has approval features, and an extension can add rules to them. We check how the standard product handles your need before building anything custom.

Related: approver, release

The person who decides on an item in an approval workflow.

In our sample storyboard the approver can choose Approve or Reject, with a reason, or ask for more information. The sample is an illustration, not a Business Central screen.

Related: approval workflow, storyboard

The most a customer may owe before further orders need attention.

A common request is to stop shipping to customers over a credit limit. How the standard product handles this depends on your version, so we check it first.

Related: sales order

A storage location in a warehouse.

A common request is to warn when a bin is over its weight limit.

Related: warehouse

A location where stock is stored and moved.

Warehouse checks are among the typical requests.

Related: bin

Business Central as delivered, without extensions.

An extension adds to it and does not change it. We research how it already handles your need so your extension fits the way the system works.

Related: extension, standard fit assessment

A numbered state of an extension, or of Business Central itself.

Business Central itself updates twice a year, so a delivered extension may need an upgrade later.

Related: upgrade, release of an app

Moving an installed extension to a newer version.

Later changes to a delivered app are upgrades, and they arrive in your sandbox first. As designed, updates are handled the same way as the first install.

Related: version, change request

Putting an extension into a Business Central environment.

As designed, we install it for you, first in your sandbox and then in production when you are happy.

Related: sandbox, production environment

A separate copy of Business Central, for example a sandbox or production.

Keeping them apart lets you test safely before real work is affected.

Related: sandbox, production environment

A safe copy of Business Central for trying things out.

As designed, we install first in your sandbox, where you test it. We recommend a dedicated sandbox with the CRONUS sample company.

Related: production environment, CRONUS

The live Business Central where real work is done.

As designed, production is installed only after you accept the sandbox install, with your consent.

Related: sandbox, install

The sample company that comes with Business Central, with made-up data.

We do not need your live data to design or test. As designed, the training manual's examples use the CRONUS sample company, never your records.

Related: sandbox, training manual

The right to use software.

For an extension we build, you receive a licence to use it in the environments you name. Business Dynamics Pro keeps the intellectual property.

Related: source code

The written AL code of an extension. You can buy it for an app after it is delivered.

It is bought under a separate licence. Buying it is what opens the app file download for that app.

Related: licence, app package

The installable file of an extension.

Downloading it is available only to customers who have bought the source code for that app. You accept the licence terms before you download.

Related: source code, install

What you tell AppoGen you need.

You describe it in a short wizard, with examples, optional files, and a role and user count, or talk it through with the requirements assistant. Sending a request does not by itself mean it will be built.

Related: wizard, requirements assistant

The short form that asks for your need, with examples.

You can add screenshots or files if you want to. You do not need technical words.

Related: request

The chat that proposes a solution in plain steps first and asks only what it must.

It is an alternative to the wizard. We ask about anything that is unclear.

Related: request, requirements document

Your needs, written down by AppoGen. You read it, correct it and approve it.

As designed, a copy is filed for you as your approved requirements document.

Related: request, design approval

A check of how standard Business Central already handles your need.

As designed, it names what is already supported and what genuinely needs extending, before anything custom is built.

Related: standard product

An illustrated walk-through of the new way of working.

It shows scenes with an illustrative screen preview, who does what, and the benefit. It is our own illustration, not a Business Central screen.

You can click any scene or field to comment. Each round gives a new version, and nothing is built until you approve one.

Related: design approval, before and after

Today's steps next to the new steps.

It helps you see what changes for the people doing the work.

Related: storyboard

Your sign-off on one version of the design.

Nothing is built before it. When you approve, you receive the functional document and a price based on the size of the design.

Related: storyboard, quote

A plain-language description of your extension, step by step.

As designed, you receive it when you approve the design. The technical details stay on our side.

Related: design approval, training manual

The checks in your approved design that the extension is tested against.

We test against them and fix what fails before anything reaches you.

Related: test

The build price, worked out by fixed rules from the size of your approved design.

Simple extensions usually cost USD 2,000 to 5,000, standard ones USD 5,000 to 12,000 and advanced ones USD 12,000 to 20,000 You see the price breakdown in plain words before you accept. You pay nothing for the build until you have seen the design and accepted a quote.

Related: price breakdown, custom quote

The plain-words explanation of your quote.

It is shown before you accept.

Related: quote

A quote we prepare after reviewing a design that is above USD 20,000.

We never quietly cap a price. Some requests are very large, and for those we may also tell you honestly that another route is better.

Related: quote

The first payment, 50 %, to start the build.

As designed, a build is paid in two equal parts.

Related: balance

The second payment, 50 %, before installation.

As designed, the balance comes before installation. It does not by itself open the app file download (that needs a source-code purchase).

Related: deposit

Writing your extension to our written coding standards.

It starts after you approve the design and pay the deposit.

Related: test, review

Checking the extension against your approved acceptance criteria.

As designed, we fix what fails before anything reaches you.

Related: acceptance criteria, review

A check by a separate AI reviewer that did not write the work.

As designed, it checks the work against your approved design and our standards.

Related: build, test

Installation by us in your sandbox, where you test it.

As designed, this comes before any production install.

Related: production install

Installation in your live system, after you accept the sandbox install.

As designed, it happens with your consent only.

Related: sandbox install

A single HTML5 page for each extension that explains how to use it.

As designed, it covers what the extension does, setup, permissions, daily tasks and troubleshooting, with illustrative screen previews that use the CRONUS sample company. You can open it offline.

Related: functional document, CRONUS

A numbered delivered build of an app.

Later changes are upgrades.

Related: change request, upgrade

A later change to an approved or delivered app.

We design it with you and price only the difference. It is paid the same way, with its own quote.

Related: release of an app, subscription

A monthly plan to design, document and change your apps, starting from USD 49.

As designed, it covers designing your apps with us, the functional document, and change requests to released apps, within your plan's allowance. It is separate from the cost of a build.

Related: trial, change request

A 14-day start that lets you try one design first.

If a subscription lapses, the apps you already have keep running, and design and change requests pause until it resumes.

Related: subscription

For 30 days after installation, we fix anything that does not match your approved design.

Our total responsibility never exceeds what you paid for that extension. A plain summary only; the legal wording is in the terms.

Related: build