How RPA stores sensitive data in log files mainly depends on how you configure the process script. See the section on log files within the Hyland RPA Designer documentation for more information.
Note the following information about the data stored in the log files:
- The logs are cached on the bot during development. At the end of processing, they are moved, depending on the configuration.
- In any case, they are stored in the database (encrypted like all other data), so they are accessible through RPA Manager.
- Optional. Depending on the configuration, these logs can also be stored on the network drive.
- The data may include personal data if personal data is explicitly read in the process and output in the log.
- When this data is read, it can be stored in encrypted form and would therefore be unreadable in the log.
-
Optional. In addition to logs, protocols can also be created and stored on the network drive. See the section on acceptance protocols within the RPA Designer documentation for more information.
These logs contain the log entries for each step and may include a screenshot.
Although the log entries may be encrypted - the screenshot is not, and may therefore contain visible personal information.
- Logs are typically used to verify the contents of a document and are created for a limited period of time.