Start with behavior
Example: “Why does Fill from specification change this table in the production order?” Name the document, form and visible menu command. The agent finds the command, handler and called procedures. An ordinary form is inspected through Form.bin; a managed form through its structure and BSL module.
Follow the path to data
After the handler, inspect server calls, queries, attribute filling and register writes. A useful question is: “Which registers does posting affect, and what becomes a filter?” A text match in a module does not prove that branch executes. Dynamic calls require additional verification.
Find customization evidence
Comments, author names, ticket numbers and prefixes help distinguish standard mechanisms from customizations. The agent should give the module path and logic location. An old comment does not prove the code is current: check the working revision and the form actually used. A full export should not be the first step of every search.
Verify the smallest change
For a new calculation, check fields and the query first, then modify the relevant module or form node. Object attributes and their form controls are checked separately. BSL syntax, query execution, configuration saving and database schema update are different checks. A developer plan and Bridge permissions are required. Dynamic updates cannot apply every kind of change.
Ready to connect your database?
Sign in, link an issued key or submit an access request. Download the package after approval.