What's New: Business Central Agent Instruction History
Agent instruction history in Business Central: instructions typed in the agent playground are autosaved as a version each time a task runs. Versions can be saved manually with names, viewed by timestamp, and downloaded, including several at once as a zip. Instruction history is not included when the agent is exported.
- Introduction to Agent Instruction History
- Accessing History Features in Business Central UI
- Autosave Mechanism and Download Functionality
- Navigating and Organizing Instruction History
- Manual Save and Version Management
- Summary and Export Considerations
Overview
The video shows how instruction history works when developing agents in Business Central. Instructions typed in the agent playground are autosaved, and a version is added to the history each time a task is run. The presenter says a version is not saved for every edit, to keep the list from growing too long.
The video also covers viewing versions arranged by timestamp, saving a version manually under a custom name, and downloading versions to disk. Downloads can be compared in external tools such as Visual Studio Code or Beyond Compare, because the client has no good diff capability. Exporting the agent does not export the instruction history, so versions must be downloaded manually.
Key points
- Instructions typed in the agent playground are autosaved.
- A version is saved to the instruction history each time a task is run, not on every edit, to avoid a very long list.
- On the agent, the edit instructions action shows the buttons save history, view history and download instructions.
- Versions can be saved manually with a custom name so important ones are easy to find.
- Saving again after an update keeps the previous version and adds a ‘-2’ suffix to the new one.
- The history lists versions arranged by timestamp.
- Individual versions can be downloaded to disk. Selecting several versions downloads them together as a zipped file.
Features
Every feature below: status not stated, demoed.
| Feature | At |
|---|---|
| Agent Instruction History Autosave | 0:17 |
| Manual Save to History | 0:30 |
| Download Instructions | 1:05 |
| View Instruction History | 1:15 |
| Multi-select Download Versions | 1:56 |
| Instruction Version Naming | 1:44 |
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.
- other “agent playground” at 0:17
Quotes
- 0:17 “We are autosaving all of the instructions that you are typing in the agent playground.”
- 0:30 “Every time when you run the task, we are going to save a version to the instruction lock.”
- 1:05 “and invoke the edit instructions, you will see that I have the buttons now to save history, view history and also download the instructions.”
- 1:30 “We wanted to avoid saving too much and creating a too long uh list. Thus, we believe if you run a task with a”
- 2:08 “Because we don’t have good capabilities to do the diff within the client itself. You can use this functionality to download it to disk,”
- 4:00 “You need to export manually as you have seen me using the download button because we are not exporting the instruction history when you”
Disclaimers in the video
- 4:00 other: Instruction history is not exported when you are exporting the agent - manual download required
Presenters (as heard): Nicolola Kukria.