AI Agent Workflow Collection

Use when the agent needs to set or release an infobase connection lock, check whether a lock is active, get session lock parameters for a data area, find active connections to the infobase, put the infobase into user-termination mode or cancel it, open the administration parameters form, programmatically delete marked-for-deletion objects with referential integrity control, get a list of objects marked for deletion, find references to objects being deleted, check or toggle the scheduled-deletion mode, integrate deletion visibility into form lists, or implement before/after deletion hooks. Do not use for routine object recording (delegate to bsp-base-common), for scheduled job management unrelated to deletion (delegate to bsp-longs-and-jobs), for infobase updates (delegate to bsp-update), or for backup operations (delegate to bsp-backup).

Use when the agent needs to open the infobase backup form from a configuration command, save or load backup settings programmatically, read the current backup schedule or status as a user-facing string, generate a navigation link to the backup data processor, calculate the date of the next automatic backup, suppress backup-related warnings at application start in a non-standard scenario, or implement an override hook that disables backup notifications for specific client configurations. Do not use for routine object recording or safe storage (delegate to bsp-base-common), for scheduled job management (delegate to bsp-longs-and-jobs), for infobase version migration (delegate to bsp-update), or for full-text or DT-file operations outside the BSP backup subsystem.

Use when the agent needs to connect a Native API or COM external component on the client or the server, install or update an external component delivered via the configuration, upload a component from a ZIP file, query component metadata (identifier, version, name), or override the set of dependent tables for OData export/import. Do not use for platform-level COM automation (unrelated to BSP), for direct file upload to the external components catalog, or for HTTP integration via web services.

Use when the agent needs to attach a file (scan, document, image) to a reference object, read or download a file's binary data from the infobase, update file metadata without changing versions, copy attached files between objects, open the file UI form, add files via the client dialog, programmatically turn on object versioning, check whether versioning is enabled for a metadata object, record an object version into the history register, read back a stored version, show the version-comparison report or the version history UI from the client, or hook the versioning mechanism into an object form. Do not use for printing or attaching printed forms (delegate to bsp-print-reports), for storing secrets like passwords (delegate to bsp-base-common and the secure storage register), for arbitrary file system operations on the client (delegate to bsp-base-common, Files subsystem), or for working with binary data streams outside the BSP attached-files flow.

Use when the agent needs to add multilingual attribute support to a configuration object, register form handlers that display values in the user's current language, generate dynamic-list queries filtered by language, derive the language suffix used in attribute names, fill predefined elements with translations, build a list-choice handler for input-by-string on a multilingual object, or open a single-attribute editor in multiple languages. Do not use for translating message strings with NStr, configuring print-form templates in different languages, configuring external translation services, or setting up regional application parameters.

Use when the agent needs to extract a clean document or catalog number for display by stripping the infobase prefix, the organization prefix, and user prefixes; needs to compute the print-ready number for a document with given strip-rules; needs to determine the user prefix of a coded object; needs to change the infobase (distributed database node) prefix and continue existing numbering; needs to add the computed-prefix field to a data composition schema; or needs to implement an event handler that resets the object number/code when the date or organization changes. Do not use for setting up a data exchange plan, registering exchange changes, or building queries for the RIB. Do not use for adding an organization as a metadata object.

Use when the agent needs to check or record consent of a personal data subject for compliance with Russian Federal Law 152-FZ on personal data, destroy or hide personal data of subjects, register access events to personal data, integrate the personal data protection subsystem into subject list forms (consent column, hidden subjects filter), override personal data destruction handlers in an applied configuration, or query the storage period and destruction date of personal data. Do not use for unrelated data protection, access management (delegate to bsp-users-access), subsystem connectivity checks (delegate to bsp-base-common), or printing/email/document flows (delegate to bsp-print-reports).

Connected commands, printing, form properties, multilang, files/versions, dedup in 1C…

Use when the agent needs to add an update handler to a configuration, run database update programmatically, check whether an update is required or in progress, register pre-defined elements for update, get or set the infobase version for a subsystem, prepare patch changes before a configuration update, write data inside an update handler without triggering business logic, or implement a hook called before or after the infobase update. Do not use for routine object recording outside an update handler (delegate to bsp-base-common), for routine jobs and background operations (delegate to bsp-longs-and-jobs), or for adding business logic to a configuration (out of scope).