Audit Records, Signature Records, and GUIDs

The system adds a GUID to audit and signature records. You can use the GUID to track the audit and signature records that are associated with the same action. For example, when a user modifies a field configured to trigger an audit and then clicks the OK button configured for a signature approval, the system creates audit and signature records. The system attaches the same GUID to each of these records. You can use this GUID when reviewing and creating reports of audit and signature records that are associated to a particular action.

A GUID can be created in different ways. The following tables shows how a GUID is created in the various database programs:

For Oracle:

Action	GUID	CFRMKEY	CFRPID	CFRUSER
Interactive OW Application	GUID passed from JDB	mkey from JDB	pid from JDB	user from JDB
Interoperability Applications	"OW without GUID"	hostname	program name	login_userID
Direct Table Operations	"Third Party"	hostname	program name	login_userID

For DB2 for Linux, UNIX, and Windows database:

Action	GUID	CFRMKEY	CFRPID	CFRUSER
Interactive OW Application	GUID passed from JDB	mkey from JDB	pid from JDB	user from JDB
Interoperability Applications	"OW without GUID"	"OWNOGUID"	"OWNOGUID"	$USER
Direct Table Operations	"Third Party"	"3RDPARTY"	"3RDPARTY"	$USER

For DB2 for i:

Action	GUID	CFRMKEY	CFRPID	CFRUSER
Interactive OW Application	GUID passed from JDB	mkey from JDB	pid from JDB	user from JDB
Interoperability Applications	"OW without GUID"	"OWNOGUID"	"OWNOGUID"	"OWNOGUID"
Direct Table Operations	"Third Party"	"3RDPARTY"	"3RDPARTY"	"3RDPARTY"

For SQL Server:

Action	GUID	CFRMKEY	CFRPID	CFRUSER
Interactive OW application	GUID passed from JDB	mkey from JDB	pid from JDB	user from JDB
Interoperability applications	"OW without GUID"	host_name()	"OWNOGUID"	user_name()
Direct Table Operations	"Third Party"	host_name()	"3RDPARTY"	user_name()