[midPoint-git] [Evolveum/midpoint] b2ad2e: Fix approval delta classifications

[mederly]

  Branch: refs/heads/support-4.9
  Home:   https://github.com/Evolveum/midpoint
  Commit: b2ad2eef50bac2dbfeae186d1220a251240a27f2
      https://github.com/Evolveum/midpoint/commit/b2ad2eef50bac2dbfeae186d1220a251240a27f2
  Author: Pavol Mederly <mederly at evolveum.com>
  Date:   2025-11-18 (Tue, 18 Nov 2025)

  Changed paths:
    M model/workflow-impl/src/main/java/com/evolveum/midpoint/wf/impl/ApprovalsManagerImpl.java
    M model/workflow-impl/src/main/java/com/evolveum/midpoint/wf/impl/util/ChangesSorter.java
    M model/workflow-impl/src/test/java/com/evolveum/midpoint/wf/impl/AbstractWfTestPolicy.java
    M model/workflow-impl/src/test/java/com/evolveum/midpoint/wf/impl/assignments/TestAssignmentsAdvanced.java

  Log Message:
  -----------
  Fix approval delta classifications

Classification of deltas (related to approvals) into "applied",
"being applied", "waiting to be applied", "rejected" and similar
categories takes part of the information from the execution task.

If the task was deleted in the meanwhile, all applied changes were
erroneously displayed as "Waiting to be applied".

This commit fixes that by treating missing task situation appropriately:
it checks the case "closed" status to know the difference between
"waiting to be applied" and "applied" states.

This resolves MID-10828.

(cherry picked from commit 1b643666c4425f1401a5c6c1733456a3f8dc5091)



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