Class EvaluatedPolicyRuleTrigger<CT extends AbstractPolicyConstraintType>
java.lang.Object
com.evolveum.midpoint.model.api.context.EvaluatedPolicyRuleTrigger<CT>
- All Implemented Interfaces:
- DebugDumpable,- Serializable
- Direct Known Subclasses:
- EvaluatedAlwaysTrueTrigger,- EvaluatedCollectionStatsTrigger,- EvaluatedCompositeTrigger,- EvaluatedCustomConstraintTrigger,- EvaluatedExclusionTrigger,- EvaluatedHasAssignmentTrigger,- EvaluatedModificationTrigger,- EvaluatedMultiplicityTrigger,- EvaluatedOrphanedTrigger,- EvaluatedSituationTrigger,- EvaluatedStateTrigger,- EvaluatedTimeValidityTrigger,- EvaluatedTransitionTrigger
public abstract class EvaluatedPolicyRuleTrigger<CT extends AbstractPolicyConstraintType>
extends Object
implements DebugDumpable, Serializable
Description of a situation that caused a trigger of the policy rule.
- Author:
- semancik
- See Also:
- 
Field SummaryFields inherited from interface com.evolveum.midpoint.util.DebugDumpableINDENT_STRING
- 
Constructor SummaryConstructorsConstructorDescriptionEvaluatedPolicyRuleTrigger(@NotNull PolicyConstraintKindType constraintKind, CT constraint, LocalizableMessage message, LocalizableMessage shortMessage, boolean enforcementOverride) 
- 
Method SummaryModifier and TypeMethodDescriptiondebugDump(int indent) protected voiddebugDumpSpecific(StringBuilder sb, int indent) booleanprotected void@NotNull PolicyConstraintKindTypeThe kind of constraint that caused the trigger.Human-readable message associated with this trigger.Collection<? extends PrismObject<?>>inthashCode()booleanbooleanisFinal()booleanisHidden()booleanisRelevantForNewOwner(@Nullable EvaluatedAssignment newOwner) Use in connection to foreign policy rules - see the documentation inAssociatedPolicyRule.toEvaluatedPolicyRuleTriggerBean(@NotNull PolicyRuleExternalizationOptions options, @Nullable EvaluatedAssignment newOwner) toString()Methods inherited from class java.lang.Objectclone, finalize, getClass, notify, notifyAll, wait, wait, waitMethods inherited from interface com.evolveum.midpoint.util.DebugDumpabledebugDump, debugDumpLazily, debugDumpLazily
- 
Constructor Details- 
EvaluatedPolicyRuleTriggerpublic EvaluatedPolicyRuleTrigger(@NotNull @NotNull PolicyConstraintKindType constraintKind, @NotNull CT constraint, LocalizableMessage message, LocalizableMessage shortMessage, boolean enforcementOverride) 
 
- 
- 
Method Details- 
getConstraintKindThe kind of constraint that caused the trigger.
- 
getConstraint
- 
getMessageHuman-readable message associated with this trigger. The message explain why the rule was triggered. It can be used in the logs, as an error message, in the audit trail and so on.
- 
getShortMessage
- 
equals
- 
hashCodepublic int hashCode()
- 
toString
- 
debugDump- Specified by:
- debugDumpin interface- DebugDumpable
 
- 
isHiddenpublic boolean isHidden()
- 
isFinalpublic boolean isFinal()
- 
debugDumpSpecific
- 
toDiagShortcut
- 
toEvaluatedPolicyRuleTriggerBeanpublic EvaluatedPolicyRuleTriggerType toEvaluatedPolicyRuleTriggerBean(@NotNull @NotNull PolicyRuleExternalizationOptions options, @Nullable @Nullable EvaluatedAssignment newOwner) 
- 
fillCommonContent
- 
getInnerTriggers
- 
isEnforcementOverridepublic boolean isEnforcementOverride()
- 
getTargetObjects- Returns:
- Target object(s) that were matched by constraint that produced this trigger. For example: target of the assignment that was added (and that matched "assignment" constraint).
 
- 
isRelevantForNewOwnerUse in connection to foreign policy rules - see the documentation inAssociatedPolicyRule. For exclusion triggers the behavior of this method is quite clear. But for other kinds of triggers (on the foreign rule) we return always `true`, as we have no way of knowing whether they are relevant in the context of "the other side". This may change in the future, after we'll learn how to understand this. Hope it will not cause any harm in the meanwhile.
 
-