Bring Your Own App

In app.json, add your app as a dependency:

"dependencies": [
  {
    "id": "<your-app-id>",
    "name": "<Your App Name>",
    "publisher": "<Your Publisher>",
    "version": "1.0.0.0"
  }
]

Then run AL: Download Symbols to pull in your app's symbols so you can reference its objects directly.

Think about where the agent adds most value in your workflow. Some ideas:

• Action on a key page — add a "Send to Agent" button on your app's main list or card page, passing relevant record context in the task message
• Business event trigger — subscribe to an event your app already raises (e.g. a custom document being posted or a status change) and auto-create a task
• Setup page field — expose a config value from your app in the agent setup page so the agent knows about your app's data structure
• Profile customization — use the agent's profile to hide or show pages from your app, scoping what the agent can see

The richer the task message, the better the agent performs. Include record IDs, relevant field values, and a clear instruction:

AgentTaskMessageBuilder
    .Initialize(
        'System',
        'A new ' + Rec.TableCaption() + ' has been created: ' + Rec."No." +
        '. Description: ' + Rec.Description +
        '. Please review and take appropriate action.')
    .SetRequiresReview(false);

Add context about your app's pages and data to the agent instructions — via the setup page field from Stage 8, or directly in the resource file. The more it understands your app's structure, the more accurately it navigates.

Publish both extensions, trigger your integration point, and watch it work. Use the task log from Stage 4 to see what pages it hit and what decisions it made. Iterate on the instructions and message until it handles the workflow reliably.