business-log-skill

To record business operation logs within a database transaction for auditing, use the TxSave service to persist structured BusinessOpLog entries alongside your business data inside a single commit. This ensures logs and business changes are saved atomically.

Yes, GORM supports in-transaction logging for change tracking and data recovery. This Skill integrates directly with GORM-backed databases, allowing you to wrap operations in a transaction and persist structured log entries atomically within the same commit.

The best way to query operation logs by business ID for traceability is using the Query service. It fetches persisted log entries by filtering on business_id or business_type, enabling flexible analysis and auditing of past in-transaction operations.

An in-transaction audit log needs structured data fields including business_id, business_type, operate_type, and a Data payload. Storing these specific fields in each BusinessOpLog entry ensures operations are traceable and supports flexible querying for audits.

No, you cannot use this transactional log service effectively without a GORM-backed database setup. The TxSave and Query functions are specifically designed to integrate with GORM to guarantee that business operations and audit logs share the same transactional commit.