Page History

...

SourceType	Eventtype	Applicationid	CaseId	Context	Occurred	SourceId (mostly model element ID)	SpanId	TaskId	TaskName	TraceId	UserId	UserIp
Login*	Authentication			authenticated;sessionId;requestUrl;authorized_roles
DCM_CaseList	Search			caseIds
DCM_WorkList	Search			results:caseId,taskId
CaseEngine	Create			messageEvent
AQ_Dashboard_CommentList	Search			commentReferenceId
AQ_File_Upload	Create			connectionName;fileIds;authorized;successful
AQ_Timeline	Read			caseIds
DCM_GetTaskInfo	Read
CaseEngine	Update
BAARS	Inbound Service Message			operationName;httpStatusCode
DCM_ThrowAsyncMessageEvent	Update			sendToCaseIds;messageEvent;affectedCaseIds
AQ_Document_Generate	Create			connectionName;fileId
AQ_File_GetMetaData	Read			connectionName;authorized;fileId

* The audit log is built to log login requests from the Runtime. When the JWT login type is used, the user never requests to login at the Runtime, but another component outside the Blueriq Platform facilitates this. Therefore, login attempts cannot be not audit-logged. Please make sure the login provider (for example Keycloak) is set to log authentication requests for audit purposes.

Requirements

The Audit Component only works with Case Modelling. Case information (caseId, taskId and taskName) is only available when the runtime is executing a task.

...

To be able to publish event messages, the event exchange needs to be configured in application-audit.properties This file can be found, or otherwise should be placed in <Blueriq installation folder>\Runtime\conf.