Package com.evolveum.midpoint.schema
Class TaskExecutionMode
java.lang.Object
com.evolveum.midpoint.schema.TaskExecutionMode
- All Implemented Interfaces:
Serializable
Describes the execution mode this task runs in. For example, if it is a "full execution" or a preview/simulation.
Or, if we should work with the production or development configuration.
TEMPORARY IMPLEMENTATION
- See Also:
-
Field Summary
Modifier and TypeFieldDescriptionstatic final TaskExecutionMode
static final TaskExecutionMode
static final TaskExecutionMode
static final TaskExecutionMode
static final TaskExecutionMode
-
Method Summary
Modifier and TypeMethodDescriptionboolean
boolean
TODOboolean
boolean
boolean
What configuration should the actions take into account?@NotNull ConfigurationSpecificationType
toString()
-
Field Details
-
PRODUCTION
-
SIMULATED_PRODUCTION
-
SIMULATED_DEVELOPMENT
-
SIMULATED_SHADOWS_PRODUCTION
-
SIMULATED_SHADOWS_DEVELOPMENT
-
-
Method Details
-
isFullyPersistent
public boolean isFullyPersistent()TODO -
isPersistentAtShadowLevelButNotFully
public boolean isPersistentAtShadowLevelButNotFully() -
isNothingPersistent
public boolean isNothingPersistent() -
areShadowChangesSimulated
public boolean areShadowChangesSimulated() -
isProductionConfiguration
public boolean isProductionConfiguration()What configuration should the actions take into account? Production or "development" one? - Production usually means `active` and `deprecated` lifecycle states. - Development usually means `active` and `proposed` states. However, in the future we may provide more customization options here (e.g. explicit enumeration of lifecycle states to use, or even a set of specific deltas to apply). IfpersistenceMode
is `true` thenproductionConfiguration
should be `true` as well. See https://docs.evolveum.com/midpoint/devel/design/simulations/ for more information. -
toString
-
toConfigurationSpecification
-