Specify the outcome
Example: “In the sales database, create an order for North Ltd. Add two items from my list, save and post it, then send the PDF.” Include the company, warehouse, date, currency and source document when relevant. The agent must find real objects in your configuration rather than copy field names from another database.
Verify the selected records
Codes, tax IDs, SKUs, agreements and companies help distinguish duplicate customer and product names. When several records fit, the agent should ask you to choose. A spelling error does not authorize silently creating a customer. Permission to choose arbitrary test data belongs in a test database only.
Confirm the saved result
Required attributes come from metadata and configuration rules. The agent validates filling and asks for missing business information. After saving, it receives a UUID and reads the object back. Posting may change registers; a request to save alone does not authorize posting. After a timeout, check the receipt and actual UUID first to avoid a duplicate.
Ask for a print form
Bridge retrieves print commands for a saved document. A supported PDF appears in chat with a meaningful name, number and date. Legacy client previews and external forms may need another adapter. A Print button alone does not guarantee PDF export. Reporting data can be queried and returned as a table; running an arbitrary built-in report and exporting its PDF is a separate capability check.
Ready to connect your database?
Sign in, link an issued key or submit an access request. Download the package after approval.