Workflow M2M Audit Attribution

Workflow enablement updates can now preserve the originating DB user when called through trusted agent M2M authentication. This keeps audit columns accurate for agent-driven workflow operations while continuing to ignore caller-supplied audit fields for normal user-authenticated requests.

What's New

• PATCH /api/v1/accounts/{accountId}/data-products/{dataProductId}/workflows/{workflowId} accepts an optional updatedBy DB user UUID for M2M callers.
• Browser/session-authenticated calls continue to use the authenticated user's DB UUID and ignore updatedBy.
• M2M calls without updatedBy leave audit attribution empty instead of storing a machine identity.

Request Example

{
  "enabled": true,
  "updatedBy": "550e8400-e29b-41d4-a716-446655440099"
}