[midPoint-git] [Evolveum/midpoint] 5757a4: Improve support for existence=true setting

[mederly]

  Branch: refs/heads/support-4.4
  Home:   https://github.com/Evolveum/midpoint
  Commit: 5757a42c2424c39ca48018e0887002aa868cb015
      https://github.com/Evolveum/midpoint/commit/5757a42c2424c39ca48018e0887002aa868cb015
  Author: Pavol Mederly <mederly at evolveum.com>
  Date:   2024-08-07 (Wed, 07 Aug 2024)

  Changed paths:
    M model/model-api/src/main/java/com/evolveum/midpoint/model/api/expr/MidpointFunctions.java
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/expr/MidpointFunctionsImpl.java
    M model/model-intest/src/test/java/com/evolveum/midpoint/model/intest/TestActivation.java
    A model/model-intest/src/test/resources/activation/resource-dummy-fixed-existence.xml

  Log Message:
  -----------
  Improve support for existence=true setting

The "existence=true" setting in schema handling means that we want
to keep the shadow existing even if focal object is being deleted.

However, the default behavior of midPoint is that it considers all
focus data values to be removed, which - by default - means that
the projector is going to remove all values driven by outbound
mappings.

This may be desired behavior for some data (e.g., when anonymizing
shadows belonging to deleted users), but not for all.

This commit adds easily accessible "midpoint.isFocusDeleted()"
method that can be used in conditions for those mappings that control
attributes that have to be kept intact on user deletion.

Related to MID-9669.

(cherry picked from commit 9c285062bc21b294fbd902c4152b4032f0d48829)



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