Design content mode of prompt dialog page
In this article, you learn how to define the Copilot screen that displays the AI-generated output. The screen is defined by the content mode of the PromptDialog page. It enables users to review output, then choose to regenerate, save, or discard it. The following figure illustrates an example of the content mode for a Copilot extension.
If the PromptDialog page has a prompt area (area(Prompt)), then an edit prompt 
button appears in the upper-left corner of the page when it's in the content mode. Users can select the edit prompt button to open the prompt mode where they can provide new input or modify input. The content mode UI consists of several other elements, which are described in the sections that follow.
For an overview building the Copilot UI, refer to Build Copilot user experience.
Prerequisites
Add a content area
In this task, you define the area of the content that displays results of the AI generation.
To define this area, you add an area(Content) control to the layout, then add one or more data fields. You can structure and arrange fields in groups and page parts. Like the Prompt area, the Content area supports all controls except repeater. Instead of a repeater, you can use a ListPart control.
layout
{
area(Content)
{
field(generatedOutput; Output)
{
ShowCaption = false;
MultiLine = true;
}
}
}
Add a save and discard action
In this task, you add actions to the content mode that enable users to save or discard the AI-generated proposal. Don't save AI-generated proposals to the database until the user chooses to do so. In accordance with the princples of responsible AI, to respect the user's choice.
There are two system actions that control the behavior: systemaction(OK) for saving and systemaction(Cancel) for discarding. These actions appear in the UI by default without you having to add any code where systemaction(OK) has the caption Keep it and systemaction(Cancel) has the caption Discard. However, you do have to add code that handles the content based on which action the user chooses.
This step is optional and only required if you want use captions other than Keep it and Discard. In the
actionscontrol, add a system actionOKfor saving proposals andCancelfor discarding proposals.actions { area(SystemActions) { systemaction(OK) { Caption = 'Save'; ToolTip = 'Save the proposal.'; } systemaction(Cancel) { Caption = 'Cancel'; ToolTip = 'Throw away the proposal.'; } } }Use the Caption property to specify the text that you want to use for the actions. Choose text that is concise but best communicates what the action does. For example, if the OK action inserts a row in list, then perhaps Insert is a better than Keep it.
Add the code that saves or discards the proposal using either the OnQueryClosePage or the value returned from the RunModal.
trigger OnQueryClosePage(CloseAction: Action): Boolean var SaveCopilotJobProposal: Codeunit "Save Copilot Job Proposal"; begin if CloseAction = CloseAction::OK then SaveCopilotJobProposal.Save(CustomerNo, CopilotJobProposal); end;
Add a regenerate action
In this task, you add an action to the PromptDialog page that enables users to generate the results again directly from the content mode.
To include this action, add a systemaction(Regenerate) control to area(SystemActions).
actions
{
area(SystemActions)
{
systemaction(Regenerate)
{
Caption = 'Regenerate';
trigger OnAction()
begin
RunGenerate();
end;
}
}
}
Customize the caption in content mode
By default, the Caption property of the PromptDialog page determines UI caption in prompt and content modes of the PromptDialog page. By using the DataCaptionExpression property, you can change the caption dynamically. This property enables you to display a different caption in the content than in the prompt mode.
A useful pattern for the caption is to use the prompt input that was provided before the AI generation is done. The Business Central's marketing text suggestions with Copilot uses the pattern.
The following code adds the DataCaptionExpression property to our example to set the caption to the text the user provides in the prompt area:
page 50100 "My Copilot"
{
Caption = 'Draft with my Copilot';
PageType = PromptDialog;
Extensible = false;
PromptMode = Prompt;
IsPreview = true;
DataCaptionExpression = UserInput;
...
}
Enable proposal history capability
A user might get more than one generated output when using Copilot. This situation can happen when Copilot provides several versions of an output from start, or when the user chooses to regenerate the output. It can be beneficial to provide users with a way to scroll back and forth through a history of the different proposals. To accommodate this capability, you can set up a version carousel at the top of the PromptDialog page.
This capability requires that the PromptDialog page uses a temporary source table. Unlike with other page types, each record of the source table represents an instance of a Copilot proposal. It can include both user inputs and the AI-generated results.
You should design the capability to insert a new record each time content is generated. When in place, the control appears on the PromptDialog page whenever the source table contains multiple records. After the user closes Copilot, for example by saving or discarding the results, the version history is deleted.
page 50100 "My Copilot"
{
Caption = 'Draft with Copilot';
PageType = PromptDialog;
Extensible = false;
PromptMode = Prompt;
IsPreview = true;
DataCaptionExpression = UserInput;
SourceTable = TempInputData;
SourceTableTemporary = true;
...
}