Do you know if there is an easy way to produce the Audit Trail to a document that can be supplied as part of the "package" that gets uploaded to eOriginal?  That would give us the ability to sort of show the chain of custody.  Although I guess we would really need to do this AFTER the transfer to the eOriginal Vault.

Thank you for your response.

To sanely automate that, the only thought that comes to mind involves running Laserfiche Audit Trail 10.x (latest v10 release) which uses a SQL Server database backend instead of AT11's Laserfiche Full-Text Search (LFFTS) catalog backend. Use Workflow (etc.) to run a SQL query that gets the relevant audit log data for the entry export and format the results into however eOriginal needs to consume them. You can use Audit Trail 10.x with Laserfiche Server (LFS) 11 as the underlying binary audit log format LFS produces hasn't changed between v10 and v11.

The easiest way to get the query you'll need is to enable SQL Server Profiler or Extended Events for the Audit Trail database, run the search you want from Audit Trail Reporting (e.g., EntryID=123, User=eOriginalIntegrationUser, Event=Export, DateTimeRange=Last1h), and find and copy the resulting SQL query from Profiler/Extended Events. Then parameterize any relevant bits like EntryID.

Note that the Audit Trail database structure uses numeric codes for event types (which Audit Trail Reporting translates to human-readable labels in the UI), so the SQL query results will include something like "EventType=42" and you'll likely want to "translate" that to something like "EventType=Export" before you pass the data to eOriginal.

With this approach, you may need to set up a small Audit Trail 10.x instance with SQL Server Express for integration purposes. If you do, given the use case I recommend setting the Audit Trail Reporting retention period to something small short a week or two to keep the AT database size minimal, and cap SQL Server Express to using a few GB of memory (otherwise it will try to claim all of it).

If you have a normal Audit Trail 11 instance running, you don't need to make any changes to it for this setup. Multiple Audit Trail instances can point at the same repository and independently ingest its audit data at the same time. The binary audit logs produced by Laserfiche Server and stored in the repository /AUDIT/ directory are the "source of truth". Audit Trail loads a subset of that data into a SQL database or LFFTS catalog to make it accessible for reporting.