- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Variables
- Arguments
- Imported Namespaces
- Trigger-based Attended Automation
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- Studio Logs
- Setup Logs
- OCR Diagnostic Logs
- Logging Levels
- Types of Logs
- Protecting Sensitive Information
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- Troubleshooting
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
Protecting Sensitive Information
To protect sensitive information that is logged during the execution of your automation at the Verbose level, you can choose not to log variable and argument values in both Orchestrator and Studio.
To do this, you can select the Private property check box from the activities that use sensitive information.
- This property is currently not available in cross-platform projects and for some activities in Windows projects.
- The property only applies to default log messages. It does not apply when explicitly logging variable and argument values via activities such as Write Line or Log Message. To learn more, see Logging Levels.
This option is visible in the DisplayName of the activity:
excludedData parameter in the project.json file from a given project (%HOMEPATH%\Documents\UiPath\[PROJECT NAME]).
By default, only two words are reserved: "private" and “password.”
However, you can easily add custom reserved words, under the default ones, in between quotation marks. Please note that wildcards (*?) are supported.
In the example below, all the activities that have password in the name do not send logs to Orchestrator.
