What's New: Designing Generative AI Experiences (2024 Release Wave 1)
Design guidance for generative AI experiences in Business Central (2024 release wave 1): the three-stage prompt dialogue page type, undo and preview safeguards, human-in-the-loop design, and the Copilot menu. Demos cover suggesting sales lines and mapping e-document lines to purchase order lines.
- Introduction and balancing innovation with user experience
- Understanding AI and Copilot in Microsoft context
- Session agenda and AI inputs and outputs overview
- Demo: suggest sales lines with unstructured and structured data
- Prompt dialogue stages and output mode interactions
- Demo: map e-document lines with structured data flow
- High-level AI experience design and user trust concepts
- Two AI value propositions - action and insight
- Managing AI risks and responsible AI principles
- Preview and undo as core safeguards
- Prompt dialogue page type and AL structures
- Generation workflow, system actions, and prompt guidance
- Copilot menu, floating overlay, and dialogue integration
- Getting started, best practices, and session conclusion
Overview
The session explains how to design Copilot features in Business Central. It covers how AI is positioned as a collaborator with the user, how to build user trust, and how to manage AI risk with preview and undo. It separates two kinds of value: action (faster or more efficient work) and insight (getting to knowledge).
On the technical side, it introduces the prompt dialogue page type with input, generating and output modes, plus prompt options, system actions for generate and cancel, and the prompt guide. It also shows where Copilot actions appear: the Copilot menu on list pages, a floating overlay, dialogues and subpages. Demos include suggesting sales lines from free text and mapping e-document lines to purchase order lines.
Key points
- The prompt dialogue has three stages: input mode, generating mode and output mode. Input mode can be skipped when all needed data already exists, as in the e-document line mapping demo.
- Prefer structured data where you have it, since it can save clicks. Unstructured input adds uncertainty in interpretation.
- Undo principle: the system must provide a preview or a way to completely undo what AI suggested. Generated output must go only to temporary tables, with no side effects on permanent data.
- Developers supply AL code for the generate system action and must make the cancel action clear all traces of the output.
- Prompt options must be option fields and should never be required. Only the prompt itself can be required.
- The Copilot menu appears on all list pages and the floating overlay shows the topmost action, which users can hide. Cards and documents do not have the menu yet, but prompt actions can be placed on subpages and in dialogues.
- To find Copilot features, check the Copilot and AI capabilities page. Only English is currently supported, so English must be selected as the language. The features come from version 24 (2024 release wave 1).
Features
| Feature | Status | At |
|---|---|---|
| Suggest sales lines with Copilot | status not stated, demoed | 4:43 |
| Prompt dialogue interface | status not stated, demoed | 6:47 |
| Output mode regeneration and iteration | status not stated, demoed | 9:31 |
| Map e-document lines to purchase order | status not stated, demoed | 10:41 |
| Marketing text generation with Copilot | status not stated | 7:48 |
| AI human-in-the-loop interaction model | status not stated | 2:01 |
| Building user trust in AI features | status not stated | 13:19 |
| Prompt dialogue page type | status not stated, demoed | 20:56 |
| AI-generated content preview and discard | status not stated, demoed | 19:04 |
| AI confidence level marking | status not stated | 19:24 |
| Placeholder text and instruction hints | status not stated, demoed | 27:33 |
| Prompt options for output customization | status not stated | 24:35 |
| Generate system action | status not stated | 26:01 |
| Cancel system action | status not stated | 26:01 |
| Undo principle for prompt dialogues | status not stated | 26:43 |
| Prompt guide | status not stated, demoed | 28:07 |
| Copilot menu on list pages | status not stated, demoed | 29:28 |
| Floating copilot menu overlay | status not stated, demoed | 29:46 |
| Analysis assist | status not stated, demoed | 30:33 |
| Dialogue prompt actions | status not stated, demoed | 31:45 |
| Subpage prompt actions | status not stated, demoed | 32:16 |
| Sparkle action icon | status not stated | 32:50 |
| Copilot and AI capabilities page | status not stated | 34:28 |
AL objects mentioned
As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.
- page 42 “Sales Order” at 4:43
- page 50 “Purchase Order” at 10:41
- page “prompt dialog” at 23:55
Not found in BC28-30: page “prompt dialog”.
Quotes
- 0:36 “AI is here to stay and it’s bringing more transformation than most of us have seen in our lifetime”
- 2:01 “the computer is working with the human user to solve the task and that distinction that way of placing the AI in relation to”
- 6:47 “it has three stages it has the input mode it has the generating mode and it has the output mode”
- 7:28 “consider really if there’s an opportunity to save a few clicks by using structure data if you have it”
- 11:01 “we actually skip the input mode because we had all the input we needed no need to directag the user through an input stage”
- 13:19 “most business users are not AI experts it’s not necessarily clear what AI um is best for at this point in time”
- 13:40 “building trust using AI uh requires that the users are comfortable with uh the limitations of AI”
- 14:41 “faster or more efficient and a i can help gain insights uh get to knowledge”
- 17:02 “instead of trying to rule out all um wrongdoings of AI we need to bracket it we need to control Ro we need to”
- 17:42 “no AI will be ever perfect because no model can interact with the physical world in a complete way so human needs to be”
- 19:04 “the system in this case business Central must always provide a preview or a way to completely undo what AI suggested”
- 23:34 “the promt dialogue is going to be with us from now and going forward and and it will complement the other page types we”
- 25:26 “it’s a good practice never to require the user to choose the prompt options what can be required is the prompt but the prompt”
- 26:43 “it’s very very important that when you are developing a new prom dialogue that you obey to this principle of uh undoing”
- 27:19 “don’t make any side effects of the generated output because that way you are uh not allowing the user to roll back”
- 28:48 “prompting is not going to feel natural to every user so this is an important way of giving them some templates to work from”
- 29:28 “we have actually placed it front and center of all list places so there is now a thing called the co-pilot menu that is”
- 31:27 “use that space wisely for an action that actually is supposed to be very prominent um so uh we are making good use of”
- 33:48 “consider the best use of the prompt dialogue for every scenario meaning what type of input do you have what kind of output do”
- 34:48 “right now we only support English language so make sure that English is selected as your language and also this is from what we”
Disclaimers in the video
- 21:17 not-in-this-release: currently there is no uh partner extensibility for the chat in uh business Central
- 32:16 other: we don’t have any co-pilot menu on the entity page yet so cards and documents don’t have that capability that lists have yet
- 34:48 other: right now we only support English language so make sure that English is selected as your language
Presenters (as heard): Yovinda, Soren Alexanderson, Cern, Yakob, Soren.
