Hi everyone,
In a number of OPM projects, I am calling a decision service for each instance of a certain entity. I have noticed that attributes from the calling entity's parent entity are not readily available in the service call.
Example:
In this project I call a decision service for each instance of ‘de immateriële schadevergoeding’:
Two of the input attributes are attributes of ‘de immateriële schadevergoeding’ and pose no problem. The input attribute ‘het geslacht van de persoon’ however, stems from the Global entity. If I map ‘persoon_geslacht’ on this attribute, I get an error at runtime saying ‘Entity is not available from entity instance’.
I've worked around this by creating a ‘copy attribute’ of ‘het geslacht van de persoon’ in the entity ‘de immateriële schadevergoeding’ (this copy is called ‘het geslacht van de persoon bij de immateriële schadevergoeding’ and contains the same value as the attribute in the Global entity). This works fine, so there is a workable solution here.
However, to me it seems as if this limitation is a bit at odds with the usual OPM experience, where attributes from parent entities are always available when writing and executing rules. That's why I was wondering if this limitation is there by design or if it's something that might be changed in a future release.
Best regards,
Jonas