bsp-patterns

To find existing BSP patterns for users and permissions in 1C Enterprise, search the SSL library using the ssl_search tool first, then fall back to a codebase codesearch to locate reusable standard modules before writing any custom code.

The best way to handle background long-running operations with progress in 1C is to reuse existing BSP/SSL standard patterns by searching the library first, which prevents unnecessary custom implementations and avoids accumulating technical debt.

Yes, BSP standard patterns support printing form registration and email message sending. You should query the SSL library using ssl_search to find the appropriate module pattern and reuse it instead of implementing a custom solution.

The BSP-first workflow for file storage, attachments, and object versioning history requires no external dependencies. It uses the built-in ssl_search and codebase codesearch tools to discover and apply standard 1C Enterprise subsystem patterns.

You should avoid BSP patterns and write custom code only when the standard BSP module does not fit your specific requirements. The workflow requires you to search SSL first and provide clear justification if a custom solution is necessary.

To search for BSP subsystem patterns for file operations, first query the MCP ssl_search tool for existing SSL matches. If no pattern is found, execute a fallback codebase search via codesearch to locate relevant implementations before proceeding.