Test Data Management
- Test Data Management 10.4.1
- All Products
Bug
| Description
|
---|---|
SATS-16903
| If you enable the
Auto Sync Catalog option for a data store, the
Connection String and
Schema Option property values get deleted.
|
SATS-16114
| If you run a scan on a Salesforce source, the scan fails at the Collect Row Count step.
|
SATS-14408
| When you create a Microsoft SQL Server data store, if you enter the instance, the Test Connection option fails.
Workaround: Do not enter a value in the
Instance field.
|
SATS-14387
| When you import details to create a new data store, the values you add in the
Schema/Path column of the import file do not appear on the UI.
|
SATS-14385
| When you scan an SAP data store, the following issues occur:
|
SATS-14379
| For Amazon S3 data stores, when you run a metadata with data scan, the
Evaluate Classification Job fails.
|
SATS-14323
| For Salesforce data stores, when you run a scan, the risk score and policy impressions values are set to zero.
|
SATS-14316
| For French and German instances, when a field or file name contains extended ASCII codes such as
ÚÜáàâãçéêíóôúü_All_Customers.csv , Secure@Source is unable to determine if the field or file is sensitive.
|
SATS-14210
| Users with the View Task, Edit Task, and Export privilege cannot download and view DSAR reports unless they also have the View Subject Registry privilege.
|
SATS-14208
| Although the user has the required DSAR privileges, the
Task Details tab freezes and displays an error.
|
SATS-13062
| There is no Online Help for the Manage Risk Simulation feature.
|
SATS-12484
| For Secure@Source 5.0 and the Protection 5.0 product, if you configure a Catalog metadata CSV file to add or delete some of the metadata, import the CSV file, and later import a CSV file that contains only the Catalog metadata you did not add or delete in Secure@Source, Enterprise Data Catalog retains only the metadata included in the latest imported CSV file.
Workaround: Re-import the CSV file that contains all of the Catalog metadata for the data store.
Impacted products: Secure@Source and Secure@Source Protection
|
SATS-12574
| On the
Subject Registry Details page, a user can view data stores that the user does not have permission to view.
Impacted products: Secure@Source
|
SATS-12279
| Persistent Data Masking job logs are not available on the Secure@Source UI. The job displays the following error message:
Job with ID <ID number> failed in TDM .
Workaround: Navigate to the following directory:
$INFA_HOME/TDM/logs/jobLogs . Locate the job log file for the job ID in the message, and view the log.
Impacted products: Secure@Source Protection
|
SATS-7533
| Persistent Data Masking jobs fail when the name of the Data Integration Service is not
DIS or
Data_Integration_Service .
Workaround: Change the name of the Data Integration Service to
DIS or
Data_Integration_Service . If you cannot rename the Data Integration Service Name, perform the following workaround steps to rename the service in the Administrator tool:
Impacted products: Secure@Source Protection
|