Home
Get Community Edition - FREE
LOG IN
Read and Review Automation Anywhere Documentation

Automation 360

Close Contents

Contents

Open Contents

Audit Log

  • Updated: 9/29/2020
    • Automation 360 v.x
    • Manage
    • RPA Workspace

Audit Log

View logs and details to record user activities.

Audit Log displays a read-only table of records of actions performed by users. These log records are searchable and exportable. Audit logs include both Successful and Unsuccessful actions attempted.

Actions

The following Audit log actions are enabled:

Note: Use your cursor to roll over the action button icons to identify specific functions.
Time filter
Users select from preset time filters or configure a custom time filter for log entries to view. The default time filter setting is Last 24 hours.
Search
Search the records. Select additional search filter criteria from the drop-down menu.
Tip: To search the exact phrase, enclose the search phrase within double quotes (for example, "Juan-Finance-564").
Export checked items to CSV
Export the data to a CSV file based on filters and or selections.
Refresh
Refresh and view the updated status.
Customize columns
Show or hide specific columns.
View
To view details of a table entry, mouse over the entry to expand and click Audit details.

Audit log table

View the following audit details in the table. Click a column to sort it in ascending and descending order.
Table item Description
Status Shows action status.
Time Shows the date and time of the action performed.
Event Type

Shows the type of action performed.
Item Name Shows the entity on which action was performed.
Event Started By Shows the user that performed the action.
Source Device Shows the device or machine name or IP address that was used to perform the action.
Source Shows the component: Control Room, Enterprise Client or API, from where the action originated or was performed.
Request ID Shows the unique identity number assigned to a specific set of user actions.

Understanding audit logs

The entry shows the status of each stage of the bot life cycle.
Audit log entry Success Failure
Create automation Bot was sent to the control room and was successfully compiled. Check if the Control Room is up and running.
Bot Sent To Device Control Room deployed the bot successfully on the specified device. Possible reasons for failure entry include:
  • Check if you have configured the Node manager on the corresponding device correctly.
  • Check for the app Automation Anywhere Bot Manager in Add Remove Programs or in Control Panel > Uninstall a program. Try to reinstall by uninstalling and downloading the app again.
  • Try to reinstall by uninstalling and downloading the app again from Device Manager.
  • Ensure the device auto log in details are set correctly.
Run bot Deployed The bot has started on the specified device. Possible reasons for failure entry include:
  • Check if you have configured the Node manager on the corresponding device correctly.
  • Check for app Automation Anywhere Bot Manager in Add Remove Programs or in Control Panel > Uninstall a program.
  • Try to reinstall by uninstalling and downloading the app again from Device Manager.
  • Ensure device auto log in details are set correctly.
Run bot finished Bot execution completed successfully. Possible reasons for failure entry include:
  • Check for the bot execution progression in Activity In progress.
  • Check the code at the line where activity log has been paused for errors.
  • If it has paused at a message box, minimize all windows and check if the message box is in the background.
Bot Runner Session Continued Control Room deploys the TaskBots in a sequence for the same RDP session. Possible reasons for failure entry include:
Bot Runner Session Released When a task successfully completes the execution. Possible reasons for failure entry include:
Download file Downloading to the Control Room. Possible reasons for failure entry include:
Upload file Uploading a file to the Control Room. Possible reasons for failure entry include:
Bot Runner Session Control Room gets the RDP session of Bot Runner machine. Possible reasons for failure entry include:
Send Feedback

  • On This Page