[midPoint] Inducements being added as direct assignments when adding disabled assignment

[Bao Tran]

Hi All,
I would like to raise a question about an unexpected MidPoint behavior we
observed regarding inducements on disabled assignments.

Org `*costcenter01*` has an inducement to `*AD-group-1`*.

When assigning John to
- *costcenter01* ; `validTo: *1.1.2026*` (a date in the past),

then the end result of the computation is:
John:
- *costcenter01* — direct, disabled -> Which is correct
- *AD-group-1 — **direct** (not via inducement)*

**Question:**
Why does MidPoint add `AD-group-1` as a direct assignment rather than
blocking the inducement due to the disabled status of the source
assignment? We expect either: being added as inducement or Not being add as

We reviewed the documentation on [Activation](
https://docs.evolveum.com/midpoint/reference/master/concepts/activation/)
and [Assignment](
https://docs.evolveum.com/midpoint/reference/master/roles-policies/roles/assignment/)
but could not find any explanation of this behavior.
-- 
Bao Tran
Software developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20260429/ef4b8e10/attachment.htm>