Table of Contents

Search

  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Access Policy transformation
  6. Aggregator transformation
  7. B2B transformation
  8. Cleanse transformation
  9. Data Masking transformation
  10. Data Services transformation
  11. Deduplicate transformation
  12. Expression transformation
  13. Filter transformation
  14. Hierarchy Builder transformation
  15. Hierarchy Parser transformation
  16. Hierarchy Processor transformation
  17. Input transformation
  18. Java transformation
  19. Java transformation API reference
  20. Joiner transformation
  21. Labeler transformation
  22. Lookup transformation
  23. Machine Learning transformation
  24. Mapplet transformation
  25. Normalizer transformation
  26. Output transformation
  27. Parse transformation
  28. Python transformation
  29. Rank transformation
  30. Router transformation
  31. Rule Specification transformation
  32. Sequence transformation
  33. Sorter transformation
  34. SQL transformation
  35. Structure Parser transformation
  36. Transaction Control transformation
  37. Union transformation
  38. Velocity transformation
  39. Verifier transformation
  40. Web Services transformation

Transformations

Transformations

Access Policy transformation configuration

Access Policy transformation configuration

When you configure an Access Policy transformation, you select a data asset that associates policies that you create in
Data Access Management
with the source data set.
A data asset is a data structure such as a table in a database that you have cataloged in
Data Governance and Catalog
. You select the data asset when you configure the properties on the Access Policy tab.
Use a single Source transformation with an Access Policy transformation. Connect the Access Policy transformation directly to the Source transformation.
The following image shows where to place an Access Policy transformation and its configuration options:
The following table describes the fields on the
Access Policy
tab:
The image shows the Access Policy tab of the transformation. The tab
						properties include Consumer, Usage, Data Asset, and Consistency Seed fields
						and a Synchronize Access Policy button.
Field
Description
Consumer
Identifies the user who will consume the data. Select a single user.
Active users in your organization with the Data Marketplace User role appear in this list. Select one of those users. Note that the user you choose helps determine the set of rules that the transformation applies to the data.
Usage
Identifies the usage context such as for customer analysis or anti-money laundering research. Usage context is one type of metadata that helps determine the set of rules that the transformation applies to the data.
Users create and manage usage contexts in
Data Marketplace
. To learn more, see
Set Up Data Marketplace
in the Data Marketplace help.
Data Asset
Identifies the data asset to which the transformation applies the rules.
A data asset is a data structure such as a table in a database that you have cataloged in
Data Governance and Catalog
.
By default, the source object that you selected when you configured the Source transformation appears when you click
Select
. Select the data asset in that source object.
Alternatively, you can select a new connection and a new data asset.
Select
Override Asset name
if there is a difference between the table name and the asset name in the data catalog.
Consistency Seed
Provides a value that represents the rule logic that the transformation applies to the data class.
A consistency seed ensures that a rule's behavior for a data class will be consistent for the same consistency seed value, usage context, and user across mappings. For example, you can ensure that a rule always replaces the last name "Smith" with "Abcd."
If you want consistent tokenization between different Access Policy transformations, insert the same consistency seed in other Access Policy transformations. If you don't want consistent tokenization between different Access Policy transformations, generate a unique seed.
Click
Synchronize Access Policy
and save the mapping to ensure that all required design time properties are configured. This ensures that the appropriate access policy rules resolve correctly when the mapping runs.

0 COMMENTS

We’d like to hear from you!