Like to understand how proliferation works in Secure@Source.
Are the data stores "linked" if the sensitive data fields contain the same name in any given 2 data stores?
Can we add custom logic (just like rule bases linking in metadata manager) to link two data stores of the sensitive data fields are of not the same name?
The documentation doesn't give any clue.
You can make use of the Import Custom Lineage which will create the Prolefiration across the Datastores and this doesn't need the same fields to be used across the Datastores :