AI Requirements Bridge — Help

What the app does

The AI Requirements Bridge turns rough feature ideas into complete, developer-ready specifications — directly inside Business Central:

• Capture a requirement with a title, a free-text description and a category.
• Refine it in an AI-guided Q&A dialog: the AI states one assumption and asks one question per round, and scores how complete the requirement is after every answer.
• Generate a consistent set of documents once the quality gate is passed: requirements list, solution design, technical architecture, acceptance criteria, effort estimate, developer notes and release notes — each as Markdown and PDF, ready to hand to any development team or partner.

Getting started

1. Install the app from Microsoft AppSource into your Business Central environment.
2. Assign licenses in the Microsoft 365 admin center (Billing → Licenses) to every user who should create requirements or generate documents. Users without a license can read everything but cannot make changes.
3. Assign permission sets in Business Central (page Users): AI Req. Bridge - Reader for read-only users, AI Req. Bridge - Creator for users who work with requirements, AI Req. Bridge - Bridge Admin for the person who maintains the setup.
4. Activate the Copilot capability: open the page Copilot & agent capabilities, and activate CDM Requirements Bridge. Depending on your environment's Azure region you may also need to allow data movement across geographies. See the Copilot capability page for details on data handling and billing.
5. Set up AI billing: AI consumption is billed by Microsoft to your organization (Copilot credits or pay-as-you-go). Configure this in the Business Central admin center under Copilot consumption billing. Without a billing setup the AI dialog cannot run.
6. Open the setup page: search for AI Requirements Bridge Setup. The app initializes sensible defaults on installation — check the number series for requirements, the score threshold (default 85) and, optionally, extra context that is passed to the AI with every request (for example a short description of your company and system landscape).

Working with requirements

Open Requirements from the role center or via search. Create a new requirement with a title, description and category. Optionally link Business Central objects (tables, pages, codeunits, reports) or master records (customers, vendors, items) to the requirement — the AI uses the object metadata to ground its questions and the generated documents. Only metadata is shared with the AI, never the content of master records.

Every requirement moves through a fixed lifecycle: New → In Q&A → Ready for Synthesis → Documents Generated → …. Each status change, field change and dialog round is recorded in an immutable history on the requirement card.

The AI dialog

On the requirement card, choose Start AI Dialog. The AI reads the description and any linked objects, then states one assumption and asks one question.

Answer in one of three ways: Confirm the assumption, Correct it (with free text), or Extend it (with free text). Free-text answers can be up to 2,000 characters.

After every answer the AI scores the requirement's completeness (0–100). When the score reaches the threshold from the setup (default 85), the requirement becomes Ready for Synthesis.

The dialog is limited to 10 rounds. If the threshold is not reached by round 10, the requirement is moved on anyway — you can always improve the description and run the dialog again later.

Tips for good results: write the initial description in the language you want the documents in — the AI mirrors your language. Mention the business problem, not just the desired feature. Link the objects the change is about; the dialog gets noticeably more precise.

Generating documents

1. On a requirement that is Ready for Synthesis, choose Generate Documents….
2. Select the document types you need. The dialog shows a token estimate per document.
3. The documents are generated one after another; progress is shown live. Each document is stored as Markdown and as a rendered PDF with your requirement number and version in the file name.

Documents are versioned: regenerating a document keeps all previous versions. You can open the Markdown in a built-in editor, make manual corrections and save them as a new version — later documents in the same set use your corrected content as context. The effort estimate document additionally stores story points and an hour range on the requirement.

Licensing and read-only mode

The app is licensed per user through Microsoft AppSource. Users with an assigned license have full access according to their permission sets. Users without a license see all requirements and documents in read-only mode — they cannot create or change anything. This also applies after a subscription ends: your data stays readable and exportable in your environment.

Support

Please include your Business Central version, the app version (page Extension Management) and, if possible, the requirement number and a screenshot with your request.