The workflow engine, Camunda, offers several configuration options to control how history and audit logs are generated and saved. Here are some common configuration options:
1. History Level: It is used to configure the generation level of historical data. Camunda provides four historical level options, namely none, activity, audit and full. The higher the level, the more detailed the historical data recorded.
2. History time range (History Time To Live): It is used to configure the storage time of historical data, and historical data beyond this time range will be automatically deleted.
3. Database Table Configuration: used to configure the database tables for historical data storage, including historical process instance tables, historical task tables, historical variable tables, etc.
4. Audit Logging Configuration (Audit Logging Configuration): used to configure the generation and storage of audit logs, including the format, storage location, and log level of audit logs.
5. Logging Event Listener (Logging Event Listener): used to trigger a custom event listener when the Camunda engine generates history or audit logs, so that users can customize the processing of log events.
The above are some common history and audit log configuration options, which can be configured according to actual business needs. Configuration history and audit logs can help users understand the execution of business processes, discover potential problems and bottlenecks, and optimize and improve them, thereby improving the efficiency and quality of business processes.