In security, activity logging concerns the reporting and auditing of RPA processes. This feature is essential to tracking data compliance and reinforcing security measures. Logging also provides detailed information that can be used to improve process efficiency.

1. By
Suhruth Dantu
Software engineer- Robotics
FALLOUT MANAGEMENT
&
LOG MECANISM

2. Data Compliance Architecture
Log Mechanism Fallout Management
 Global
Process
Tracking
 The Benefits
of Logging
Configuration
 Built-in
Compliance
Measures
 Visual Logs
 Summary
 Genuine
 Genuine
Fallouts.
 Exceptions.
 Resolution.

3. Global Process Tracking
Enterprise-level RPA tools set logging actions at a global level, which means that every possible action in the
automation can be tracked and time-stamped when the feature is activated. Typically, RPA robots record all
activity on a step-by-step basis and store it in a session log. This global process tracking provides a fully
operational audit trail, but the detailed action logs can also be used to extract actionable analytics, to be
displayed in a centralized control panel. Thus, with comprehensive governance measures, your business can
ensure security compliance while bolstering efficiency.

4. Log Mechanism
In security, activity logging concerns the reporting and auditing of RPA
processes. This feature is essential to tracking data compliance and
reinforcing security measures. Logging also provides detailed
information that can be used to improve process efficiency.
 Transaction Logs.
 Audit Logs.
 Error Logs.

5. Transaction Logs
• Transaction logs are used for tracking the status of the bot and the
time taken by the bot to complete the operations process.
Sl.no XXX ID Start Time End Time Status Remark
1 22xxxxx66xxxx 14:31:15 14:38:16 Successful Completed
1 22xxxxx67xxxx 14:38:25 14:40:16 Manual Fallout Reason

6. Audit Logs
The Audit Logs are used for Research and Analysis when an unknown Error Occurs.
Audit Log:
==================================================================================================
Task Name: XXXXXXXX.
Open X Application: X Application opened successfully.
Perform Click on __ Button: Click was performed successfully.
Open Spreadsheet: Spreadsheet opened successfully.
Run Macro: Macro ran successfully.
Status: Success or Fallout or Error.
Date: XX/YY/ZZZZ.
Time: xx:yy:zz.

7. Error Logs
Error logs are used while debugging the code and at the time of research on
why error occurred.
Text and Image can be logged in this.
===============================================================================
Error linenumber: XX
Error Description: xxxxxxxxxxxxxxxxxx.
Taskname: xxxxxxxxxxxxxxxxxxx.
Date:11/01/2017 17:41:45.
=================================================================================

8. Visual Logs.
• Another audit control mechanism are the less-common visual logs.
Unlike the typical text data stored in activity logs, visual logs are a
series of screenshots that are created for each action in an
automation during the recording phase. While they provide a handy
reference image as to what each action is intended to perform, they
are most commonly used to for auditing and debugging purposes.
• Visual logs can be very helpful when looking to debug an issue caused
by a difference within a target system that has not been captured or
introduced by an update. The use of visual logs needs to be thought
about carefully due to the information that can inadvertently be
captured within them (customer personal data for example).

9. The Benefits of Logging Configuration
To fit your business needs, log messages can often be configured in
terms of the information they convey. For example, log message
configuration can help administrators filter metrics based on
relevance and data governance standards. This enables your business
to streamline the review process for especially complex automations.
Custom configuration can also allow your business to format log data
(in terms of file type and structure) to be leveraged with business
auditing and intelligence tools. Populating relevant data into your
incumbent intelligence tool and team is helpful in long term
understanding of RPA impact and seeing trends.

10. Built-in Compliance Measures
One reason to look for robust logging within enterprise-level RPA tools
is that the functionality can be utilized to assist with process
compliance. With human teams, businesses set up a process and
attempt to ensure the compliance of documented steps. However, it is
impractical to expect teams to always follow exact documentation,
making it hard to validate compliance. Once a RPA process is built it
will always follow the exact same steps (always compliant), along with
providing the logged steps to prove that the developed steps have
always been followed.

11. Fallout Mechanism.
Genuine fallouts:
The fallouts which needs Manual Intervention i.e. which cannot be
processed by bots are known as Genuine Fallouts.
Exceptions:
Exception is a scenario where Bot throws an error due to system issues
Like System Response, Server response , Application Behavior etc.

12. Resolution & Summary.
In terms of security and optimization, logging is one of the most powerful features in RPA. Global
process tracking ensures that all actions in the automation are accountable and auditable.
Meanwhile, features like logging configuration enable businesses to fit logged data to their
standards. In fact, the top RPA tools are built with enterprise data needs in mind, providing a wide
variety of data governance standards.

13. Thank
You