Data Protection
Application logs capture all transaction data while running a process including capturing of even your sensitive data or the confidential data of the organization. These transactional data can be populated in the reporting module of AssistEdge RPA or AssistEdge Engage, which makes those particular set of data visible to anyone who accesses the reports.
AssistEdge provides the maximum level of security and protection of data in both business and operational reports. You can mark the required business data and operational data, which contains sensitive or confidential information, to either mask or anonymize for data protection.
In Automation Studio, the business data which is used for creating business reports can be captured using Business Metrics while the operational data, used for creating operational reports can be captured by passing the data using Process Input option on the Tool Bar menu. Refer Business Metrics activity and Process Input section to know how to capture data using these options.
NOTE: |
A business report is the custom report created by the user while an operational report is the out of the box reports available as part of the product that appears in the Default Dashboards of the Reporting module of AssistEdge RPA or AssistEdge Engage. Refer AE-RPA ReportingGuide or AE-Engage Reporting Guide for more details. |
Once the required data is captured in a particular automation process workflow, follow the instructions mentioned to perform data protection in Automation Studio:
- In the Tool Bar menu of Studio page, click the
(Data Protection) icon. The Data Protection Arguments dialog box appears.
- Click Add and provide the relevant details:
Column Header |
Description |
Argument |
Select the parameter containing data you want to mask or anonymize. It lists only those parameters that have been passed as business data via Business Metrics activity, as operational data via Process Input or if the parameter is passed as both business and operational data. Note: The FileType argument related to Process Input is not available for Data Protection. |
Masking Pattern |
The type of masking to be done to the data. Available options are:
This field is disabled if Anonymized is set to Yes. Note: As a fallback mechanism to support contingency of data protection functionality in Automation Studio, when the selected Process Input argument and the masking pattern does not match the criteria for data masking, the system sets the masking pattern to Default. A system generated alert is sent to the configured e-mail Id. This ensures that the process does not fail even if there is a mismatch in the masking pattern. For example, if the selected masking pattern is CreditCard and the argument mapped is an e-mail, the system changes the masking pattern to Default at the time of process execution . This is applicable only for Process Input argument type. For more information on how to configure alerts for the fallback mechanism, refer Infrastructure Health Monitoring section in the AE-RPA-Administrator Guide.pdf. |
Anonymized |
Encrypts or modifies the entire data completely. Available options are:
By default it is set to No. If set to Yes, Masking Pattern field is disabled. Following is a sample anonymized data: |
Business Report |
Signifies if the data reflects in the business report in the reporting module of AssistEdge. By default it is selected for business data configured and is not editable for such data. However, it is cleared and editable for parameter that is passed as both business and operational data and Anonymized is set to No. |
Operational Report |
Signifies if the data reflects in the operational report in the reporting module of AssistEdge. By default it is selected for operational data configured and is not editable for such data. However, it is cleared and editable for parameter that is passed as both business and operational data. |
- Click Confirm.
The parameter is marked and saved for data protection.