[midPoint-git] [Evolveum/midpoint] 8c02af: Separate logic of determining correlation event ma...

[Andrej]

  Branch: refs/heads/master
  Home:   https://github.com/Evolveum/midpoint
  Commit: 8c02af258d2cc2c226af469d7aff66426a4dbc93
      https://github.com/Evolveum/midpoint/commit/8c02af258d2cc2c226af469d7aff66426a4dbc93
  Author: Andrej Zan <andrej.zan at evolveum.com>
  Date:   2026-02-26 (Thu, 26 Feb 2026)

  Changed paths:
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/simulation/ProcessedObjectImpl.java

  Log Message:
  -----------
  Separate logic of determining correlation event marks.

**What**

Separate logic which figures out what correlation simulation event marks
should be added to the processed object, from the logic, which finds
event marks used by "shadow management" simulation.

**Why**

First of all, these marks are not used together (at least not now).

Second, addition of the correlation simulation event marks does not
depend on the actual change of correlation state. I.e. we want to add
these marks even if the state has not been changed.

For example in case, when the shadow was already correlated and the
simulation concluded with the same results, the state has not changed.
But we want to show what is the correlation result (in form of marks)
anyway.

**Task**: 11109


  Commit: 36142b371b8613404ebf440920de6646c3bc1380
      https://github.com/Evolveum/midpoint/commit/36142b371b8613404ebf440920de6646c3bc1380
  Author: Andrej Zan <andrej.zan at evolveum.com>
  Date:   2026-02-26 (Thu, 26 Feb 2026)

  Changed paths:
    M gui/admin-gui/src/main/java/com/evolveum/midpoint/gui/impl/page/admin/cases/component/CorrelationContextDto.java
    M gui/admin-gui/src/main/java/com/evolveum/midpoint/gui/impl/page/admin/simulation/panel/correaltion/CorrelationCandidatePanel.java
    M gui/admin-gui/src/main/java/com/evolveum/midpoint/gui/impl/page/admin/simulation/panel/correaltion/CorrelationProcessedObjectPanel.java
    M gui/admin-gui/src/main/java/com/evolveum/midpoint/gui/impl/page/admin/simulation/panel/correaltion/SimulationCorrelationPanel.java
    M gui/admin-gui/src/main/java/com/evolveum/midpoint/gui/impl/page/admin/simulation/util/CorrelationUtil.java
    M infra/schema/src/main/java/com/evolveum/midpoint/schema/util/cases/OwnerOptionIdentifier.java
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/correlation/CorrelationServiceImpl.java
    M model/notifications-impl/src/main/java/com/evolveum/midpoint/notifications/impl/events/CaseManagementEventImpl.java

  Log Message:
  -----------
  Fix issues in Correlation simulation results page

**What**

Fixes:

- Wrong metrics values.
- Incorrect values in the correlation candidate column.
- Exception when "unfolding" row with more candidates.
- When the correlation is uncertain, show also the "no owner" option.

**Why**

Regarding the addition of the "no owner" option. When the correlation is
not certain about the owner, it is possible, that the owner simply does
not exist yet. User should be aware of such thing, so we add a special
"no owner" option to the list of all candidates.

**Notes**

Some of the issues were caused by considering only the processed object
delta for reading candidates/owner. The problem is that this delta may
be empty, when the shadow was already correlated.

If shadow was already correlated, and this simulated correlation
concluded with the same results, then the delta will be empty. Thus we
can not rely only on the delta.

The chosen approach is to either use the "after" object from the
processed object if it is present, or to apply the delta to the "before"
object and use that to find the relevant information.

**Task**: 11109


Compare: https://github.com/Evolveum/midpoint/compare/04e947d5570b...36142b371b86

To unsubscribe from these emails, change your notification settings at https://github.com/Evolveum/midpoint/settings/notifications