Validation Rules: relations of relations?

Question

Hey all, I’m going a bit cross-eyed here. I’ve got a validation rule that should verify that Acronyms on which an asset is dependent have related Business Terms. Eg… Policy depends on definition of Business Term (some of which are Acronyms) Acronym is acronym for Business Term rule { given { supportingAcronyms = relations.'depends on definition of'?.findAll{it.assetType.name == 'Acronym'} supportingAcronymNames = relations.'depends on definition of'?.findAll{it.assetType.name == 'Acronym'}.name...

georgecheung · Answer

according to: https://productresources.collibra.com/docs/collibra/latest/Content/Assets/ref_asset-model.htm

Note (Complex) Relations are only available one level deep. This means that when your script refers to a target asset through a (complex) relation, that referred asset will contain all the aspects of the asset that are mentioned above (name, attributes, etc), but without the (complex) relations of the referred asset.

Which means relations and complex relations can only be extracted from the first level, so it would not be possible to use validation rules to retrieve relations of relations. In this case - I would recommend using workflows to do the validation since the workflow does not have that 1 level relation limitation.

arthurburkhardt · Answer

@tom.friesen Even though the validation rules relations property are supposed to return Map<String,List<AssetModel>>, the relations is not populated (i.e. it is not recursive).

You can quickly check with the following code (based on a Data Asset - is represented by -> Acronym -> is acronym for -> Business Term):

rule {
  given{
    result = relations.'represented by'.first().toString()
  }
  then{
    isLengthEq(result, 0, message: "result: ${result}")
  }
}

Funnily enough, this generates an error FROM THE POSTGRES DATABASE (because the datatype only support VARCHAR(255) and collibra tries to insert the full result message, which then gets logged. => Positive side effect, we get logging! w(ﾟДﾟ)w

In my case, the (edited) log says:

Caused by: java.sql.BatchUpdateException: Batch entry 0 insert into dgc.TERM_VAL_RES ([...])
values ([...]
 'result: {id=3d2d4cdf-2526-4b56-b6d9-f7b61714845c,
 name=PII,
 displayName=PII,
 articulationScore=0.0,
 type={[...]} ,
 assetType={[...]} ,
 vocabulary={[...]} ,
 attributes={00000000-0000-0000-0000-000000000202=[PII is an acronym for Personally Identifiable information],
 Definition=[PII is an acronym for Personally Identifiable information]},
 relations={},
 complexRelations={}} ',

As you can see, the “relations” field is empty, even though there is a relation from my PII acronym to a business term.

mickkarls · Answer

@tom.friesen . One of our internal experts had this to say: Validation rules are complicated, unfortunately. Checking this will take some time, it seems they are using custom relations, so in any case we cannot test it. Also it is not clear (from the message) what is the error? I suggest 2 things: More information (+ examples) : https://productresources.collibra.com/docs/collibra/latest/Content/DGCSettings/OperatingModel/ValidationRules/to_validation-rules.htm; There is even a section for relations inside When ‘A’ doesn’t help; could you book a coaching session (1hour); so the Architect can have a look together with the customer on the instance?

1	Grant Rollerson SUNCORP CORPORATE SERVICES PTY LTD
2	Tom Friesen Algonquin College
3	SB S Benson Plus3 IT
4	S stefan_busch
5	Brian Lloyd USA TODAY Co.
6	D daverichard