Interface IterativeActivityRunSpecifics
- All Superinterfaces:
- ImplicitSegmentationResolver
- All Known Subinterfaces:
- PlainIterativeActivityRunSpecifics<I>,- SearchBasedActivityRunSpecifics<C>
- All Known Implementing Classes:
- AbstractImportActivityRun,- AsyncUpdateActivityRun,- AutoScalingActivityRun,- FocusValidityScanPartialRun,- ImportActivityRun,- IterativeActivityRun,- LiveSyncActivityRun,- PartialReconciliationActivityRun,- PlainIterativeActivityRun,- ReclassificationActivityRun,- ResourceObjectsReconciliationActivityRun,- ScanActivityRun,- SearchBasedActivityRun,- ShadowCleanupActivityHandler.MyRun,- ShadowIntegrityCheckActivityRun,- ShadowRefreshActivityHandler.MyActivityRun
This interface summarizes what should an implementor of 
IterativeActivityRun
 (either plain or search-based) provide.
 Main responsibilities (at this level of abstraction):
 1. provides custom code to be executed before/after the real execution (if needed),
 2. provides custom code to be executed before/after individual buckets are executed (if needed),
 3. provides default reporting configuration,
 4. indicates what activity state should be used to keep threshold counters - TODO to be reconsidered,
 5. interprets implicit work segmentation configuration.
 The real "meat" (e.g. query formulation, item processing, etc) is in subtypes, though.
 This "specifics" functionality is pulled out from IterativeActivityRun to precisely
 describe the interface between the generic activity framework and specific activity implementation.- 
Method SummaryModifier and TypeMethodDescriptiondefault voidafterBucketProcessing(OperationResult result) Called after bucket is processed.default voidafterRun(OperationResult result) Called after the run.default voidCalled before bucket is processed.default voidbeforeRun(OperationResult result) Called before the run.@NotNull ActivityReportingCharacteristicsdefault AbstractWorkSegmentationTyperesolveImplicitSegmentation(@NotNull ImplicitWorkSegmentationType segmentation) Converts `ImplicitWorkSegmentationType` into "real" segmentation configuration.default ActivityStateuseOtherActivityStateForCounters(@NotNull OperationResult result) Should we use activity state other than the state of the current activity when keeping the counters (e.g. for thresholds)?
- 
Method Details- 
beforeRunCalled before the run. Note that e.g. for search-based activities the search specification is *not* known at this moment.- Throws:
- CommonException
- ActivityRunException
 
- 
afterRunCalled after the run.- Throws:
- CommonException
- ActivityRunException
 
- 
beforeBucketProcessingdefault void beforeBucketProcessing(OperationResult result) throws ActivityRunException, CommonException Called before bucket is processed. (For search-based tasks the search specification is already prepared, including narrowing using bucket.)- Throws:
- ActivityRunException
- CommonException
 
- 
afterBucketProcessingdefault void afterBucketProcessing(OperationResult result) throws ActivityRunException, CommonException Called after bucket is processed.- Throws:
- ActivityRunException
- CommonException
 
- 
createReportingCharacteristics- Returns:
- Reporting characteristics of the activity run. They e.g. provide default values
 for ActivityReportingDefinition.
 
- 
useOtherActivityStateForCounters@Experimental default ActivityState useOtherActivityStateForCounters(@NotNull @NotNull OperationResult result) throws SchemaException, ObjectNotFoundException Should we use activity state other than the state of the current activity when keeping the counters (e.g. for thresholds)?
- 
resolveImplicitSegmentationdefault AbstractWorkSegmentationType resolveImplicitSegmentation(@NotNull @NotNull ImplicitWorkSegmentationType segmentation) Description copied from interface:ImplicitSegmentationResolverConverts `ImplicitWorkSegmentationType` into "real" segmentation configuration.- Specified by:
- resolveImplicitSegmentationin interface- ImplicitSegmentationResolver
 
 
-