13 Messages
Classify/Flag a Business Terms origin using logic.
Hi,
As we increase the use of Collibra in our organisation we are see a great level of adoption. One item that would assist our on-boarding team, governance team and end users is to be able to flag/classify new assets, specifically Business Terms in our business glossary to start, as to their origin.
For example the following table could be used as POC
Origin 1
On Boarded by project team
Fed through integration source
Origin 2
Created/Added via workflows
Origin 3
Updated attributes associated with the Business Term either manually or via workflows.
This would need to be generated automatically and be non editable by user. The origin filed would be an attribute of the business term also. Would anyone in the community have done something similar like this or have a suggestion on how this may work best in Collibra?
I am assuming we would need to create an automated workflow that would be triggered in the scenarios above.
Community_Alex
678 Messages
•
14.4K Points
3 years ago
@stephen.mc.donald, @bilal.khan.collibra.com tracked down this response from one of our Pre-Sales Engineers, @pascal.vlaemynck: “Yes, as he proposes, they would need to create a simple workflow to be event triggered when assets/attributes are added/updated .”
0
0
shubhangishekhar
15 Messages
2 years ago
Hi @kristen.freer Could you redirect me to this workflow as I might have a similar usecase
1
0
shubhangishekhar
15 Messages
2 years ago
Hi @bilal.khan.collibra.com / @pascal.vlaemynck I have a requirement that I am creating Issue requests from multiple sources so I want to include a custom attribute that updates the source name. For e.g. If I am creating issue via workflow it updates the source name as Collibra and through import API then source name as Source 1 or Source 2 depending on the type of data source. Could you help me with developing this logic
0
0