What problem does it solve? Concurrent editing of the same 1C:Enterprise object by multiple users causes conflicts like "Запись была изменена или удалена другим пользователем" and "объект заблокирован". This Skill guides you through choosing and correctly implementing pessimistic and optimistic object locks so every modifying path is protected and version conflicts surface as actionable messages. ## Core Features & Use Cases - Lock strategy selection: Distinguishes pessimistic locks (Заблокировать / ЗаблокироватьДанныеДляРедактирования) from optimistic version checks, and decides the form id lifetime question. - Full-path audit: Uses Unica MCP code search and graph tools to find every path that modifies an object, including background jobs and integrations, per standard 490. - Conflict handling design: Shapes loud interactive failures versus skip-and-log background behavior, and replaces raw platform version-conflict errors with application-level messages. - Use Case: A user reports "объект заблокирован" when a scheduled job runs. Use this Skill to trace all modifying paths, make the job catch the lock failure and skip with an event-log warning, and verify no transaction is rolled back merely because an object lock failed. ## Quick Start Ask the assistant to review why users get "Запись была изменена или удалена другим пользователем" when editing a catalog object and to add proper object locking to every modifying code path.
