As with other Event Rule Actions, AWE Workflows are audited to the Auditing and Reporting Module (ARM) database and can appear in logs and reports--regardless of the type of database you use*.
* For EFT to connect to any database, the proper drivers need to be installed on the EFT computer. If the correct client-side software (drivers) is installed on the EFT computer, AWE can make the database connection string to get to that database. Refer to the EFT System Requirements for information about Oracle drivers.
For all Event Actions, the following items are audited:
Action Types such as move, copy, OpenPGP, and send e-mail.
Action Parameters - These are runtime values passed to the action, not the replacement variables. For AWE workflows, this is the path to the temporary file associated with the workflow executed. This file contains more detailed debug logging if enabled for that particular workflow.
Failed Action Flag - This is captured if this action is the result of a FAILURE sequence on a prior action.
Action Result Code