If there is a precondition for a process to start that depends on data from inside Identity Manager, and that data can be found via searches, use the 'Dynamic Search' precondition validator. The symbolic name is dynamicSearchProcessStartInterceptor.

The 'Dynamic Search' precondition validator validates the number of results that are found by a configured search. Depending on if the number matches the condition or not, the required action is triggered.

1. In Identity Manager Admin, go to CoreTemplate (Identities, Cards,...) > State-Tabs > Additional Commands > Precondition.

2. Configure the parameters:
   

   Parameter	Possible values	Description
   SearchConfig	<SearchConfig>	A search configuration, whose result provides the required data needed to verify the wanted precondition.
   ResultCondition	< lower than = equals > greater than	The condition that is used to validate the number of the result of the search configuration.
   ResultCount	<number>	The number of entries that the ResultCondition validates against.
   Visibility	isDisabled isEnabled isNotVisible isVisible	Action that should be triggered if the condition if fulfilled. If the condition is not fulfilled, the opposite of the configured event will be executed: Selected condition Condition fullfilled Condition not fullfilled isDisabled Process disabled Process enabled isEnabled Process enabled Process disabled isNotVisible Process not visible Process visible isVisible Process visible Process not visible

3. Click Save.

TypedCoreObjectRelationProcessStartInterceptor & RelatedObjectsInDefinedStateMissingProcessStartInterceptor

Functionality:

• Checks if a relation to an object of the hard coded CoreTemplateName / CoreTemplateName and State exists.
• To have a working StartInterceptor, creation of a Subclass is necessary to set a CoreTemplate name

Migration:

1. Configure a SearchConfig that matches with the Relation-Search and State.
2. Use 'Dynamic Search' and set the parameters accordingly as described above.

CoreObjectProcessStartInterceptorComposite

Functionality:

• Combines several hard coded StartInterceptors
• To have a working StartInterceptor, creation of a Subclass is necessary. List with StartInterceptors to combine needs to be hardcoded inside.

Migration:

1. Depending on how the combined StartInterceptors are used in combination, a 1 to 1 migration is not possible.