Oracle Adds Long-Term Audit Logs for Human Approval Workflows

Human approval is often meant to be the accountable stop in an automated process. But Oracle Integration’s native workflow records are not designed as a permanent archive. With version 26.10, Oracle can now send Human in the Loop workflow activity to OCI Log Analytics, giving customers a configurable way to retain and query the record after the underlying workflow data would otherwise age out.

The new publishing option records each state change for a workflow and its components. That includes workflow creation, completion, faults and expiration, plus task events such as assignment, withdrawal and completion. The resulting records are published as JSON and parsed into searchable fields, creating a timestamped sequence of how an approval moved through the system.

A longer record than the workflow itself

Oracle says its default native retention is 32 days for Standard and Enterprise editions, and 184 days for Healthcare editions. Enterprise customers can extend that native period to six months. After a workflow reaches a terminal state, its instance and task history are deleted once the applicable retention period ends.

That distinction is the point of the release. The published logs live in a log group the customer owns in its OCI tenancy, alongside other observability data. Oracle positions the setup for audit trails that must remain reconstructible after a workflow instance has been purged, as well as for monitoring work that is still underway.

From approval trail to operating view

The parser maps workflow and event states, process name and version, assignee, approver, task result, comments, duration, due date, priority, error ID and project ID into Log Analytics fields. That makes it possible to search for open tasks by assignee, inspect rejected tasks and their comments, compare completion times across workflows, or locate faulted activities.

What Oracle provides out of the box

• An Oracle-defined log source for Human in the Loop activity streams.
• An Oracle-defined JSON parser that maps log attributes to named fields.
• A prebuilt dashboard covering approval demand, open tasks, completion times, outcomes, faults and expirations.

The prebuilt source and parser remove an otherwise common setup job: defining what the logs are and how to break their JSON records into useful fields. Customers can inspect or duplicate those Oracle-defined components if they need additional fields or enrichment, but Oracle’s supplied mapping is available when publishing is enabled.

Useful, but not automatic

Customers must enable Human in the Loop publishing separately for each Oracle Integration instance. They must also first enable Oracle Integration’s activity-stream publishing to Log Analytics. Oracle’s configuration calls for a dedicated HITL log group, plus permissions allowing the integration service to upload logs.

The release does not change who approves a task or make an approval decision more reliable. It changes the visibility of that process: once configured, the state changes behind a human checkpoint can remain searchable on a retention schedule chosen outside the workflow system itself.