Tracking Asset Attributes Changed

Hi, @keegan.shirel.collibra.com,

Customizing this tutorial workflow, I was able to get notifications about the additions of new attribute values or about changes to existing attribute values. Here’s how the “main config” ended up looking in the first script task:

import com.collibra.dgc.core.api.model.instance.attribute.Attribute

def attributeId = event.getEventResourceId()
if(attributeId) {
Attribute attribute = attributeApi.getAttribute(attributeId)
def attributeTypeId = attribute.getType().getId()
def attributeName = attributeTypeApi.getAttributeType(attributeTypeId).getName()
def assetName = attribute.getAsset().getName()
def attributeText = attribute.getValueAsString()
	execution.setVariable("isEmpty", false);
  	execution.setVariable("attributeText", attributeText);	
	execution.setVariable("attributeName", attributeName);
	execution.setVariable("assetName", assetName);
} else {
execution.setVariable("isEmpty", true);
}

The event of an attribute value’s deletion required the “if” statement since the getEventResourceId() bean, should there be no attribute value left over, would have nothing to call on. The tutorial’s workflow template says that that bean “assigns the UUID of the attribute that started the workflow to an attributeId variable.”

How can one call on the attributeName and assetName variables I effectively used above in a different workflow that aspires to socialize removals of attribute values entirely?

Happy Thanksgiving to all.

Best,

Tyler

Cc @arthur.burkhardt and his mountain of Data Citizens Forum frequent flier miles

Hi @tyler.bass.tmrhq2.com - I think you’re looking to record the attribute value and attribute type if it has been deleted. In that case, you’ll want to use the activityStreamApi, as Arthur suggested in his first message.

Hi, Keegan, et al,

So, equipped with these workflow beans to which you have kindly referred me, I am trying to notify users of alterations to a given asset’s status and am having some trouble—particularly, by the look of the console, with isolating the domain name as a variable. The idea of course is that the “Asset Status Changed” start event triggers the workflow. Here is my script task thus far:

def eventType = event.getEventType().toString();
def assetName = item.getName().toString();
def assetId = item.getId().toString();
def domainValue2 = getDomainId(assetId).toString();
def domainValue2Name = domainApi.getDomain(domainValue2).getName();

execution.setVariable('eventType',eventType);
execution.setVariable('assetName',assetName);
execution.setVariable('domainValue2Name',domainValue2Name);

String assetUrl1 = "https://tmrdev.collibra.com/asset/" + ${assetId}
execution.setVariable('assetUrl1',assetUrl1);

The idea is that the variables above could end up in a mail task that includes the following message:
The ${domainValue2Name} asset <b><a href="${assetUrl1}">${assetName}</a></b> has undergone a Status change.

An acceptable subject line would be:
${eventType}: ${domainValue2Name} Asset '${assetName}'

Ideally, the mail task could even articulate the specific status at which the asset has arrived. So far, the Collibra console is advising me that I am missing a method for getDomainId(). If you or anyone else here would happen to have any input, please, I would appreciate that. Thanks.

Tyler, I think it is throwing an error because you aren’t calling getDomainId on the item workflow bean.

try replacing def domainValue2 = getDomainId(assetId).toString();

with def domainValue2 = item.getDomainId().toString()

Hi, Sean,

Thanks and sorry. Trying that, I receive a console message informing me that no signature of the method getDomain() is applicable for the following argument types: “(String) values.”

I may be wrong, but I’m not sure that meets the need of the first post. This code queries a workflow instance rather than intercepting workflow events.

Yes, absolutely
Do a little trial/error since the workflow event interception is not atomic (the code is not blocked to ensure all events have been processed before the code runs). As I said in the post, 1s seems to be a reasonable delay.

@arthur.burkhardt, I think if he is only trying to capture the workflow’s start event label and description, the code itself doesn’t need to intercept any workflow events. If this workflow is set to be triggered when an asset attribute is changed, the code is activated in response to a workflow start event. However, he could add more information about the business item which triggered the workflow with the item workflow bean.

This is literally the first line of the thread.

I meant to say I set up my example so it was triggered by the “Asset Attribute Changed” Start Event in the Colliibra workflow settings, as you just noted (should have included that detail! ). The script task within the workflow i wrote, doesn’t need workflow beans since he only wanted the workflow’s start label and desc (at least as I could gather from his code block), but if he wanted to link those details to the item that triggered it, he could also use the item bean.

Sure, multiple ways.

1. Remove responsibility permissions and make a workflow available to reassign resources => You have full control over what happens
2. Parse the activity log, find all responsibility changes and start workflow instances for all resources where responsibilities have changed.

Thank Arthur, much appreciated. Do you know if there is an existing workflow for this?

No, not that I’m aware of

Hi Prashanthi,

import com.collibra.dgc.core.api.component.instance.DomainApi

Please use this.

Thanks,
Paresh