Separate Data Access Workflows Based Asset Types in Data Basket
Summary: Anie Issac seeks advice on creating Data Usage assets in different domains in Collibra, according to asset types in a data basket. They aim to implement two separate data access workflows—Dataset Access and Data Product Access—each starting differently based on the asset type. Brody Murray responds, confirming collaboration with John on customizing the "Request Assets Access" workflow to address this requirement.
I am looking for information related to the creation of Data Usage assets. In Collibra, the Data Usage domain (domain ID: 00000000-0000-0000-0001-000200000002) is hidden and selected by default. Is there an option to create Data Usage assets in a different domain based on the asset type added to the data basket?
My requirement is to have two separate instances of the data access workflow depending on the asset type in the data basket—for example, a Dataset Access Workflow when the basket contains a dataset, and a Data Product Access Workflow when it contains a data product.both workflow are similar, but their start forms will be different.
If Data Usage assets can be configured to be created in two different domains, I could then add an additional filter (based on domain ID) to trigger the appropriate workflow.
Brody Murray
·3 months ago · EditedHi @Anie Issac ! Thank you for reaching out. I just wanted to touch base to check on this as I believe you are actively working with John on customising the updated "Request Assets Access" workflow to achieve the varying workflow flows based on asset type.
But in short, the data usage domain is fixed, so the easiest way to implement this is through altering the OOTB "Requests Asset Access" workflow to check for the type of asset (XOR Gateway) to branch based on the asset type of the checked-out resource (ie dataset, or data product) within the same workflow definition.