[midPoint] How to not create an assignment that already exists but is indirect / induced ?

[Alcides Moraes]

Hello list,

TL;DR - Is there a way to check for indirect assignments in groovy script expressions?

Now for the full use case:

We have a resource with a custom in-house connector that is working well for direct assignments.
There are inbound / outbound mappings to create the assignments given in midpoint and in the resource directly, both ways.

However, if I give an indirect assignment to an object from midpoint, midpoint also processes the inbound mapping afterwards and then also creates the direct assignment in midpoint as well. 
How should I filter this? I thought about creating a set condition in the mapping, that would check for indirect assignment, but I don’t think there’s a function for this? Midpoint script library has a isDirectlyAssigned function only.

I should note that I’m not using an association mapping, because I need to populate the assignment with additional fields (like orgRef for example), and I don’t think I’m able to do this with the association/assignmentTargetSearch approach, so I’m using standard attribute/inbound mapping and create the assignment there.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20240110/32b50656/attachment.htm>