Set AI Brain review strictness and test it
Choose how broadly DMNexa raises review concerns, then use a sample request to see the current AI Brain behavior before relying on it for real drafts.
Choose the strictness level that matches how many optional concerns you want surfaced, save it, and test a realistic sample. Strictness changes review sensitivity, not the requirement for seller approval.
Strictness helps control how noisy or focused AI review feels.
Choose a level
Open More → Settings → AI Brain and find Review strictness. Select the level that fits your business. A lower setting focuses on critical fields such as items, due date, fulfillment, and delivery address. A more thorough setting can surface a wider set of rule-based concerns.
The exact labels shown in your current app describe the available choices. Save the selection and watch for any error before leaving the page.
Test a representative request
Use Try it with a request similar to your real orders. Include some complete details and intentionally omit one important fact. Review what is extracted and which warnings appear.
Repeat with another case that contains a changed or negative instruction. This helps reveal conflicting rules or overly broad custom instructions.
Adjust without hiding important risk
If review feels noisy, remove irrelevant rules before lowering strictness simply to silence warnings. If important gaps are missed, write a more specific rule and test it again.
Testing improves configuration, but real orders still require review because customer language and context vary.
Frequently asked questions
Does higher strictness make AI extraction always more accurate?
No. It affects which concerns the review raises; it does not guarantee perfect understanding of the source text.
Does testing create a real order?
The AI Brain playground is intended to preview behavior. Follow the screen label and use the normal order creation flow for real customer work.
This page is maintained from the current DMNexa product behavior. If your screen looks different, check for an app update or contact support.